Hi Tom: On Tue, Jul 8, 2008 at 4:27 PM, Tom Luong <[EMAIL PROTECTED]> wrote:
> I have an autoinstall script which currently works fine for imaging systems > on FC5. I have a new Fedora 9 image and have ported the autoinstall script > from FC5 to Fedora 9. I think there's a labeling issue on Fedora 9. The > imaging process completes if I change the fstab section from using a label > to block device(for example: LABEL=/boot to /dev/md0). However, the system > still fails at boot after imaging. It throws the error "mount: could not > find filesystem '/dev/root'" It seems like many SI users have experience > this issue. I don't think my issue is related to the initrd because I do > see the RAID1 module loaded. I have attached a screenshot of the error > message. > > > > I was able to boot my Fedora 9 rescue disk and chrooted into this image. I > noticed that my blkids didn't have any labels even though there are commands > in the autoinstall script to do this. It looks like Fedora 9 prefers using > UUID instead of label. I came to this conclusion after manually installing > a new RAID1 system. See below. > > > > Has anyone else experience what I'm describing? > > > > I am currently running SI version 3.7.3 > > > > > > Thanks, > > Tom > > > > > > > > [EMAIL PROTECTED] ~]# blkid > > /dev/sda1: UUID="39fed812-247e-23ea-a4f8-63eff4b384c8" TYPE="mdraid" > > /dev/sda3: TYPE="swap" LABEL="SWAP-sda3" > UUID="3e1907c7-24ae-4f70-8cb0-d98d2a29d6ac" > > /dev/sda2: UUID="40067914-6588-e464-388f-705ddb92739d" TYPE="mdraid" > > /dev/sdb1: UUID="39fed812-247e-23ea-a4f8-63eff4b384c8" TYPE="mdraid" > > /dev/sdb2: UUID="40067914-6588-e464-388f-705ddb92739d" TYPE="mdraid" > > /dev/md1: UUID="40170d9c-afa6-4f84-8910-24159f55a498" TYPE="ext3" > > /dev/sr0: LABEL="Fedora 9 x86_64 DVD" TYPE="iso9660" > > /dev/md0: UUID="10f6e1b6-ea02-4f6e-8657-e7924c48cb2f" TYPE="ext3" > > /dev/sda5: UUID="06a1648e-94bc-e8dd-5e04-897435761186" TYPE="mdraid" > > /dev/sdb3: TYPE="swap" LABEL="SWAP-sdb3" > UUID="c001aee7-aef1-4c0b-b2a3-6a8652d91f16" > > /dev/sdb5: UUID="06a1648e-94bc-e8dd-5e04-897435761186" TYPE="mdraid" > > /dev/md2: UUID="8ecc5924-d502-4783-bf78-473b28dc5b60" TYPE="ext3" > > > > > > [EMAIL PROTECTED] ~]# df -h > > Filesystem Size Used Avail Use% Mounted on > > /dev/md0 20G 2.0G 17G 11% / > > /dev/md2 195G 188M 185G 1% /data1 > > /dev/md1 190M 13M 168M 7% /boot > > tmpfs 16G 0 16G 0% /dev/shm > > > > > > [EMAIL PROTECTED] ~]# cat /etc/fstab > > /dev/md0 / ext3 defaults 1 1 > > /dev/md2 /data1 ext3 defaults 1 2 > > /dev/md1 /boot ext3 defaults 1 2 > > tmpfs /dev/shm tmpfs defaults 0 0 > > devpts /dev/pts devpts gid=5,mode=620 0 0 > > sysfs /sys sysfs defaults 0 0 > > proc /proc proc defaults 0 0 > > UUID=c001aee7-aef1-4c0b-b2a3-6a8652d91f16 swap swap > defaults 0 0 > > UUID=3e1907c7-24ae-4f70-8cb0-d98d2a29d6ac swap swap > defaults 0 0 I vaguely remember issues with /dev/root when I was doing some testing with Fedora 7 or 8, but I don't remember exactly what it was. So, if your system can't find /dev/root, perhaps you need to look at your autoinstallscript and change /dev/root to a real block device partition (like /dev/sda1)? Cheers, Bernard ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
