On Wednesday 22 February 2006 01:16, John Dykstra wrote: > I've got another cannot-boot problem. My UML is built from 2.6.16-rc4 > source, with Jeff's patch set and the defconfig configuration. My root > filesystem is > http://www.stearns.org/uml-root/root_fs.fc-3-base.pristine.20050605.bz2, > with MAKEDEV std, generic, and the ubd0 etc. devices created per the > website, and inittab and fstab modified to use those /dev entries.
> [EMAIL PROTECTED] l]$ ./vmlinux mem=48M ubd0=../fc3_root_working > Linux version 2.6.16-rc4 ([EMAIL PROTECTED]) (gcc version 3.2 20020903 (Red > Hat > Linux 8.0 3.2-7)) #1 Tue Feb 21 14:13:41 CST 2006 > VFS: Mounted root (ext3 filesystem) readonly. > INIT: version 2.85 booting > Welcome to Fedora Core > Press 'I' to enter interactive startup. > Starting udev: [ OK ] This is the point - it remounts a tmpfs filesystem on /dev and fills it via udev. That said, it's really strange that udev doesn't recognize UBD. For what I remember, it should maybe create a /dev/ubda node instead of /dev/ubd0, but I don't see any ubda in your listing. I'm a bit puzzled. Could you retest with 2.6.15 to check for any difference? > Checking root filesystem > [/sbin/fsck.ext2 (1) -- /] fsck.ext2 -a /dev/ubd0 > /dev/ubd0: > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate > superblock: > e2fsck -b 8193 <device> > > fsck.ext2: No such file or directory while trying to open /dev/ubd0 > [FAILED] > > *** An error occurred during the file system check. > *** Dropping you to a shell; the system will reboot > *** when you leave the shell. > Give root password for maintenance > (or type Control-D to continue): > ------------------- > > If I log in at this point, it is clear why the fsck failed--there is no > /dev/ubd0: > > ------------------- [...] > ------------------- > However, if I shut down UML and look at the filesystem via loopback, the > ubd0, ubd1, etc. files are there, with the correct major/minor. > Comparing the two views of /dev, there are also a number of character > device files present in the loopback view that I don't see when > partially booted within UML. > So what filesystem is mounted (read-only) when the boot is interrupted? > How do I get it to contain the necessary block device files? > Or am I totally confused? -- Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!". Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894) http://www.user-mode-linux.org/~blaisorblade ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
