[SOLVED] PPv4: udev-automount not working at boot

[winestock]

I have installed the current udev-automount 1.0 package on my Pogoplug series 4. If I a 2 bay raid box, configured for JBOD, powered on and hooked to one of the USB 3.0 ports on Pogoplug, boot the Pogoplug, only one of the hard drives is mounted correctly. I do see both EFI partitions mount though. In order to get both hard drives to mount correctly, I have to disconnect the USB 3.0 connection, boot the Pogoplug, wait about 10 seconds, connect the raid box via USB and both hard drives will get mounted correctly. I would like to be able to leave the raid box USB connected and powered on and at boot time at have both hard drives auto mount correctly. Has anyone enountered this situation and have found a resolution using udev-automount?

[WarheadsSE]

The udev automount rules are intended for when devices are plugged in, less when present at boot. I suggest making an fstab entry for your drive(s)

[winestock]

As it turns out, the issue was related to having the raid box power switch set for "auto" mode. If I placed the power switch in the "on" position the issue does not happen. In auto mode the raid box would try to sense what was going on with the USB connection and I suspect that it would not spin up hard drives fast enough when the Pogoplug booted.

EDIT: That did not resolve the issue. I eneded up going with adding the hard drive devices to /etc/fstab.

[pitterlee]

So my question is what could possibly be slowing down the transfer? I figured it must be a configuration issue with Arch. Thank you very much in advance.

[xenoxaos]

@pitterlee

What transfer...This topic is about udev not autmounting drives on boot. Not about transfer rates.

As an aside to probably answer your question, check which filesystem your drives are formatted in. If it's not a native Linux filesystem, transfer rates will likely be slow. For example, NTFS/HFS will be incredibly slow because there is a lot of overhead when transferring to/from the drive.