Red Hat :: Unable To Boot RHEL 5.2 And Unable To Mount Root File System In Rescue Mode
Jan 28, 2010
Environment: A 32-bit kernel RHEL5.3 system running on a virtual machine. The root(/) filesystem is on an LV.
Issue: Unable to resize the FS after extending the root LV since it is mounted. After extending the LV, online resizing of the FS was not supported and the root filesystem could not be unmounted while it was in use. On rebooting, I got a kernel panic error. In runlevel 1, I couldn't run chroot, couldn't find the /etc/fstab, root FS could not be mounted, fsck did not run (tried block 31 for second copy of superblock using dd count=1 bs=4k skip=31 seek=1 if=/dev/sda2 of=/dev/sda2), couldn't find any rpm on installation media to install unix-utils rpm. On running commands in runlevel 1,
I switch on the PC and it loads the Grub splash screen. However, it does not automatically boot the top entry after two seconds as it's supposed to and just hangs. I hit enter to boot it and it attempts to but after a few seconds gives me the error "unable to mount file system....a maintenance shell will be started"
This occurred after I was using it and then everything suddenly froze up on me and I had to crash out Now this!
Booting to CentOS 5.5 works and I am able to login with all my devices mounted. When I boot from the install DVD and type "linux rescue" I eventually get the message, after attempting to have one of the screens mount my partitions in read/write mode:
"An error occurred trying to mount some or all of your system. Some of it may be mounted under /mnt/sysimage." But nothing appears mounted under /mnt/sysimage. Should I try mounting my CentOS 5.5 partitions manually at this point ?
I switch on the PC and it loads the Grub splash screen. However, it does not automatically boot the top entry after two seconds as it's supposed to and just hangs. I hit entry to boot it and it attempts to but after a few seconds gives me the error "unable to mount file system....a maintenance shel will be started" Where do I go from here? to figure out whats going on?
I have a brand new Z97-PRO (Wifi/USB3.1 version) that I got to replace a Gryphon Z87, and it was working great for the first day. I had my Debian and Windows drives both working, and I was working on getting GRUB reinstalled on the Debian drive in no time. At some point I needed to restore my Windows MBR for the millionth time, but this time was different. The Windows logo popped up and froze there. I know this is a thing that sometimes happens, but every other time since I replaced my Gryphon this process only lasted seconds. I let it sit for hours and it didn't move.
I then tried my Debian live USB, which loaded into the main menu, but upon selecting rescue mode it black screened and hung. This was an issue I experienced when I first got the board, but it seemed to work itself out after a few reboots and remained flawless until it just came back. At this point, I'm unable to get in to any of my OSes and I can't seem to successfully boot any external media in order to fix it. My BIOS is totally stock save for secure boot, which is set to Other OS, and memory in XMP mode. I also tried using an Ubuntu Live USB, but ended up hanging with the exact same Q-Codes as in Debian. I am running the system on 1 stick of RAM while testing.
Q-Codes at hang: UEFI USB - AF (Exit Boot Services Event) Regular USB - F6 (Reserved for future AMI progress codes)
Specs: - 2 boot SSDs (OCZ for Windows, Kingston for Debian), 2 storage drives, and a DVD drive. - The boot SSDs occupy SATA ports 1 & 2, the DVD drive takes up 3, and the storage drives take up 5 & 6 - i7 4770K, 32GB (8GBx4) Corsair Dominator RAM, GTX780Ti - 750W Silverstone PSU
I have an ongoing issue that I've not been able to troubleshoot. Upon bootup I get the following text and error, and it stops. ACPI: Aborted because bad gzip magic numbers MP-BIOS bug: 8254 timer not connected to IO-APIC Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
I was using win-7. I tried to install RHEL 6 today. [dual boot]/ = 40000 MB and /boot = 1000 MBThe installation completed successfully.The problem is that it is not showing the graphical mode. Only the terminal mode is available. I tried chvt 1-7but I am unable to go to the graphical mode. It is not appearing.What should I do? System config:MSI CR420 Laptop.ntel core i3-350MEdited after following user76871's answer:There is no Xorg.0.log file in /var/log/, There is no xdm in /etc/init.d/, there is no kdm also.I tried startx that also didn't work. I tried system-config-display but the display is not available at system-config-
I have 4 partitions in my system, out of which two(sda1, sda2) have windows on them. I have installed RHEL 4 32 - bit on sda3 and after that , installed installed RHEL 64-bit on to a partition sda 5. Now i am unable to boot into RHEL 32-bit. The error i am getting is Error 13: Invalid or unsupported executable format.
My linux workstation recently crashed. After rebooting, Linux (Red Hat 5.3) will not boot properly and automatically went into emergency mode or recovery mode i think. I can still see my /home/user/ and all the files inside.I boot from CD to rescue mode and tried mounting read-only the /dev/sd5 which contains the files in the crashed hard disk to try to copy out my files but mounting was unsuccessful (invalid argument). I checked the filesystem type using fsck -N /dev/sda5 and shows it to ext2. i tried to mount another known working hdd and was successful.
My question is why in emergency mode, the crashed hdd is able to be mounted automatically as read-only but cannot be done in rescue mode thru a bootable CD?Is there any special mount options used in emergency mode?I also cannot copy out in emergency mode booting from the crashed hard disk as everything is read only.
Im trying to restore RHEL 5.3 which was previously installed on LVM. I have completly new disks.
1. I have started RHEL install DVD with option: linux rescue 2. set up network 3. connected to NFS server where the backup is stored 4. restored partition image: dd if=/mnt/source/layout.bin of=/dev/sda bs=1024 count=1 (this will preapare partitions like it was before backup. After that it is necessary to run fdisk /dev/sda and choose oprion "w" - write)
Now, I want to create Logical Volumes, but I have no "pvcreate" command in RHEL rescue mode.
After upgrading from 10.04 to 10.10 I have had some problems booting my Ubuntu. It all started when restarting after the upgrade, and I got the error;
mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting / sys/ on root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or dirctory Target filesystem doesn't have /sbin/init. No init found. Try passing init= boot arg
BusyBox v1.13.3 (Ubuntu 1:126.96.36.199ubuntu11) built-in shell (ash)(initramfs) After searching the Internet, I found a "solution". I just had to boot with a USB stick with the Ubuntu Rescue Remix (the normal Ubuntu USB won't boot either), and i wrote;
sudo fsck /dev/sdb5
Now I could start my Ubuntu again. So whats the problem? If I turn off my computer the normal way, there is no problem, but if I log off, put it into sleep mode, if something happens and I have to turn it off with the button it goes back to the first problem, and I have to reboot it with the USB stick and fix it all over again! If I don't have the USB stick with me, I probably wont be able to use my laptop!
I cannot install Kubuntu (or Unbuntu) 10.4 on my husband's computer. I have spent 5 hours on this and cannot get anywhere. I am deeply frustrated. The iso I burned to CD is good (works on 2 other computers). His computer will not boot from USB, no matter what I do to the drive order in BIOS. After loading the blue screen with the Kubuntu logo on it (and the blue-white dots), the screen changes to black and shows the following text:
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash) (initrafs) Unable to find a medium containing a live file system.
He really needs to get rid of WinXP. Kubuntu is what I have on my computer (and love it!). Here is some info about his computer:
OS Name Microsoft Windows XP Home Edition Version 5.1.2600 Service Pack 3 Build 2600 OS Manufacturer Microsoft Corporation
I am running the latest suse release downloaded directly from their website. I ran the installation after buring the dvd and everything seemed to be working fine. after the installation i ran updates and used it for a little bit. When i shut it down that night and went to restart it I got an error that stated the OS wasnt there. I then went through the installation and everything and it retained the information from the installation before (web history etc.) but for some reason every time I reboot or shut it down the system is not able to read the startup information from the hard drive and will not come on without me re installing it.
I started installing the beta of Maverick a few days ago, but the update server was running inordinately slow, so I canceled it. Several times, I have attempted to continue the installation, but I've been unable to reach the server. Shortly after this happened, I could no longer boot normally--I get the error:
Code: Kernel Panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0) Choosing the previous kernel fixes the problem.
So, I obviously want to upgrade to the release version now. When I open the update manager, I get asked if I want to do a partial upgrade to complete the install. I'm a bit leery of doing this since I only have one previous kernel to go back to (my list got really long and I have another operating system entry underneath, so I set my automagic boot manager to only keep two), and if I can no longer boot after the upgrade, I'll have to use Windows until it gets fixed... So, should I finish the upgrade, try to troubleshoot the error, or do something else to jump right to the latest release, after being partway through the upgrade?
I work for a company that makes portable devices running Linux and I was recently asked to make the underlying file system read-only for "security" purposes. Since the distribution is based on LinuxFromScratch, I know that very little writing happens at run time. So, even if the device runs on a usb flash device, I doubt that putting the root file system RO will be that beneficial. I am actually more concerned about a process actually breaking because it cannot open a file in RW mode than a process going rogue and filling the root file system with log files, etc. I'd really like to ear what kind of advantages disadvantages there really is with read-only file-systems.
I'm running window xp and unbuntu 10.04. I ran into a problem where I reinstalled unbuntu by erasing old one under CD boot. During installation, it asked me to place files and i placed it in /. Now when I log in as single user (only user or other at login screen) and try to change any system files, it said I don't have permission. I can't change anything or access root file. I try chmod function and it said i don't have permission as well.
I've created LVMs, and use this after I have added new disks to the system. df -h give me some lines, and one of them looks like this:(this is the system which holds backup files - and I want to disconnect it from time to time to create a duplicate backup)
Problem: When I disconnect this drive, the system will not boot. Gives me the "enter password for root" or click control+D to continue. How can I get around this check - if the disk fails to load, or have been taken out.
Actually Some one has deleted my vmlinuz-2.6.18-164.el5 and its backup vmlinuz5 from /boot dir i want to restore those files. i tried by "linux rescue" mode but unable to mount my dvd from RHEL5 dvd drive there is no file exist as /dev/cdrom .
got a client which rebooted one of their slackware servers and would not come up.Server is stuck at Kernel panic - not syncing: VFS: unable to mount root FS.I have booted into a live cd and mounted hdd1 but have not been able to get any further.
Warning - Windows user who doesn't know much Linux outside of writing programs. Do feel free to patronise providing you explain in detail .
I have a working Windows XP machine. I've installed a second hard drive (channel 1, slave to Windows XP master) and installed Centos (having checksummed the images and verified the media). Problem is it will not boot.
The exact text on screen is...
Booting 'Centos (2.6.18-194.el5)' root (hd1,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.18-194.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
I've managed to use the "Linux rescue" to at least ensure the box default boots to Windows. how to get Centos to boot.
Also, given I told Centos where to install to, and I've not changed anything since, how come it could not even manage to create a working system? Never had this problem on Windows (OK, always on Windows 98 but I never considered that an O/S ).
Im having a serious issue with booting ubuntu 10.04, the issue being it wont boot up at all, after working so well for so long (i suspect some recent dodgy system updates are responsible) so I decided to just reinstall ubuntu from scratch again but wanted to retrieve some important files from my root device. So I am running the live desktop and I can see my previous filesystems under places but cannot mount or open my original root device where the files I want to recover are located, I receive this error msg:"Unable to mount 77 GB Filesystem.
My computer developed a new trick tonight. 4 times in the last 2 hours it's booted & ran fine...for about 30 minutes or so. Then some apps become unstable & crash, and some don't notice anything wrong. Firefox keeps running fine, but if I have a nautilus window open, the next time you click anywhere, it crashes. So, try to restart the machine & it comes back with the "kernel panic -not syncing vfs unable to mount root FS on unknown block" message. The first time I restarted it, I managed to get to a root terminal & fsck the drive. It found 2 errors that it fixed, supposedly. The next collection of restarts, it would just go through bios, then grub, then hang on the error.
So, power down the machine first & then boot it....magically, I'm back to the desktop again for another 30-45 minutes. Anyone have any idea what's going on? It's been fine since the day mint was released...and the only system change was plugging my 2nd monitor back in 3 days ago. Why would it go kukoo in the last 2 hours?The machine is a quad core intel with 4 gigs of ram, Asus mobo and a 250gig sata drive for the system drive.
somehow got Ubuntu 9.10 set up dual boot on my Vista laptop. I installed it somehow off the live cd. Everything working fine and then I decided to update from the update manger to Ubuntu 10.04 (dummy me)!
Got half way through installation and system froze for more than an hour. Had to shut down computer. Now when I select to boot to Ubuntu, computer freezes with this message:
[ 1.068088] Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(8,1)
Can anything, within reason, be done? Should I use windows to uninstall Ubuntu and then try to re-install? If so, can someone tell me how I might have setup dual boot off the live cd? Should I just flog myself?
I can't mount my Ubuntu partition. I was using my PC when it suddenly crashed, so I rebooted. When Ubuntu started again, it said that it was mounting, but I rebooted again. So, now when I start it tries to mount the main partition but it can't. Then appears <initramfs> and I don't know what to do.