CentOS 5 :: Mount: Could Not Find Filesystem /dev/root?
Jun 27, 2009
I have successful tar an existing CentOS 5.2 partition from Fefora10. The idea is to move a working CentOS 5.2 reside in an internal hard drive to a portable hard drive. I know how to edit a stencil in menu.lst to boot the clone CentOS5.2. During boot, I encountered
Red Hat nash version 5.1.19.6
mount: could not find filesystem /dev/root
setuproot: moving /dev failed No such file or directory
setuproot: mounting /proc: No such file or directory
setuproot: mounting /sys: No such file or directory
I had a LiveUSB of CentOS 5.5, so I decided the install it.With no installer,I just copied the files to my hard drive.his was in a multi boot with Windows 7, Ubuntu 9.10, and FreeDOS.I updated GRUB2 and it detected CentOS. I loaded my entry and it failed to mount the root filesystem.I took the initrd0 file from the LiveUSB syslinux folder and added that ramdisk to the entry. Now it finds the root filesystem (/dev/sda9 as Ext3).But it fails shortly after loading /sbin/init. It talks about an init error where it says "File not found!!!".The previous lines involved umounting old filesystems, like /dev.
When I try to boot to OpenSUSE I get the following error during boot-up: unknown filesystem type 'reiserfs' could not mount root filesystem - exiting to /bin/sh$
This only started happening quite recently - before this I could boot to Linux quite happily.
I am running 11.2, kde4. The day before yesterday, the system updated and I think there was kernal update within that. I had no problems immediately afterward. Then I did a total shutdown for the night, and turned it back on yesterday only to find this:
Mount: wrong fs, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error In some cases useful info is found in syslog--try dmesg | tail or so Could not mount root filesystem--exiting to /bin/sh sh: cannot set terminal process group (-1): Inappropriate ioctl for device sh: no job control in this shell $
Besides the last updates from the other day, I did nothing out of the ordinary, no downloads or any system/configuration tweeks. Will I have to reinstall opensuse? or is there a way to reclaim my previous setup--or at least reclaim my files and documents? I'm running off of the 11.2 livecd.
I have a dual booting newly installed 64 bit Ubuntu 9.10 on my machine. It was all fine until today. Now when I boot into Ubuntu, I see the error Failed to mount root filesystem. I cant remember any significant changes during the last session. One thing I remember is I upgraded the system using the update manager which asked me to choose an option for grub boot loader. I opted for its upgradation. After the upgrade, I was able to work with Ubuntu for a few more sessions. Windows XP works very fine.I checked other threads which suggested running fsck, but it did not help. fsck does not report any errors.
I am using GRUB bootloader. I can boot into windows fine. But booting into linux gives me the error "kernel panic: unable to mount root fs on unknown block(0,0)I got LILO to load linux fine but GRUB always gives me this error regardless of the linux OS for this particular computer.
Running F12 on my compaq evo N410c. Did a system restart 4rm gnome logged in as root & now grub cant mount my root filesystem, it boots vista though. How do i rectify dis.
I have just tried to update my kernel from 2.6.24.5 to 2.6.39-rc3 on a Slackware 12.1 distribution. I have successfully updated the kernel before, but it was from a newer distribution and newer kernel(Slackware 13.1 and 2.6.33.4). After I updated and rebooted, I got the following error:
Code: List of all partitions: 0300 4194302 hda driver: ide-cdrom 0800 312571224 sda driver: sd 0801 244197560 sda1 00000000-0000-0000-0000-000000000sda1 0802 68372640 sda2 00000000-0000-0000-0000-000000000sda2 No filesystem could mount root, tried: romfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (8,1) Pid: 1, comm: swapper Not tainted 2.6.39-rc3-smp #1 .....
I am a linux semi-noob who just got the idea that it would be fun to play with Arch Linux.I was dual-booting Windows and OpenSuSE, and I installed Arch by shrinking the Windows partition and putting a new logical partition in between the windows partition and the swap partition I already have.Unfortunately, opensuse still thinks that its root filesystem is on /dev/sda7 so it fails to boot b/c it is looking at an ntfs filesystem that I used for document sharing.If someone has a solution, that will save me from having to reinstall opensuse.
My Fedora 12 System was failed when booting.The message like that : mount: wrong fs type, bad option, bad superblock on /dev/mapper/my_vol missing codepage or helper program, or other error. In some case, useful info is found in syslog - try dmesg | tail or so Can't mount at root filesystem. [drm: drm_mode_rmfb ] *ERROR* tried to remove a fb that we didn't own. Boot has failed, sleep forever. I guess something wrong with my hard disk, so the bootloader can't recognize the filesystem type.
I'm trying to boot Emdebian Grip 1.0 built on Compact Flash on a mini PC with grub2 as bootloader. Unfortunately , the booting is unsuccessful and I got stuck into an error message :Code:No filesystem could mount root , tried : minix msdos iso9660kernel panic - not syncing : VFS : Unable to mount root fs on unknown-block (22,1)It seems grub2 hasn't tried to mount ext2 as the filesystem and my Compact flash is formatted as ext2. Here is the menuentry of the grub.cfg :
Code: menuentry "Debian GNU/Linux, linux 2.66.2.9-custom" { insmod ext2
i made a live usb stick with a original live iso image of f10 following carefully instructions of fedora support comunity once i finished i had tested it and i had the same problem (warning can not find root filesystem create symlink /dev/root and then exit this shell to continue the boot sequence, bash: no job control in this shell) of the following person:
I have opensuse 11.3 installed, and my motherboard has the intel i845 chipset, one day windows had enough of the intel graphics chip and would not let me have anything but 640x480 pixels, well you cant do much with that so I put an ati card in and disabled the intenal graphics. windows was happy enough but suse could not boot - more specifically could not mount the root filesystem, saying it had errors (did a very quick fsck), could not find the journal, and I had a bad superblock. the "failsafe kernel" was no better. If I take the ati card out suse boots fine. however I do swap frequently between windows and linux and changing graphics cards between boots is somewhat irritating.
A friend of mine upgraded his pc to ubuntu 10.04. Sadly enough we ran into issues with his graphics card, which apparently doesnt work well with lucid. We decided to downgrade to 9.10. I did this by installing over the old partition and chose to import the settings from the old account.The problems started when the pc booted for the first time:The list of kernels in grub2 was the one from 10.04.Somehow grub2 from the old installation seems to be still around and messes everything up. Any ideas how I could fix this?
I decided to try to do the 3 distro upgrade stretch from 8.04 to 10.04 this weekend and now I am hung on 9.04 to 9.10.. The upgrade went swimmingly, but I hit a wall upon boot. When I try to load kernel 2.6.31-22 I am greeted with the following error:
Code:
[ 20.879845] ACPI: I/O resource vt596_smbus [0x400-0$407] conflicts with ACPI region SMOV [0x400-0x406] Mount of root filesystem failed.
A maintenance shell will now be started ... After doing some digging I found this thread which appears to be similar in the inability to mount the filesystem. However, it does not mention the ACPI error. I tried everything in that thread; verifying device ID's, editing fstab options; running a filesystem check, and flipping the UTC option in the rcS file but nothing worked. The OP of that thread eventually did a fresh install of Karmic; but I would rather not have to go that far.
I've downloaded Fedora 12 and decided to try and install it on my old laptop which is currently running Ubuntu 9.10 with no problems.
When I boot from the live cd, it starts to load with the 3 bars on the bottom, one on top of the other, one is white, one is dark blue, the other is in between those colours in the spectrum somewhere....
Anyway, the load bars complete and "Fedora 12" turns white, then the following output populates:
mount: unknown filesystem type 'DM_Snapshot_Cow' (<----- repeated a bunch of times) can't mount root filesystem Boot has failed, sleeping forever.
I've upgraded my squeeze box to linux kernel 2.6.32-5. But it shows mounting "here is the uuid of / " on /root failed: Device or resource busy while booting.Here is the menuentry of linux kernel 2.6.32-5.
Summary of issue: EXT4 filesystem won't mount--with error = mount: unknown filesystem type 'ext4'. Is no ext4 in kernel the issue? Or is something corrupted?Really perplexed by this. I updated Centos 5.5 to 5.6 to get ext4 (5.6 is supposed to have full support of ext4). I built several arrays and put the ext4 filesystem on them. All went well until I tried to mount them. BTW, this array (below) is set up as a RAID6 using partition 1 of #8 2TB drives.Bear with me here; just trying to be complete and not waste your time.
Attempting to mount give this:[root]# mount -v /dev/md1 /asc/array1mount: unknown filesystem type 'ext4'Note: it does "fake" mount with ption (which apparently does everything except the system call):[root]# mount -f -v /dev/md1/dev/md1 on /asc/array1 type ext4 (rw,grpquota,usrquote)e2fsprogs:Package e2fsprogs-1.39-23.el5_5.1.x86_64 already installed and latest version (for Centos 5.6; CentOS 6x uses the 1.41...)
today I upgraded (yum update) one of my Dell Poweredge Server from 5.2 to 5.3. After rebooting the system first seems to start normal but then the following Error Messages appear:
Apr 5 14:28:26 srv_1 kernel: I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x668000008 ("xfs_trans_read_buf") error 5 buf count 4096 Apr 5 14:28:26 srv_1 kernel: attempt to access beyond end of device Apr 5 14:28:26 srv_1 kernel: dm-0: rw=0, want=27514634256, limitfs]
[code]....
Booting with a rescue disk and doing a xfs_repair solves the file system Problems but moved a lot of files ( at least /usr/bin and /usr/lib completly) to "lost+found"... I tried the update with a spare 5.2 Server (different Hardware), and ended up with exactly the same effect and error message. Both systems are running XFS as root File system on an LVM Disk.
Ive setup a filesystem on a RAID 0+1 and am looking at moving root filesystem from a single disk to the new one. I could not install CentOS on mirrored filesystem as the RAID card did not have a pre-built driver for CentOS 5.3, so I had to compile the driver after installing the system.
What Im going to do now is:
1.Mount the new mirrored filesystem under /root1 2.use find | cpio to copy everything from the existing / to /root1 3.use grub to create a boot record on /root1 4.edit /root1/etc/fstab to point / to the new disk 5. reboot the system and keep my fingers crossed
I was looking at the root filesystem folder for mounting a device when I noticed extra folders. I'm using an encrypted filesystem so I'm not sure if it's that, a break in or the default Red Hat layout. I searched these forums and Google to no avail on extra folders. The root system contains the following:
bin {fda00e13-8c62-4f63-9d19-d168115b11ca} media opt selinux usr boot home misc proc srv var dev lib mnt root sys etc lost+found net sbin tmp
I have a CIFS share mounted from the "Places" menu and it is accessible from the desktop.I am unable to find its location in the filesystem using "mount" Where does it get mounted to?
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
[Code]....
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 ).
I want to upgrade kernel to 2.6..36 from 2.6.18 of CentOS 5.5. The make process is successful but prompt "could not find filesystem /dev/boot " after reboot.
Some articles suggest to edit file .config and set CONFIG_SYSFS_DEPRECATED_V2 to 'y' and re-make kernel. However, the problem still stand there after reboot again.
My linux distro is CentOS 5.3. Today I edited /etc/sysconfig/readonly-root and set "READONLY" to yes, now my /etc/sysconfig/readonly-root file is like this:
# Set to 'yes' to mount the system filesystems read-only. READONLY=yes # Set to 'yes' to mount various temporary state as either tmpfs
I installed Ubuntu Server 9.10 in a virtual machine, and I'm trying to install the VMware Tools but I can't mount the installer CD: $ sudo mount /dev/scd0 /media/cdrom mount: unknown filesystem type 'iso9660'
I used the ntfs-config utility to mount my windows drives automatically at startup. While doing so, I had my USB-HDD still attached, and after making changes and rebooting, it did something unknown I didn't expect and I cannot mount my USB-HDD again, and it gives me the following error message:
Error mounting: mount exited with exit code 1: helper failed with: mount: only root can mount /dev/sdb1 on /media/MyUSBDrive
I did manage to open it somehow, but then all the data was erased apart from ~3 GiB [edit: it's got some kind of extra drive built-in which is mounted as a CD-ROM drive, and when I open that one first all the files are missing in the actual drive, otherwise I get the message above]. I don't know what information I should include here, but my fstab looks like this:
fuse: failed to access mountpoint /media/sdb1: No such file or directory
What should I do to recover my files and fix the mount error? [edit: at the very least, how do I backup my files onto my internal HDD so I can format it and recover it in this manner]
I'm having some trouble with my Ubuntu 10.04. It had been working normally, and now my startup isn't occurring normally. The bootloader shows my Windows install and two different revisions of Ubuntu. Upon letting it load Ubuntu, however, it goes to BusyBox v1.13.3 and says "built in shell (ash)" and presents me with a functioning command line.
I'm comfortable with working on the command line, but does anyone know where to start with this?
i used opensuse 11.1 ...there is option for root user to create password for root...but for ubuntu i did not find anything like that...so how can i create root password....or how can i use root
