On Sunday, 29 October 2023 10:40:19 GMT Neil Bothwick wrote: > On Sun, 29 Oct 2023 03:16:05 -0500, Dale wrote: > > I have several external hard drives. I have one that is, weird. Others > > work fine. When I first power up the drive, cryptsetup can't open it > > because it doesn't exist yet. > > Is it the drive/enclosure taking too long to power up? There are kernel > options to delay the boot to allow for USB devices to become available, > such as usb-storage.delay_use. Try setting a long delay and, if that > fixes it, reducing the delay until you find a suitable setting.
There's also a rootwait kernel cmdline option. I had to use this to be able to boot a rootfs on a (sluggish) spinning drive on a USB docking station, but I suspect this does not apply to your setup if the rootfs is not stored on this drive. Either way, there may be a case for setting rc_after=lvm in the device_mapper configuration, to make sure all ducks are in a row as the devices and fs containers are initialised in the correct order. You can manage rc service priorities by playing with rc_after and rc_need options. You mention two things, 770T works fine with this combo of external drives and the problem started after you enabled crypto hardware acceleration in the FX kernel. Assuming these observations are reliably repeatable, then this could be explained as follows: The 770T performs decryption slowly using its CPU core(s), as well as loading drivers and initialising any rc services including LVM. This means any initialisation by the kernel of (sluggish) hardware will give it enough time to get up and running. With the FX system, everything happens much faster and at some point it trips over itself, because the sluggish hardware hasn't got its boots on in a timely fashion.
signature.asc
Description: This is a digitally signed message part.
