Fedora Linux Support Community & Resources Center
  #1  
Old 25th September 2008, 09:07 PM
wuemura Offline
Registered User
 
Join Date: Aug 2007
Posts: 30
Cool [Solved] Problem with "could not find filesystem /dev/root"

I've switched the motherboard with a very different one that F9 was installed in, the other motherboard was ASUS M2N-e-SLI and i've changed to GIGABYTE GA-MA78GM-S2H, the ASUS one broke down.

After rebuilding the computer this is the error that the system show:

Code:
Loading pata_amd module
Waithing for driver initialization.
Trying to resume from device (/dev/sda7)
Unable to access resume device (/dev/sda7)
Creating root device.
Mounthing root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Mount failed for selinuxfs on /selinux: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Booting has failed
In rescue mode I could check the ' /etc/sysconfig/hwinfo' file and still has information about the other hardware.

How can i update the file, if there is the cause of the problem or how do i change or reset the system so fedora can discard the old configuration and detect an new one that I'm using?

I don't want to format the system since there is nothing wrong with it and I will not learn nothing from this.

Thank you!
__________________
AMD64 X2 4400 - GIGABYTE GA-MA78GM-S2H - 4x1GB DDR2 667 Kingston - 800GB Barracuda SATA2 (RAID 0) - DVDRW SONY DRU830 - Samsung SyncMaster 730MP
Linux Counter #143436

Last edited by wuemura; 26th September 2008 at 03:18 AM.
Reply With Quote
  #2  
Old 25th September 2008, 09:28 PM
lary Offline
Registered User
 
Join Date: Mar 2008
Posts: 2
Perhaps the fsck command may help?
Reply With Quote
  #3  
Old 25th September 2008, 09:50 PM
wuemura Offline
Registered User
 
Join Date: Aug 2007
Posts: 30
I will try fsck and see what it does.
__________________
AMD64 X2 4400 - GIGABYTE GA-MA78GM-S2H - 4x1GB DDR2 667 Kingston - 800GB Barracuda SATA2 (RAID 0) - DVDRW SONY DRU830 - Samsung SyncMaster 730MP
Linux Counter #143436
Reply With Quote
  #4  
Old 25th September 2008, 10:20 PM
wuemura Offline
Registered User
 
Join Date: Aug 2007
Posts: 30
fsck show all related partitions as `clean`.

root partition
Code:
[root@localhost ~]# /sbin/fsck.ext3 /dev/sda8
e2fsck 1.40.8 (13-Mar-2008)
/: clean, 457076/26221536 files, 9068116/26216182 blocks
boot partition
Code:
[root@localhost ~]# /sbin/fsck.ext2 /dev/sda6
e2fsck 1.40.8 (13-Mar-2008)
/boot: clean, 41/128520 files, 39662/514048 blocks
/dev/sda7 is the swap partition
__________________
AMD64 X2 4400 - GIGABYTE GA-MA78GM-S2H - 4x1GB DDR2 667 Kingston - 800GB Barracuda SATA2 (RAID 0) - DVDRW SONY DRU830 - Samsung SyncMaster 730MP
Linux Counter #143436

Last edited by wuemura; 25th September 2008 at 10:30 PM.
Reply With Quote
  #5  
Old 26th September 2008, 02:09 AM
lary Offline
Registered User
 
Join Date: Mar 2008
Posts: 2
Sorry m8, it was just an idea (quite silly on a second thought). I suppose i can't help, I just liked the " I don't want to format the system since there is nothing wrong with it and I will not learn nothing from this." and I 'd really like to see what the answer is. If I come with a better idea I 'll post it.
Reply With Quote
  #6  
Old 26th September 2008, 03:16 AM
wuemura Offline
Registered User
 
Join Date: Aug 2007
Posts: 30
Talking

Looks like i had to solve this by my self, again.

System is working know after taking a closed look at he the boot process to first, understand what is wrong so i know where to "attack" and second fix the problem since "format and reinstall" is not a option.

This is my problem, my old board broke down and I change it with a different new one, since linux was not working I've installed windows XP on a spare partition to keep on working until i had some time to solve this. Since Grub is gone because of windows we had to do a very complex, time consuming recover of the system.

It's kind of a complex solution..... so.... first of all boot you CD/DVD in rescue mode without network and chroot to it:

Code:
chroot /mnt/sysimage
Now is the hard part, try to keep it up

# Dude! Where is my pendrive?
Code:
[root@dragon]# blkid
/dev/sdb1: UUID="A2E2ACB2E2AC8BDB" LABEL="Dados" TYPE="ntfs" 
/dev/sda8: LABEL="/" UUID="3094c537-bc2a-4a9e-8e97-30dffe802896" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sda1: UUID="E6D8E6B2D8E67FE3" LABEL="WIN2003" TYPE="ntfs" 
/dev/sda5: LABEL="SWAP" UUID="7C2F-48E0" TYPE="vfat" 
/dev/sda6: LABEL="/boot" UUID="f86bff6f-31f8-4eca-bbee-4e0bfb694397" SEC_TYPE="ext2" TYPE="ext2" 
/dev/sda7: TYPE="swap" LABEL="SWAP-sda7" UUID="de033a40-d028-43e5-b246-f629fba30d29" 
/dev/sda9: UUID="a7286624-a557-4665-946b-1275cf960bf4" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sdc1: SEC_TYPE="msdos" LABEL="2GPEN" UUID="4876-31F3" TYPE="vfat" 
/dev/sr0: LABEL="Fedora 9 x86_64 DVD" TYPE="iso9660"
Our pendrive is /dev/sdc1.

Now is time to get ready to put our pendrive in good use:

# Backup the thing
Code:
dd if=/dev/sdc of=pendrive_backup.img
# Format
Code:
mkfs.ext3 -v /dev/sdc
# Make some partitions on it, on my 2GB pendrive i've set 1GB for windows use and another 1GB for linux, 1GB is too much for now but you can use the space for some backup or what ever you want.

Code:
fdisk /dev/sdc

Device contains neither a valid DOS partition table, nor Sun, SGI or
OSF disklabel
Building a new DOS disklabel with disk identifier 0x6011d2ff.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): p

Disk /dev/sdc: 2028 MB, 2028994560 bytes
63 heads, 62 sectors/track, 1014 cylinders
Units = cylinders of 3906 * 512 = 1999872 bytes
Disk identifier: 0x6011d2ff

  Device Boot      Start         End      Blocks   Id  System

Command (m for help): n
Command action
  e   extended
  p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-1014, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1014, default 1014): +2018M

Command (m for help): p

Disk /dev/sdc: 2028 MB, 2028994560 bytes
63 heads, 62 sectors/track, 1014 cylinders
Units = cylinders of 3906 * 512 = 1999872 bytes
Disk identifier: 0x6011d2ff

  Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1        1010     1972499   83  Linux

Command (m for help): n
Command action
  e   extended
  p   primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (1011-1014, default 1011):
Using default value 1011
Last cylinder or +size or +sizeM or +sizeK (1011-1014, default 1014):
Using default value 1014

Command (m for help): p

Disk /dev/sdc: 2028 MB, 2028994560 bytes
63 heads, 62 sectors/track, 1014 cylinders
Units = cylinders of 3906 * 512 = 1999872 bytes
Disk identifier: 0x6011d2ff

  Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1        1010     1972499   83  Linux
/dev/sdc2            1011        1014        7812   83  Linux

Command (m for help): t
Partition number (1-4): 1
Hex code (type L to list codes): 6
Changed system type of partition 1 to 6 (FAT16)

Command (m for help): p

Disk /dev/sdc: 2028 MB, 2028994560 bytes
63 heads, 62 sectors/track, 1014 cylinders
Units = cylinders of 3906 * 512 = 1999872 bytes
Disk identifier: 0x6011d2ff

  Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1        1010     1972499    6  FAT16
/dev/sdc2            1011        1014        7812   83  Linux

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.
# Doing what the 'WARNING' said to do, read the man page of fdisk.
Code:
dd if=/dev/zero of=/dev/sdc1 bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.0121442 s, 42.2 kB/s
# Creating a filesystem for eatch partition.
Code:
mkdosfs -F 16 -n "WTUPEN" /dev/sdc1
mke2fs -L "GRUBPEN" /dev/sdc2
# Mount the /dev/sdc2 some place else with:
Code:
mount -t ext2 /media/GRUBPEN
# Making the base directories and copying some grub files on it
Code:
mkdir -p /media/GRUBPEN/boot/grub
cp stage1 stage2 menu.lst grub.conf /media/GRUBPEN/boot/grub
# Installing Grub
Code:
grub-install --no-floppy --root-directory=/media/GRUBPEN /dev/sdc2

Probing devices to guess BIOS drives. This may take a long time.
Installation finished. No error reported.
This is the contents of the device map /media/GRUBPEN/boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

(hd0)/dev/sda
(hd1)   /dev/sdb
(hd2)   /dev/sdc
This part is done, now boot your pendrive, select your kernel and let it boot. In my system i see a error like 'partition not found', press ESQ, press 'e' to edit the line and change this:
Code:
root (hd0,5)
To this:
Code:
root (hd1,5)
Press 'ENTER' and 'b' to boot, soon after the system will get the nice error i've asked help for:
Code:
Loading pata_amd module
Waithing for driver initialization.
Trying to resume from device (/dev/sda7)
Unable to access resume device (/dev/sda7)
Creating root device.
Mounthing root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Mount failed for selinuxfs on /selinux: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Booting has failed
Since the system had passed the Start UP > Stage 1 Bootloader > Stage 2 Bootloader > Kernel stage, it never gets to 'init' part because linux is not able to mount any partition:
http://www.ibm.com/developerworks/li...y/l-linuxboot/

If linux is not getting any info from the partitions, the error is located some place else attached to kernel, it's not System.map because inside there are only symbols, so is the initrd file.

http://en.wikipedia.org/wiki/Initrd
The initial ramdisk, or initrd is a temporary file system commonly used by the Linux kernel during boot. The initrd is typically used for making preparations before the real root file system can be mounted.

And there we go....

Code:
[root@dragon ~]# cd /boot
[root@dragon boot]# mkdir tmp
[root@dragon boot]# cp initrd-2.6.25.11-97.fc9.x86_64.img tmp
[root@dragon boot]# cd tmp
[root@dragon tmp]# gzip -dc /boot/initrd-2.6.25.11-97.fc9.x86_64.img | cpio -id
14333 blocks
[root@dragon tmp]# vi init
skipping the boring part...
echo "Loading sata_nv module"
modprobe -q sata_nv
The part in red is the problem, we don't need it anymore.
This is how we do it:
Code:
[root@dragon ~]# cd /boot
[root@dragon boot]# mv initrd-2.6.25.11-97.fc9.x86_64.img initrd-2.6.25.11-97.fc9.x86_64.old
[root@dragon boot]# mkinitrd initrd-2.6.25.11-97.fc9.x86_64.img 2.6.25.11-97.fc9.x86_64
This will solve the problem because the new initrd will have the working module that we need, now to finish the job 100% we need to recover Grub since the Windows installation messed that up, this is hard work so, pay attention.
__________________
AMD64 X2 4400 - GIGABYTE GA-MA78GM-S2H - 4x1GB DDR2 667 Kingston - 800GB Barracuda SATA2 (RAID 0) - DVDRW SONY DRU830 - Samsung SyncMaster 730MP
Linux Counter #143436
Reply With Quote
  #7  
Old 26th September 2008, 03:16 AM
wuemura Offline
Registered User
 
Join Date: Aug 2007
Posts: 30
Cool

Now reboot the system, boot your pendrive, edit the partition again so Fedora 9 will boot without the errors, to get grub fixed make sure you know exactly where the /boot partition is located, if you get this far and still don't, do the follow:
Code:
[root@dragon ~]# blkid
/dev/sdb1: UUID="A2E2ACB2E2AC8BDB" LABEL="Dados" TYPE="ntfs" 
/dev/sda8: LABEL="/" UUID="3094c537-bc2a-4a9e-8e97-30dffe802896" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sda1: UUID="E6D8E6B2D8E67FE3" LABEL="WIN2003" TYPE="ntfs" 
/dev/sda5: LABEL="SWAP" UUID="7C2F-48E0" TYPE="vfat" 
/dev/sda6: LABEL="/boot" UUID="f86bff6f-31f8-4eca-bbee-4e0bfb694397" SEC_TYPE="ext2" TYPE="ext2"
/dev/sda7: TYPE="swap" LABEL="SWAP-sda7" UUID="de033a40-d028-43e5-b246-f629fba30d29" 
/dev/sda9: UUID="a7286624-a557-4665-946b-1275cf960bf4" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sdc1: SEC_TYPE="msdos" LABEL="WTUPEN" UUID="4876-31F3" TYPE="vfat" 
/dev/sdc2: LABEL="GRUBPEN" UUID="e01aa86d-2071-4f6a-b3bf-ddf13ff4716c" TYPE="ext2" 
/dev/sr0: LABEL="Fedora 9 x86_64 DVD" TYPE="iso9660"
/dev/sda is where we need to fix, so:
Code:
[root@dragon ~]# grub-install /dev/sda
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

# this device map was generated by anaconda
(hd0)     /dev/sda
Reboot.

Job done, i can see grub menu, system is working 90% (need to reconfigure some stuff but is working), now I'm back here using Fedora 9 again.

Enjoy the the solution.
__________________
AMD64 X2 4400 - GIGABYTE GA-MA78GM-S2H - 4x1GB DDR2 667 Kingston - 800GB Barracuda SATA2 (RAID 0) - DVDRW SONY DRU830 - Samsung SyncMaster 730MP
Linux Counter #143436

Last edited by wuemura; 26th September 2008 at 03:32 AM.
Reply With Quote
Reply

Tags
problem

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
"WARNING: Cannot find root file system", when F10 Live CD boots. cybercytes Installation, Upgrades and Live Media 1 27th January 2009 10:37 AM
"WARNING: Cannot find root file system!" when booting Live CD Lollan Installation, Upgrades and Live Media 1 5th December 2007 06:14 AM
Yet another "could not find filesystem '/dev/root' " problem on F7. [H]omer Installation, Upgrades and Live Media 5 4th June 2007 02:49 AM
FC6: "mount: could not find filesystem '/dev/root'" bthornton EOL (End Of Life) Versions 5 14th November 2006 07:40 PM
FC5 Xen Boot "could not find filesystem 'dev/root'" chuckbrazie EOL (End Of Life) Versions 0 14th September 2006 03:30 PM


Current GMT-time: 23:54 (Sunday, 21-12-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat
...Starbucks Photos on Instagram - Mina La Valenciana Photos - St. Charles Streetcar