You are not logged in.

#1 2011-12-04 02:51:57

bicyclingrevolution
Member
Registered: 2010-10-18
Posts: 71

Contents of /dev erased and system can't boot

After updating my system and running Bleachbit, I rebooted to find it can't find /dev/sdb1, my root partition, and therefore cannot boot. Using a live cd I discovered /dev has exactly three files: console, null, and zero. How do I recover my deleted devices--from a live cd?

Offline

#2 2011-12-04 03:16:52

anrxc
Member
From: Croatia
Registered: 2008-03-22
Posts: 834
Website

Re: Contents of /dev erased and system can't boot

mknod /dev/console, /dev/null, /dev/zero and /dev/sda from a live environment and udev will take care of the rest.


You need to install an RTFM interface.

Offline

#3 2011-12-04 03:47:55

bicyclingrevolution
Member
Registered: 2010-10-18
Posts: 71

Re: Contents of /dev erased and system can't boot

I ran this:

cd /mnt/sdb1/dev/
mknod sda b 8 0
mknod sdb b 8 16
mknod sdb1 b 8 17

and it still will not boot.

Offline

#4 2011-12-04 03:57:09

bohoomil
Member
Registered: 2010-09-04
Posts: 2,376
Website

Re: Contents of /dev erased and system can't boot

Look elsewhere for the problem; /dev is populated automatically and you don't have to manually re-create its content. Is everything set correctly in your grub config file? When you boot from live CD, can you mount your partitions and list their content?


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#5 2011-12-04 04:03:27

bicyclingrevolution
Member
Registered: 2010-10-18
Posts: 71

Re: Contents of /dev erased and system can't boot

Everything mounts fine from a live cd. I see no problems in grub. I tried making grub boot using root=/dev/sda1 but that made no difference. Fstab is set up properly. I have no idea what the problem could be, other than /dev failing to be populated properly.

Offline

#6 2011-12-04 04:14:33

bohoomil
Member
Registered: 2010-09-04
Posts: 2,376
Website

Re: Contents of /dev erased and system can't boot

What output do you get from grub when you reboot? On which disk and partition(s) do you have your Arch installation? (In the first post, you mention /dev/sdb1, which suggests a second hard drive, but then you mention /dev/sda1 which is physically a different device.) Do you have /boot on a separate partition?

Last edited by bohoomil (2011-12-04 04:51:47)


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#7 2011-12-04 06:35:00

bicyclingrevolution
Member
Registered: 2010-10-18
Posts: 71

Re: Contents of /dev erased and system can't boot

I am using grub from an install on another disk, sda6. That install boots up fine, while my newer install on sdb1 fails with a message something like this:

Waiting 10 seconds for /dev/sdb1...
Root device '/dev/sdb1' does not exist, attempting to create it...
Could not create device, dropping to a recovery shell.

I tried editing grub to use /dev/sda1 for root because I thought the disks might have switched, but that is not the case, since the same grub will boot off sda6 just fine. Also, editing grub resulted in the exact same error message when booting the sdb1 system with root=/dev/sda1, only the error said sda1 instead of sdb1.

Offline

Board footer

Powered by FluxBB