View previous topic :: View next topic |
Author |
Message |
Shining Arcanine Veteran

Joined: 24 Sep 2009 Posts: 1110
|
Posted: Fri Nov 06, 2009 4:28 am Post subject: I executed rm /dev/sda* as root... |
|
|
I installed Gentoo Linux on a VMWare Player virtual machine on my laptop (x86).
I followed the handbook fairly well until I had to install LILO. I was half asleep at this time and deleted /dev/sda* as root in my chrooted environment. I tried rebooting into Linux (as I had just finished installing it) and I am receiving the error "VFS: Cannot open root device "803" or unknown block(8,3)".
It also says "Please append a correct "root=" option; here are the available partitions:", with the only thing following it being "0b00 1048575 sr0 driver: sr", which does not appear to be a partition to me. It then continues to talk about kernel panic.
I installed a virtual machine on my desktop and it turned out that the minimal install CD I was using was using /dev/hda while my installation used /dev/sda, so without thinking, I tried symlinking /dev/hda to /dev/sda (with the corresponding partitions being symlinked too), without realizing that the LiveDVD that I was using used /dev/sda by default. A long story short, I seem to have damaged my MBR before even being able to boot my system. I have went into the LiveDVD again, re-established the chroot environment and ran /sbin/lilo without any complaints from it (which is something I could not do after goofing on the original LiveDVD session).
Could someone please advise me on what to do? The only solution I can think of that I did not try is to start from scratch, but I would prefer to fix my mistake over recompiling the virtual machine for more than a day. |
|
Back to top |
|
 |
Mike Hunt Watchman


Joined: 19 Jul 2009 Posts: 5287
|
Posted: Fri Nov 06, 2009 7:25 am Post subject: |
|
|
It would probably be better to start over, and if your experimentations fail again, then start over again. Trying all kinds of installation techniques is one of the fun things that can be done with Gentoo that isn't really doable with any other OS.
When all else fails, follow the Gentoo Handbook, and you'll be fine.
Have fun.  |
|
Back to top |
|
 |
Hu Administrator

Joined: 06 Mar 2007 Posts: 23517
|
Posted: Sat Nov 07, 2009 3:01 am Post subject: |
|
|
Starting from scratch is overkill, and probably not very fun when working with the reduced computing power of a virtual machine running on a laptop.
sr is the optical drive. Your problem is unrelated to your deletion of the device nodes. Modern Linux systems typically use a dynamic /dev, so rebooting repopulates the /dev directory. Your problem is that you omitted kernel support for your hard drive. Boot the LiveDVD and run lspci -k to find the name of the kernel driver for your hard drive. |
|
Back to top |
|
 |
Mike Hunt Watchman


Joined: 19 Jul 2009 Posts: 5287
|
Posted: Sat Nov 07, 2009 8:48 am Post subject: |
|
|
Ok, I didn't realize that rm /dev/sda* only removes the device nodes and not the contents of the drive. So of course there is no need to start over.  |
|
Back to top |
|
 |
Hu Administrator

Joined: 06 Mar 2007 Posts: 23517
|
Posted: Sat Nov 07, 2009 5:30 pm Post subject: |
|
|
Right. If he had written anything to any of those device nodes first, the data would have gone onto his drive and potentially caused massive corruption. Simply deleting the device node is quick and safe, but it is not useful. |
|
Back to top |
|
 |
Shining Arcanine Veteran

Joined: 24 Sep 2009 Posts: 1110
|
Posted: Fri Nov 20, 2009 7:57 pm Post subject: |
|
|
Hu wrote: | Starting from scratch is overkill, and probably not very fun when working with the reduced computing power of a virtual machine running on a laptop.
sr is the optical drive. Your problem is unrelated to your deletion of the device nodes. Modern Linux systems typically use a dynamic /dev, so rebooting repopulates the /dev directory. Your problem is that you omitted kernel support for your hard drive. Boot the LiveDVD and run lspci -k to find the name of the kernel driver for your hard drive. |
That turned out to be the program. I found a guide via Google that had information what needs to be enabled in the kernel for a VMWare Virtual Machine to work and fixed it, although I did so only after I started over from scratch and still had the same problem. :/ |
|
Back to top |
|
 |
Mike Hunt Watchman


Joined: 19 Jul 2009 Posts: 5287
|
Posted: Sat Nov 21, 2009 3:23 pm Post subject: |
|
|
Shining Arcanine wrote: | ... although I did so only after I started over from scratch and still had the same problem. :/ |
Oops, my bad, sorry.  |
|
Back to top |
|
 |
Shining Arcanine Veteran

Joined: 24 Sep 2009 Posts: 1110
|
Posted: Mon Nov 23, 2009 4:05 pm Post subject: |
|
|
Mike Hunt wrote: | Shining Arcanine wrote: | ... although I did so only after I started over from scratch and still had the same problem. :/ |
Oops, my bad, sorry.  |
Don't worry about it. Any amount of work on a computer is a learning experience.
Although to be honest, times like these (and my computer science assignments) make me wish I had the neutral-scan interface from Star Trek:
http://memory-alpha.org/en/wiki/The_Nth_Degree |
|
Back to top |
|
 |
|