[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: findfs does not find rootfs UUID [solved]



Am Sonntag, 8. Mai 2011 schrieb Rainer Dorsch:
> Am Sonntag, 8. Mai 2011 schrieb Rainer Dorsch:
> > Hello,
> > 
> > I moved my root partition to a new SSD and used ext4 as filesystem.
> > Everything works well, except that I get an error message during boot
> > (which I think was not there before):
> > 
> > findfs: Unable to resolve ...
> > 
> > http://bokomoko.de/~rd/ext4-rootfs-uuid/IMG_6119.JPG
> > 
> > for my root partition. The system boot without a problem though, and when
> > booted findfs works out ok:
> > 
> > blackbox:~# findfs UUID="4a4eb948-2d2b-4188-96ae-76a3776ae69c"
> > /dev/sdb1
> > blackbox:~#
> > 
> > Should I be concerned about this issue?
> 
> Here are some more details:
> 
> From /boot/grub/grub.cfg
> 
> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686-bigmem' --class debian
> -- class gnu-linux --class gnu --class os {
>         insmod part_msdos
>         insmod ext2
>         set root='(/dev/sdb,msdos1)'
>         search --no-floppy --fs-uuid --set
> 4a4eb948-2d2b-4188-96ae-76a3776ae69c echo    'Loading Linux
> 2.6.32-5-686-bigmem ...'
>         linux   /boot/vmlinuz-2.6.32-5-686-bigmem
> root=UUID=4a4eb948-2d2b-4188-96ae-76a3776ae69c ro quiet quiet elevator=noop
>         echo    'Loading initial ramdisk ...'
>         initrd  /boot/initrd.img-2.6.32-5-686-bigmem
> }
> 
> from /var/log/boot:
> 
> Sun May  8 15:08:02 2011: Setting parameters of disc:  /dev/sda.
> Sun May  8 15:08:02 2011:   /dev/sdb.
> Sun May  8 15:08:02 2011: findfs: unable to resolve
> 'UUID="4a4eb948-2d2b-4188-96ae-76a3776ae69c"'
> Sun May  8 15:08:02 2011: Activating swap...done.
> Sun May  8 15:08:02 2011: Usage: mountpoint [-q] [-d] [-x] path
> Sun May  8 15:08:02 2011: Checking root file system...fsck from
> util-linux-ng 2.17.2
> Sun May  8 15:08:02 2011: root_ssd: clean, 878324/3055616 files,
> 6715280/12207384 blocks
> Sun May  8 15:08:02 2011: done.
> Sun May  8 15:08:02 2011: Usage: mount -V                 : print version
> Sun May  8 15:08:02 2011:        mount -h                 : print this help
> Sun May  8 15:08:02 2011:        mount                    : list mounted
> filesystems
> Sun May  8 15:08:02 2011:        mount -l                 : idem, including
> volume labels
> Sun May  8 15:08:02 2011: So far the informational part. Next the mounting.
> Sun May  8 15:08:02 2011: The command is `mount [-t fstype] something
> somewhere'.
> Sun May  8 15:08:02 2011: Details found in /etc/fstab may be omitted.
> Sun May  8 15:08:02 2011:        mount -a [-t|-O] ...     : mount all stuff
> from /etc/fstab
> Sun May  8 15:08:02 2011:        mount device             : mount device at
> the known place
> Sun May  8 15:08:02 2011:        mount directory          : mount known
> device here
> Sun May  8 15:08:02 2011:        mount -t type dev dir    : ordinary mount
> command
> Sun May  8 15:08:02 2011: Note that one does not really mount a device, one
> mounts
> Sun May  8 15:08:02 2011: a filesystem (of the given type) found on the
> device. Sun May  8 15:08:02 2011: One can also mount an already visible
> directory tree elsewhere:
> Sun May  8 15:08:02 2011:        mount --bind olddir newdir
> Sun May  8 15:08:02 2011: or move a subtree:
> Sun May  8 15:08:02 2011:        mount --move olddir newdir
> Sun May  8 15:08:02 2011: One can change the type of mount containing the
> directory dir:
> Sun May  8 15:08:02 2011:        mount --make-shared dir
> Sun May  8 15:08:02 2011:        mount --make-slave dir
> Sun May  8 15:08:02 2011:        mount --make-private dir
> Sun May  8 15:08:02 2011:        mount --make-unbindable dir
> Sun May  8 15:08:02 2011: One can change the type of all the mounts in a
> mount subtree
> Sun May  8 15:08:02 2011: containing the directory dir:
> Sun May  8 15:08:02 2011:        mount --make-rshared dir
> Sun May  8 15:08:02 2011:        mount --make-rslave dir
> Sun May  8 15:08:02 2011:        mount --make-rprivate dir
> Sun May  8 15:08:02 2011:        mount --make-runbindable dir
> Sun May  8 15:08:02 2011: A device can be given by name, say /dev/hda1 or
> /dev/cdrom,
> Sun May  8 15:08:02 2011: or by label, using  -L label  or by uuid, using 
> -U uuid .
> Sun May  8 15:08:02 2011: Other options: [-nfFrsvw] [-o options] [-p
> passwdfd].
> Sun May  8 15:08:02 2011: For many more details, say  man 8 mount .
> Sun May  8 15:08:02 2011: Starting early crypto disks...done.
> Sun May  8 15:08:02 2011: Starting remaining crypto disks...done.
> Sun May  8 15:08:02 2011: Cleaning up ifupdown....
> Sun May  8 15:08:02 2011: Loading kernel modules...done.
> Sun May  8 15:08:02 2011: Activating lvm and md swap...done.
> Sun May  8 15:08:02 2011: Checking file systems...fsck from util-linux-ng
> 2.17.2
> Sun May  8 15:08:02 2011: home_ssd: clean, 257539/4276224 files,
> 11073341/17097176 blocks
> Sun May  8 15:08:02 2011: /dev/sda1: clean, 278/14663680 files,
> 23995714/29304560 blocks
> Sun May  8 15:08:02 2011: /dev/sdb7: clean, 553445/12574720 files,
> 26918497/50293482 blocks (check in 2 mounts)
> Sun May  8 15:08:03 2011: opt: clean, 100621/12222464 files,
> 6554174/24414775 blocks
> Sun May  8 15:08:03 2011: exchange: clean, 11/4890624 files,
> 352990/19531015 blocks
> Sun May  8 15:08:03 2011: done.
> Sun May  8 15:08:03 2011: Mounting local filesystems...done.
> 

The problem was that I specified the root filessytem in /etc/fstab as

UUID="4a4eb948-2d2b-4188-96ae-76a3776ae69c"     /                    ext4          
noatime,discard,data=ordered,errors=remount-ro 0       1

When I use a device, the problem goes away:

/dev/disk/by-uuid/4a4eb948-2d2b-4188-96ae-76a3776ae69c    /                    
ext4          noatime,discard,data=ordered,errors=remount-ro 0       1


Thanks,
Rainer


-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdorsch@web.de
jabber: rdorsch@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: