similar to: bomb out on unknown rootflags?

I tried to convert / to ext3, so I went ahead and entered rootflags=noload,journal=355 on the LILO prompt. The kernel failed to mount /: EXT3-fs error (device ramdisk(1,0)): ext3_get_inode_loc: bad inode number: 355 The boot device is a scsi hard disk, so initrd is used to load the scsi driver, before mounting /. So, it looks like the kernel rootflags= arg gets applied to the ramdisk, not the

Hi Thomas, >----Messaggio originale---- >Da: thomas@kupper.org >Data: 22/01/2010 10.48 >A: "Leszek Ciesielski"<skolima@gmail.com> >Cc: "linux-btrfs"<linux-btrfs@vger.kernel.org> >Ogg: Re: mount command not honoring rootflags passed > > >On 22 Jan 2010, at 10:40, Leszek Ciesielski wrote: > >> On Fri, Jan 22, 2010 at 10:30 AM,

Hi All, I'm new to ext3 and I'd like to boot in data=journal mode. I'm running the latest Debian stable. Where do I put this directive so it happens on every reboot? In the "append=" line in /etc/lilo.conf? Sorry for the confusion, but this line isn't clear to me: ------------------------ You may provide mount options to the root filesystem via LILO using the rootflags

I hate to bother the list with this, but I am lost. With our servers that use LILO we use append=rootflags=data=journal. I have read everything I can find on GRUB, the key is everything I can find, and I have no idea how perform the same function in grub.conf Randy

On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > >

On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > >

Hi I am running a pxe diskless node in f13 and I have some proposals to make ovirt-early working in this version. nash is no more available (nash/mkinitrd is replaced by dracut), so this following command fails : "echo "network --device $DEVICE --bootproto dhcp" | nash" it makes the network configuration incomplete. I replace the linuxrc command by dhclient and it's

I am trying to use data=journal on my root file system. I have separate slices on which journal=data works fine on all of them, except root. I have tried putting rootflags=journal=data on my kernel line in Grub, but I get a kernel panic. I'm missing something simple, I jut know it. It can't be the kernel version because it works on the other slices. My etc/fstab file is as follows:

On Tue, Feb 24, 2015 at 11:56:50PM +0100, Olivier Mauras wrote: > > > On Tue, 2015-02-24 at 16:05 -0500, Laine Stump wrote: > > On 02/24/2015 03:37 PM, Olivier Mauras wrote: > > >> Hello, > > >> > > >> I've been trying to boot a VM with the rootfs being a 9P share from > > >> the host. The VM OS is centos 7. > > >>

Hi, http://www.syslinux.org/wiki/index.php?title=Config > DEFAULT > > DEFAULT command > > Set the default command line (which often references a LABEL). I have tried default vmlinuz-4.12.13_1 root=.... rootflags=.... initrd=.... but vmlinuz does not get executed. I was given a prompt ("boot:"). Despite that "prompt 0" and "timeout 0" are

Hello, I've been trying to boot a VM with the rootfs being a 9P share from the host. The VM OS is centos 7. The OS boots but no services can work and it appears that the authentication system is broken. Now the funny thing is that booting the same OS on the same 9P share manually with Qemu works as expected with a fully functionnal OS... So I'm wondering what could libvirt do that render

I am using RedHat 7.2 w/ kernel 2.4.7-10. My / filesystem is configured as ext3. I want to change it to use data=journaled instead of ordered. If I mount it from a boot floppy, it mounts fine. (mount /dev/hda2 /mnt -t ext3 -o data=journal). I have attempted to find the correct procedure to start it up as journaled from grub to no avail. I have created a new initrd image that works fine with

Hi all, On my slackware 7.1 system, in rc.S fsck is started. In fstab there's the following line: /dev/hda2 / ext3 defaults,noatime 1 1 from the readme I figured that I should put the line append="rw rootflags=journal=102" in lilo.conf The system boots up, but I get the error message that the root partition is already rw. Should I just skip the filesystem

On 02/24/2015 03:37 PM, Olivier Mauras wrote: >> Hello, >> >> I've been trying to boot a VM with the rootfs being a 9P share from >> the host. The VM OS is centos 7. >> The OS boots but no services can work and it appears that the >> authentication system is broken. >> >> Now the funny thing is that booting the same OS on the same 9P share

I am trying to use data=journal for my root file system. If I add: Kernel /vmlinuz-2.4.7-10 ro root=/dev/hda2 rootflags=data=journal To my grub.conf file, all I get is a kernel Panic, "EXT2-fs: Unrecognized mount option data. Kernel panic: VFS unable to mount root fs on 01:00" My fstab file is: LABEL=/ / ext3 defaults 1 1 Any suggestions?

Hi, i am having problems converting the rootfs - I created a journal and booted with "rw rootflags=journal=<inode>" - Before i changes the fstab and put the WIP fsck to /sbin/fsck.ext3. The kernel seems to mount the filesystem ok and then the bootup scripts (debian potato) try to fsck the rootfs which leads to e2fsck 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 JFS DEBUG:

I'm trying to enable writeback mode for the root partition. However, adding the normal option "rootflags=data=writeback" to my grub.conf kernel line doesn't result in writeback mode (according to `dmesg`). Does anyone know of a way to enable this? -Doug -- Douglas E. Warner <dwarner at ctinetworks.com> Network Engineer CTI Networks, Inc.

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

Please be aware that I HAVE NOT TESTED THIS PROGRAM... please try it in a "safe" environment since for all I know it could nuke your "real root" by mistake. -hpa

Hi all, I was trying to mount root-partition which is ext3 partition with noatime and ro option. I included "ro" in the kernel command line But for mounting it with "noatime" option when I searched for some solution I came across a patch http://lkml.org/lkml/2007/8/5/38 But after applying this patch and including option "noatime" in