Arch Linux

Nagarjuna

Member

Registered: 2010-03-13

Posts: 6

boot fails after pacman -Suy

Today I tried to refresh my system using pacman -Suy
After reboot I get the following message:

:: Checking Filesystems     [BUSY]
/dev/hda4:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

********* FILESYSTEM CHECK FAILED ********************
*
* please repair manually and reboot. Note that the root 
* file system is currently mounted read-only. To remount
* it read-write type: mount -n -o remount,rw /
* When you exit the maintenance shell the system will
* reboot automatically.
*
***************************************************

give root password for maintencance
(or type Control-D to continue):

Running e2fsck -b 8193 /dev/hda4
gives the same error message (except the part within asterixes)

Curiously, "fdisk -l" does not give any output at all!

cat /proc/partitions

major minor #blocks name

3 0 58605120 hda
3 1 15727603 hda1
3 2             1 hda2
3 3    104391 hda3
3 4  5245222 hda4
3 5   618471 hda5
3 6 16418398 hda6
3 7 20490876 hda7

cfdisk gives the following error: "FATAL ERROR: Cannot open disk drive"

cat /etc/mtab:

/dev/hda4 / ext3 rw 0 0
/udev /dev tmpfs rw,nosuid 0 0
none /proc proc rw 0 0
none /sys sysfs rw 0 0

cat /etc/fstab

devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
sys /sys sysfs defaults 0 0

/dev/hda5 swap swap defaults 0 0
/dev/hda4 / ext3 defaults 0 1
/dev/hda3 /boot ext defaults 0 1
/dev/hda6 /home ext3 defaults 0 1

blkid doesnt give any output either, so I cannot find UUIDs to use in my fstab

the /boot folder is empty, probably hasn't mounted,
but through windows I could locate /boot/grub/menu.lst:

timeout 0
default 0
color light-blue/black light-cyan/blue

title Arch Linux
root (hd0,2)
kernel /vmlinuz26beyond root=/dev/hda4 ro
initrd /kernel26beyond.img

Are there perhaps any irregularities in my setup files, I havent been able to spot any
I have tried anything I know!
Can anyone please help me get my system up and running again?

      ~Quinten

ZaQ

Member

Registered: 2009-12-12

Posts: 106

Re: boot fails after pacman -Suy

Did you

mount -n -o remount,rw /

?

When was your last update? What has been updated?

Can you mount your devices with an arch install cd?

Last edited by ZaQ (2010-03-13 16:42:03)