On 13-06-2020 10:53, J. Fahrner via Dng wrote:
> Am 2020-06-13 10:31, schrieb richard lucassen:
>> The nofail means that it wil mount automatically, but if the disk
>> is absent it won't give errors. But it does not wait for the device!
>
> The disk has itś own power supply and is always connected. I think
> there is something missing at the boot stage (driver?).
>
>> ok, I assume it's u-boot? In that case you can easily try to boot from
>> another disk. But apparently you do not have access to the device?
>
> I don't know the boot process. I think it's like a Raspberry Pi. There
> is a little FAT partion and a EXT4 root partition on emmc. Since it is
> headless, I only can access it through ssh. When it does not boot I
> have to open it, remove the emmc card, insert it into an adapter and
> reverse my changes on pc.This is very elaborate. So I need a
> straightforward method to isolate the problem.
> _______________________________________________


I did have a similar problem with a Raspberry Pi caused by fsck taking
to long to end. If you can add a keyboard giving a CTL D it maybe continues.

Because i only do have data on it I entered a mount in rc.local.

But maybe if you fsck the drive on another system?


Grtz.

Nick