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

Re: Fwd: ext4 +Booting has failed





On Thu, Mar 13, 2008 at 9:09 AM, Eric Sandeen <sandeen redhat com> wrote:
Justin Conover wrote:
>
>
> ---------- Forwarded message ----------
> From: *Justin Conover* <justin conover gmail com
> <mailto:justin conover gmail com>>
> Date: Wed, Mar 12, 2008 at 6:44 PM
> Subject: ext4 +Booting has failed
> To: fedora-test-list redhat com <mailto:fedora-test-list redhat com>
>
>
> Installed F9Alpha with ext4 on root under lvm, booted fine and things
> were working until I updated Sunday 3/9.  Dell Inspiron 6000 also had to
> use nolapic nohz=off to boot the installer.
>
> With kernel-2.6.25-0.105.rc5.fc9  (why is there an fc still :) )

"Fedora Collection," I've heard :)

> After it reads LVM
>
> EXT4-fs: dm-1: not marked OK to use with test code.

Please see http://fedoraproject.org/wiki/FedoraExt4, specifically:

   * Recent (post-alpha) kernels have a new test in place before
allowing a filesystem to be mounted with this development code - it
requires a special flag to be set. This is both to prevent ext3 from
accidentally being claimed as ext4, as well as to put a psychological
barrier in place. ;) When creating the filesystem, you must do:

[root]# mkfs.ext3 -E test_fs /dev/<device>

for pre-existing filesystems, to set the flag, do:

[root]# debugfs -w /dev/sda5
debugfs 1.40.5 (27-Jan-2008)
debugfs:  set_super_value s_flags 4
debugfs:  quit

If you don't do this, you may get a message like this upon bootup:

EXT4-fs: dm-1: not marked OK to use with test code

... and welcome to "alpha" :)

Please copy back to fedora-test if you like, I'm not on that list...

-Eric

> mount: error mounting /dev/root on /sysroot as ext4dev: Invalid arguement
> setuproot: moving /dev failed: No such file or directory
> setuproot: error mounting /proc: Nos such file or dierctory
> setuproot: error mounting /sys: No such file or directory
> Mount failed for selinuxfs on /selinux: No such file or directory
> (enforcing=0) <- booted up with  (selinux=0) same thing
> switchroot: mount failed: No such file or directory
> Booting has failed.
>
> Default alpha kernel 2.6.24-2.fc9     I get:
>
> Starting udev: udevd-event[1270]: node_symlink: device node '/dev/rtc'
> already exists, link
> to '/dev/rtc0' will not overwrite it
>
>
> Just sits there.
>
> I was going to try 'rescue mode' from the install dvd and mount my
> system, but apparently that isn't setup for ext4 either.. :(
>
> I think I'm looking at a dead duck, but if anyone has a suggestion, let
> me have it.
>
> Not sure if *Eric Sandeen is on this list or not.*
>
>
>


At this point it sounds like I need to do a re-install and do this:

[root]# debugfs -w /dev/sda5
debugfs 1.40.5 (27-Jan-2008)
debugfs:  set_super_value s_flags 4
debugfs:  quit

Before I do the updates and boot.

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