Re: NSLU2 (Slug) fails to boot with second drive connected
I tried the following which is the last part of the directions for
mounting with UUID's.
Then update the initramfs:
$ sudo update-initramfs -u
and flash the new initramfs
$ sudo flash-kernel
Even with both drives having UUID's in /etc/fstab and then doing the
above two commands after putting both drives in the /etc/fstab fiile
when I reboot it still does not automount the second disk.
On 6/18/07, Stuart Read <email@example.com> wrote:
That switching between sda and sdb is the reason you need to use the
UUIDs, from what I remember. So you should probably use UUIDs for all
the USB partitions. Someone else will have to chime in here, but I
think you also need to update the fstab in the slug's flash memory.
There's a very simple command to do this but I can't recall it for the
life of me...
On 6/18/07, Aaron Klein <firstname.lastname@example.org> wrote:
> Yes I was trying to search the website and didnt find anything (i
> guess I was using the wrong keywords) and then I went to search this
> mail list with the web search but got a 500 error page. After I sent
> this message I looked back as far as April 2007 in the archives and
> found the information that at least gets it to boot now using just as
> you said the UUID's instead of the /dev/sd arguments. I found a link
> back to the nsu2-linux website here
> Now I have the slug booting with two drives attached and it sees the
> root drive properly I cant figure out how to get it to auto mount the
> second disk correctly. I thought if I did the same thing as I did for
> the root drive with the second disk using the information from the
> website it would work but no it does not auto mount. I can mount via
> the UUID or the /dev/sd* arguments the second disk right after boot so
> I dont now why its ont auto booting unless there is some other file
> other than /etc/fstab that I need to edit.
> Below is the contents of my current fstab file.
> # /etc/fstab: static file system information.
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc /proc proc defaults 0 0
> UUID=b0beb15a-1e86-40f9-996e-1d58d3bd1936 / ext3 defaults
> ,errors=remount-ro 0 1
> /dev/sda5 none swap sw 0 0
> /dev/sda1 /media/usb0 auto rw,user,noauto 0 0
> /dev/sda5 /media/usb1 auto rw,user,noauto 0 0
> /dev/sda1 /disk2 ext3 defaults, errors=remount-ro 0 2
> Interesting enough after doing the UUID on the root drive the second
> disk became /dev/sda1 where as before it was /dev/sdb1.
> On 6/18/07, Stuart Read <email@example.com> wrote:
> > Hi Aaron,
> > >From what I've read before, you need to mount the disks using UUIDs
> > instead of /dev/sd* type assignments. I believe there is a wiki page
> > regarding this on www.nslu2-linux.org, but I can't find it just now.
> > Maybe search the archives of this list?
> > Good luck
> > Stuart
> > On 6/18/07, Aaron Klein <firstname.lastname@example.org> wrote:
> > > I am having an issue with my recently hacked Slug. I have Debian
> > > running on on the slug and all is well with Samba setup and getting in
> > > via SSH when I have my OS disk in port 1. I have a second disk that I
> > > recently put on port 2 and now when I boot up the unit it hangs at
> > > some point in the boot sequence prior to SSH so I cant get in to see
> > > whats up.
> > >
> > > If I connect the second drive after the unit comes up I can mount the
> > > drive fine and use it as a samba share on XP with no issue what so
> > > ever.
> > >
> > > How can I configure the slug to boot with this second disk in port 2?
> > >
> > >
> > > --
> > > To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact email@example.com
> > >
> > >
> > --
> > To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
> Have pets? Get the help you need from the Pet Advice Network.
> We have 6 websites ready to help you. http://www.petadvice.net
> To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com
To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
Have pets? Get the help you need from the Pet Advice Network.
We have 6 websites ready to help you. http://www.petadvice.net