Re: 2 Disks (by label/UUID)
I had also the issue with the UUIDS. However, I did not flash the kernel
in-between, I only changed /etc/fstab.
Also -- at least in my case -- it was sufficient to try to mount *some*
filesystem, not necessarly the rootfs. (Maybe, Stuart, can you try this
too? Does it break if you use UUIDS on some other fs than the rootfs?)
I do not have the hardware here to hook up the serial interface on my
thecus, so I cannot debug that right now.
BTW, As I made a backup of /etc before reinstalling to armel, I actually
have this offending fstab, (just the UUID changed, as this stick is
still in use...)
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/md0 / ext3
defaults,errors=remount-ro,noatime,commit=36000 0 1
/dev/md1 none swap sw 0 0
tmpfs /tmp tmpfs defaults 0 0
tmpfs /var/run tmpfs defaults 0 0
#tmpfs /var/log tmpfs defaults 0 0
#tmpfs /var/tmp tmpfs defaults 0 0
UUID="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" /mnt/systemstick ext2
defaults,errors=remount-ro 0 1
On Mon, 2008-05-12 at 17:19 +0200, Martin Michlmayr wrote:
> * Stuart Read <stuart.t.read+NSLU2@gmail.com> [2008-05-11 21:13]:
> > I can't think of any particular reason the upgrade should have failed,
> > as I've stopped (for the moment) playing with the UUID/label thing and
> > had left things as they were until I had more time to work at it.
> > Any thoughts/suggestions?
> On what exactly? Finding out why it doesn't boot with UUID/label?
> I'd proceed like this:
> - make a backup of flash (cat /dev/mtdblock? > backup)
> - change /etc/fstab to use UUID/label for the root partition and only
> boot entries in /etc/fstab for the first disk
> - Edit /usr/share/initramfs-tools/hooks/flash_kernel_set_root
> and put this at the end:
> echo "root: -$rootdev-" >&2
> - Run: update-initramfs -u
> - Check the output and see if the UUID/label it prints looks ok
> - Run flash-kernel
> - Boot with only one disk attached
> Martin Michlmayr