On Tue, May 26, 2009 at 12:53 AM, Neil Bothwick <n...@digimed.co.uk> wrote: > On Tue, 26 May 2009 05:35:46 +0100, Stroller wrote: > >> Mark: yes, I don't see any reason NOT to address by label (e2label or >> whatever XFS / Reiser use) these days. The only thing I can think of >> is that your USB drivers or the kernel module that does USB mass- >> storage is not loaded in time during boot. Aren't there any messages >> about failed mounts amongst the kernel messages on the screen? > > That's most likely the problem, I had a similar situation trying to mount > an SD card at boot time. Two solutions are to mount the device later in > the boot sequence, from /etc/conf.d/local, or to build the necessary > modules into the kernel. Since you're mounting the USB device on boot, > there's no point in having separate modules for USB. > > > -- > Neil Bothwick
Stroller & Neil, Thanks. I don't know why but I hadn't considered the idea that the USB driver would be better built into the kernel for this application. Basically, this is a little PowerPC Mac Mini that I've turned into a new HD Homerun/USB video storage MythTV backend server. I want to be pretty confident that the hard drive is mounted because the machine is headless and sitting in a corner. If someone turns it on after a power failure I don't want to have to mess around to get the external storage mounted. I don't need the drive mounted at boot time, but I certainly want it up and running before the mythbackend script gets started. If I get a power failure and someone restarts everything it could be in the middle of a previous recording and I need the partial recording to end up on USB. I'll look at building in the USB driver into the kernel and using e2label also. I did actually manage to get it working using some udev rules that I found in the forum, but I must say I don't really understand them and never thought they were necessary. I'm glad you guys are thinking the same way. Thanks, Mark
