Arch Linux

bloodniece

Member

From: Behind a computer

Registered: 2008-10-03

Posts: 25

Website

[SOLVED] Grub Error 17 and other not so fun stuff

Booted today and greeted by grub error 17.
I booted from Arch Live CD

fdisk -l

looks ok

fdisk  /dev/sdb

x,f,w   nothing done, proper order
ok, let's chroot my install and install grub

mount /dev/sdb1 /mnt

unknown filesystem type, doh

mount -t ext4  /dev/sdb1 /mnt

nope

mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error
       (aren't you trying to mount an extended partition,
       instead of some logical partition inside?)
       In some cases useful info is found in syslog - try
       dmesg | tail

dmesg | tail

attempt to access beyond end of device
sdb1: rw=0, want=4, limit=2
EXT4-fs: unable to read superblock
attempt to access beyond end of device
sdb1: rw=0, want=4, limit=2
EXT4-fs: unable to read superblock

time to fsck ?

Last edited by bloodniece (2009-10-04 15:11:12)

bloodniece

Member

From: Behind a computer

Registered: 2008-10-03

Posts: 25

Website

Re: [SOLVED] Grub Error 17 and other not so fun stuff

I fixed it thanks to testdisk.

When I initially set this install of Arch up I used a whole disk in 2 partitions: / and swap. A grub error 17 led me to believe the partition table was fuxored.  Fdisk did not fix the partition table but it was reporting the root partition as extended, which would not boot and is NOT how I set the system up.  If had been up for about 10 months and working fine.  I was able to use testdisk in a livecd session to both backup my home and etc directories and fix the partition table.

I'm marking this issue fixed.  But I'm still confused as to what the hell happened.  Unclean shutdown?

tripbr

Member

Registered: 2009-10-15

Posts: 5

Re: [SOLVED] Grub Error 17 and other not so fun stuff

I fixed it thanks to testdisk.

When I initially set this install of Arch up I used a whole disk in 2 partitions: / and swap. A grub error 17 led me to believe the partition table was fuxored.  Fdisk did not fix the partition table but it was reporting the root partition as extended, which would not boot and is NOT how I set the system up.  If had been up for about 10 months and working fine.  I was able to use testdisk in a livecd session to both backup my home and etc directories and fix the partition table.

I'm marking this issue fixed.  But I'm still confused as to what the hell happened.  Unclean shutdown?

I'm getting contantly ERROR 17...

I dunno how to fix, I simply reboot some times and it desapears..

If someone could give me a clue..

Thx guyz!