similar to: mount: error 22 mounting ext3

I have just installed Redhat 7.2 on a P3 with adaptec 2400A IDE RAID. After many attempts with the partitions, I have finally managed to install but not get the following error on boot: creatig root device mounting root filesystem error mounting ext3 pivotroot:pivot_root(/sysroot,/sysroot/initrd)failed:2 freeing unused kernel memory :220k freed kernel panic: no init found. try passing init=option

Hi, I use RH 7.2 (the download version) with kernel 2.4.9-13 (upgraded by using the Up2date program). Today i used Up2date (version 2.7.11) to upgrade to 2.4.9-21 (kernel, headers and source). I get the following error while the new kernel is booting: EXT3-fs: unable to read superblock mount: error 22 mounting ext3 pivotroot: pivot_root (/sysroot, /sysroot/initrd) failed: 2 Of course this

I managed to install RHEL3 onto a 1GB USB key. I had to forgo using grub to get it to but, but am now using extlinux. It actually boots, but ends up panicking. Here's the console messages that should be of interest: usb.c: registered new driver hub Loading ehci-hcd.o module ehci-hcd 00:1d.7: Intel Corp. 82801EB USB2 ehci-hcd 00:1d.7: irq 23, pci mem f882b000 usb.c: new USB bus

Hi everyone, I've been running Redhat 7.2 (new install) for about 2 weeks now without any problems, but today I was not so lucky. My system hung while I was trying to configure the kernel-source RPM using 'xconfig'. After rebooting the system, it seems that my whole ext3 file system is corrupted. I get the message: Mounting root filesystem EXT3-fs: ide0(3,3):couldn't mount

Hi I am trying to have a built in initramfs along with the traditional initrd. So I mount the initrd from the initramfs, but am facing problems in trying to run the 'linuxrc'. Following are the issues: 1. I mount the initrd from the initramfs and exceve 'linuxrc'. It starts executing linuxrc, but gives the following errors and panics: Red hat nash version 3.4.42 starting

I'm trying to install CentOS 2.1 on SATA drive that lives on ICH7R controller. I have the controller setup in BIOS to "compatibility" mode, which means it should look just like regular IDE controller to the OS. In this mode, ide0 and ide1 are PATA controllers, and 4 SATA ports are mapped to ide2 and ide3. If I boot from the 2.1 installation CD, all the drives are detected

Here I don't want to start a discussion, but rather share a *solution* that took me some days to come up with. The whole stuff started with a power-outage. After reboot, my server (ext3) came back with the dreaded file system error (Ctrl-D to reboot or password for maintenance) - if you've never seen this, consider yourself lucky! In any case, I did the fsck as prescribed, but abandoned

Hi all, i'm new in the list so i'm sorry if this i'm posting is off-topic or it was already answered before. I'm having this problem; i've got an ext3 8GB partition and it doesn't mount, the cause of this: a user (yes me!) running fsck.ext3 with the filesystem mounted, ups! (snif, forgive me!!, totally newbie and mad) errors while booting: EXT3_fs error (device hda4):

Hello, I'm using RedHat 7.2. I needed to mount my root fs to QNX 6.1. QNX supports ext2 only but I tried that anyway. It was mounted wrong (e.g. the /root directory was symbolic link to non-existing file). When I wanted to boot from the RedHat again, these errors occured: ... Mounting root filesystem EXT3: failed to open journal device unknown-block(0,0):-19 mount: error 22 mounting ext3

Hello, I'm using RedHat 7.2. I needed to mount my root fs to QNX 6.1. QNX only support ext2 but I tried that anyway. The disk was mounted bad (for example the /root directory seemed to be symbolic link to a non-existing file). When I wanted to boot from the RedHat again, these error messages occured: ... Mounting root filesystem EXT3: failed to open journal device unknown-block(0,0):-19

Hi, The following set of patches is intended mostly to improve ipconfig and nfsmount compatibility with glibc. The context: I'm working on yaird, an alternative to mkinitrd, and currently implementing nfs root file systems. This is based on ipconfig and nfsmount from klibc, with a rewritten version of kinit. Users should be able to build the package with vanilla glibc, since klibc is not

> PDC20265: IDE controller at PCI slot 0000:00:11.0 > PCI: Found IRQ 10 for device 0000:00:11.0 > PDC20265: chipset revision 2 > PDC20265: 100% native mode on irq 10 > PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary > PCI Mode. > ide2: BM-DMA at 0x8000-0x8007, BIOS settings: hde:DMA, hdf:pio > ide3: BM-DMA at 0x8008-0x800f, BIOS settings: hdg:pio,

I recently rebooted one of my machines and was greeted with a message about one of my ext3 partitions having some errors. I dutifully started e2fsck on the partition, but after a few hours of some useful messages about fixing inodes, it then started printing out lists of ascending numbers which I'm not sure how to interpret. The first time I noticed this, these numbers were in the 4000000

First of all you must be able to boot. Thus you must press 'e' when your grub screen appear with selection highlights on Red Hat Linux. Highlight line consisting 'initrd...' and press 'd'. Press 'b' to boot. Because your partition does not have a journal on it, create one with these steps below. - Make sure you remember the device attached to ide3(34,7), it is

I installed a 4.1 x86_64 with kernel 2.6.9-11.ELsmp (rpm) initially. My box is tyan 5350 and a SATA harddisk The install was successful and the harddisk was detected as /dev/sdaX But strangely, when I first reboot my machine. The harddisk change to /dev/hdaX What is the problem ? Below are some of dmesg output hda: WDC WD1200JD-00HBB0, ATA DISK drive Probing IDE interface ide1... Probing IDE

Hi Guys, While recompiling 2.4.18-14 I get kernel/module version mismatch errors from insmod at boot time and eventually resulting in a kernel panic .I'm compiling my kernel following all usual steps doing a proper make clean and make mrproper. Here are error messages I get : Loading jbd.o module /lib/jbd.o: kernel-module version mismatch /lib/jbd.o was compiled for kernel

On 28 Feb 2002, Stephen C. Tweedie (sct@redhat.com) wrote: > Hi, > > On Sat, Feb 23, 2002 at 02:55:33PM +0100, Jan Söderholm wrote: > > > I use RH 7.2 (the download version) with kernel 2.4.9-13 (upgraded by > > using the Up2date program). Today i used Up2date (version 2.7.11) to > > upgrade to 2.4.9-21 (kernel, headers and source). I get the following >

Hi, What is the difference between chroot & pivot_root. They don't seem obvious based on the man pages apart from the below mentioned caveats. 1) Inherited Open file descriptors, have to be explicitly closed. 2) Does not change CWD of the process, which can be overcome by doing a chdir before & after chroot call. Any information on this would be useful. Thanks,

I am trying to find out where to go in regards to problem mentioned in subject line. Maybe you can offer some advice or, if not, then maybe redirect to another organization or web site. I have been installing just about every new release of the kernel that has come out for RH 7.2. I have always recompiled these to a customized version for my Tyan s1598/K6-III system. I do this so that only

Hi All, I am trying to start a lxc container using libvirt and I am facing an issue due to pivot_root. The return code from the system call ?pivot_root? is EINVAL (Invalid arguments). I isolated the issue to this specific condition check within the system call. This is an code snippet from fs/namespace.c::pivot_root * error = -EINVAL; if (root.mnt->mnt_root != root.dentry)