No volume groups found Volume group" VolGroup00" not found Unable to access resume device mount: could not find filesystem 'devroot' I can boot in rescue mode, chroot to the installed system. Subject: Re: unable to access sda2 on boot SOLVED Date: Tue, 10 Apr 2007 14: 36: 20 0400 Easy fix, just put the install cd in and told it to update, it fixed the boot information as it returned the system to its original state, but still kept all my settingsfiles, did have to reinstall some drivers tho.
While changing box, it is highly likely that your disks no longer have the same device name as viewed by Linux. This could be because the driver is a different one, or they are just numbered differently. In any case, the disk that used to be devhda may now be devsdb, or something else. Dec 21, 2008 By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.
Registration is quick, simple and absolutely free. Oct 23, 2009 Fedora: 1: 11: 50 AM: Booting stops after: Unable to access resume device, mount: could not mount lespaul047: Linux Newbie: 2: 05: 50 PM: Unable to resume device: tekmann33: Linux Newbie: 6: 04: 39 PM: Unable to access resume device: jdege: Linux General: 9: 10: 32 Red Hat Fedora: : Unable To Access Resume Device Red Hat Fedora: : Mailserver Have To Have Direct Access To WAN Or Can It Be A LAN Device With Just One NIC?
Hardware: : Possible To Access An IrDA Device As A Serial Device I experienced this: Unable to access resume device (devdm2) mount: could not find filesystem 'devroot' after 1. using the GUI 'ntfsconfig which had generated a new etcfstab file (and thankfully left a useful turd at and then before rebooting 2.