search for: mkrootdev

The attached patch breaks out the /dev/root device node creation from do_mounts, placing it in it's own utility (called mkrootdev). This is worthwhile, as certain setups will need the device node there to run fstype and load a proper module (or other things). No, it does not currently configure raid devices.... I didn't know if that made sense in there or not.... Let me know what you think - most of the code is just ve...

...tem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.9-42.EL ro root=LABEL=/ rhgb quiet [Linux-bzImage, setup=0x1400, size=0x16dd65] initrd /initrd-2.6.9-42.EL.img [Linux-initrd @ 0x1fefe000, 0x612ef bytes] Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 4.2.1.8 starting mkrootdev: label / not found mount: error 2 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! *************************************** This is what I did: - installed CentOS 4.4 from CDs using "exper...

...for 2.6.13.x (.3 tested) with this kernel. With 2.6.12.6 it works fine. I have not tested this in x86_64 -mode yet. The symptom is that mptbase and mptscsih load, but mptscsih does not discover any controllers nor drives, and things like Booting the kernel. Red Hat nash version 4.1.18 starting mkrootdev: lable / not found mount: error 2 mounting ext3 mount: error 2 mounting none switchroot: mount failed : 22 umount : /initrd/dev failed : 22 kernel panic - not syncing : Attempted to kill init occur. I have been informed that there are changes to the mpt-driver options between 2.6.12 and 2.6.13,...

Hi all, Im network booting initrd-2.6.9-22.EL.img from pxelinux. <snip from init script> echo Creating root device mkrootdev /dev/root umount /sys echo Mounting root filesystem mount -o defaults --ro -t ext3 /dev/root /sysroot mount -t tmpfs --bind /dev /sysroot/dev echo Switching to new root switchroot /sysroot echo UMOUNTING initrd-dev umount /initrd/dev </snip> I receive error while mounting : mount -o defaul...

Hi , I am ruuning Senmail with MailScanner on CentOS 4.4. It has updated to kernel 2.6.9-42.0.8.EL from its past kernel 2.6.9-42.0.3.EL. Now the Server can not boot up and gives the below error. mkrootdev: label / not found Mounting root filesystem mount: error 2 mouting ext3 switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! But I can boot up from its last kernel 2.6.9-42.0.3.EL. I have booted it up from that kernel. But I wnat to rectify that new kernel erro...

...d /lib/md.ko echo "Loading raid1.ko module" insmod /lib/raid1.ko echo "Loading xor.ko module" insmod /lib/xor.ko echo "Loading raid5.ko module" insmod /lib/raid5.ko /sbin/udevstart raidautorun /dev/md0 raidautorun /dev/md1 raidautorun /dev/md2 echo Creating root device mkrootdev /dev/root echo Mounting root filesystem mount -o defaults --ro -t ext3 /dev/root /sysroot echo Switching to new root switchroot --movedev /sysroot [4] grub title Xen (2.6.12xen0) serial root (hd0,0) kernel /xen.gz dom0_mem=192000 com1=38400,8n1 module /vmlinuz-2.6.12-xen0...

...t people will care about: Red Hat nash version 4.2.1.8 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Loading ide-disk.ko module ide_disk: no version for "struct_module" found: kernel tainted. Loading jbd.ko module Loading ext3.ko module Creating root device mkrootdev: label / not found Mounting root filesystem mount: error 2 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! (XEN) Domain 0 crashed: rebooting machine in 5 seconds. I assum...

<some stuff snipped for brevity> > > I didn''t want to make the Xen kernel the default until I was > > sure that it would boot correctly. > > Sensible. > > > > When I put the root=LABEL=/ on it I get an error: > > > > mkrootdev: label / not found > > Yes, I''ve had problems using "LABEL=" on my system too - and > it''s really > not any difference - it''s just easier to change the root drive if you > use LABEL= on the kernel line. > > Can you post your /etc/fstab f...

Hi In linuxrc(on initrd), there is one 'mkrootdev /dev/root' for creating root device, which it later mounts as root. Where does it get the information regarding the real root device from? Thanks Rachita.

...ails to parse the device number, just for kicks. As I said, I can't test this, so feel free to kick me if this doesn't work as expected. On a side note, would it be possible to pull the do_mounts device node creation out into an external tool, ala fstype/ipconfig/nfsmount (I named it 'mkrootdev' here), so that the device node can be created before passing control to kinit? The reason I ask is that I need to call fstype and load the proper fs module before passing control. Again, thanks for klibc! --- usr/kinit/do_mounts.c 2006-03-13 01:14:12.000000000 -0600 +++ usr/kinit/do_mount...

...lilo doesn't really work, the root cause as far as I've been able to go is that '/dev/root' isn't recognized and as such not mounted. With grub this works. The init script in the initrd includes the following (automatically generated): ===8<== echo Creating root device. mkrootdev -t ext3 -o defaults,ro /dev/md0 echo Mounting root filesystem. mount /sysroot ===8<== And looking at the vast amount of RH bugs about this, it seems this root autodetection has caused significant grief, e.g., https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=197701. However, no bugs on th...

....o modules insmod: QM_MODULES ERROR: /bin/insmod exited abnormally! Loading ext3.o module insmod: QM_MODULES: ERROR: /bin/insmod exited abnormally! Mounting /proc filesystem Creating block devices failed to create /dev/hda failed to create /dev/hda1 failed to create /dev/hda2 Creating root device mkrootdev: mknod failed: 30 Mounting root filesystem mount: error 2 mounting ext3 pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 umount /initrd/proc failed: 2 Kernel panic - not syscing: Attempted to kill init! 2. This issue is irrespective of issue 1. I was wondering how I would be spawning the...

...ons passed to my net4521 or with the initrd image itself. What should I do to make the initrd load properly? Please advise. Thanks Prabha linuxrc: ------------ #!/bin/nash echo Mounting /proc filesystem mount -t proc /proc /proc echo Creating block devices mkdevices /dev echo Creating root device mkrootdev /dev/root echo 0x0100 > /proc/sys/kernel/real-root-dev echo Mounting root filesystem mount -o defaults --ro -t ext3 /dev/root /sysroot pivot_root /sysroot /sysroot/initrd umount /initrd/proc ------------- /tftpboot/pxelinux.cfg/C0A80102 -------------- PROMPT 1 DEFAULT net4521 LABEL net4521 KERN...

I have a CentOS 5 machine in which I'm trying to remove lvm. I dd'ed the file system to another partition, then dd'ed it back overwriting the lvm partition. I then modified menu.lst and fstab and replaced the paths to point to the correct device. When the system boots it's still looking for lvm. I can restore the system back to where it was with lvm, but I'm not sure what

I have finally gotten one version of windows 2003 r2 x64 installed as a guest. The bad news is no network. The network tab says it''s a realtek 8139 when I know it is a intel. I tried downloading the intel drivers and they wont install says it''s the wrong hard ware. Is this common that it uses a 8139 as a generic network card? Also the network card shows The

First let me say that I'm not a sysadmin, but am simply wearing that hat this week so please excuse my ignorance. I need to temporarily move some virtual servers from a CentOS-KVM platform to a CentOS-XEN platform while I do some upgrades to the CentOS box. I've created a local LV, and used DD and SCP to transfer the block device from the VKM machine to the XEN machine. For quite a