Re: GPT messed up, cant boot or access harddrive
fdisk still claims the drive to have a GPT, Partitions look good
Code:
ubuntu@ubuntu:~$ sudo fdisk -l /dev/sda
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 280582 1304581 512000 83 Linux
/dev/sda2 118786048 186845207 34029580 83 Linux
/dev/sda3 186845208 250069679 31612236 83 Linux
Parted doesnt complain:
Code:
ubuntu@ubuntu:~$ sudo parted /dev/sda unit s print
Model: ATA SAMSUNG SSD 830 (scsi)
Disk /dev/sda: 250069680s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 280582s 1304581s 1024000s primary ext4
2 118786048s 186845207s 68059160s primary ext4
3 186845208s 250069679s 63224472s primary
Mounting does not work:
Code:
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Output of dmesg is:
Code:
[18980.898605] EXT4-fs (sda1): ext4_check_descriptors: Block bitmap for group 0 not in group (block 4294967294)!
[18980.898611] EXT4-fs (sda1): group descriptors corrupted!
Re: GPT messed up, cant boot or access harddrive
Doesn't look good. That partition looked like the most likely to be intact. Try the other two.
Re: GPT messed up, cant boot or access harddrive
Well sda2 seems to work, sda3 doesnt:
Code:
ubuntu@ubuntu:~$ sudo mount /dev/sda2 /mnt
ubuntu@ubuntu:~$ sudo mount /dev/sda3 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
dmesg for those two look more promising:
Code:
[18926.257673] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[18942.384760] EXT4-fs (sda3): bad geometry: block count 15800064 exceeds size of device (7903059 blocks)
How can I access the data on sda2? "mount -l" says its mounted on /mnt, but I cant find it anywhere.
Re: GPT messed up, cant boot or access harddrive
The error is because the size of the partition is too large for the size of the filesystem.
Re: GPT messed up, cant boot or access harddrive
I think a different mount point would be better? This seems like something from the live OS
Code:
ubuntu@ubuntu:~$ ll /mnt/
total 118441
drwxr-xr-x 5 root root 4096 Dec 5 21:10 ./
drwxr-xr-x 1 root root 260 Jan 4 14:19 ../
-rw-r--r-- 1 root root 919745 Sep 10 22:29 abi-3.8.0-31-generic
-rw-r--r-- 1 root root 919810 Oct 23 11:42 abi-3.8.0-33-generic
-rw-r--r-- 1 root root 919810 Nov 12 19:28 abi-3.8.0-34-generic
-rw-r--r-- 1 root root 154960 Sep 10 22:29 config-3.8.0-31-generic
-rw-r--r-- 1 root root 154961 Oct 23 11:42 config-3.8.0-33-generic
-rw-r--r-- 1 root root 154961 Nov 12 19:28 config-3.8.0-34-generic
drwxr-xr-x 2 root root 1024 Nov 1 2012 efi/
drwxr-xr-x 5 root root 1024 Jan 2 19:25 grub/
-rw-r--r-- 1 root root 30796589 Sep 28 11:17 initrd.img-3.8.0-31-generic
-rw-r--r-- 1 root root 30799018 Nov 11 17:50 initrd.img-3.8.0-33-generic
-rw-r--r-- 1 root root 30800042 Dec 3 09:18 initrd.img-3.8.0-34-generic
drwx------ 2 root root 12288 Nov 1 2012 lost+found/
-rw-r--r-- 1 root root 176764 Dec 5 2012 memtest86+.bin
-rw-r--r-- 1 root root 178944 Dec 5 2012 memtest86+_multiboot.bin
-rw------- 1 root root 3062541 Sep 10 22:29 System.map-3.8.0-31-generic
-rw------- 1 root root 3062707 Oct 23 11:42 System.map-3.8.0-33-generic
-rw------- 1 root root 3062653 Nov 12 19:28 System.map-3.8.0-34-generic
-rw------- 1 root root 5362320 Sep 10 22:29 vmlinuz-3.8.0-31-generic
-rw------- 1 root root 5364816 Oct 23 11:42 vmlinuz-3.8.0-33-generic
-rw------- 1 root root 5364080 Nov 12 19:28 vmlinuz-3.8.0-34-generic
Re: GPT messed up, cant boot or access harddrive
Ok, created a differnent folder for the mount point and it seems to be the correct content. But the efi/ folder is empty.
Re: GPT messed up, cant boot or access harddrive
This is a /boot partition. It may or may not be the correct one. It's worth taking a look at grub/grub.cfg.
Unfortunately, we still haven't found / or /home, tho.
Re: GPT messed up, cant boot or access harddrive
I remember the "Windows" entry at the end of the grub.cfg. Seems to be mine.
Code:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6 5bb9b055-184d-4fd5-acf7-90c295e94ca2
else
search --no-floppy --fs-uuid --set=root 5bb9b055-184d-4fd5-acf7-90c295e94ca2
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
clear
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ "${recordfail}" != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-5bb9b055-184d-4fd5-acf7-90c295e94ca2' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 849ea212-8008-42f4-b440-f67f8a8687be
else
search --no-floppy --fs-uuid --set=root 849ea212-8008-42f4-b440-f67f8a8687be
fi
linux /vmlinuz-3.8.0-34-generic root=UUID=5bb9b055-184d-4fd5-acf7-90c295e94ca2 ro quiet splash $vt_handoff
initrd /initrd.img-3.8.0-34-generic
}
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-5bb9b055-184d-4fd5-acf7-90c295e94ca2' {
menuentry 'Ubuntu, with Linux 3.8.0-34-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.8.0-34-generic-advanced-5bb9b055-184d-4fd5-acf7-90c295e94ca2' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 849ea212-8008-42f4-b440-f67f8a8687be
else
search --no-floppy --fs-uuid --set=root 849ea212-8008-42f4-b440-f67f8a8687be
fi
echo 'Loading Linux 3.8.0-34-generic ...'
linux /vmlinuz-3.8.0-34-generic root=UUID=5bb9b055-184d-4fd5-acf7-90c295e94ca2 ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.8.0-34-generic
}
menuentry 'Ubuntu, with Linux 3.8.0-34-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.8.0-34-generic-recovery-5bb9b055-184d-4fd5-acf7-90c295e94ca2' {
recordfail
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 849ea212-8008-42f4-b440-f67f8a8687be
else
search --no-floppy --fs-uuid --set=root 849ea212-8008-42f4-b440-f67f8a8687be
fi
echo 'Loading Linux 3.8.0-34-generic ...'
linux /vmlinuz-3.8.0-34-generic root=UUID=5bb9b055-184d-4fd5-acf7-90c295e94ca2 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.8.0-34-generic
}
menuentry 'Ubuntu, with Linux 3.8.0-33-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.8.0-33-generic-advanced-5bb9b055-184d-4fd5-acf7-90c295e94ca2' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 849ea212-8008-42f4-b440-f67f8a8687be
else
search --no-floppy --fs-uuid --set=root 849ea212-8008-42f4-b440-f67f8a8687be
fi
echo 'Loading Linux 3.8.0-33-generic ...'
linux /vmlinuz-3.8.0-33-generic root=UUID=5bb9b055-184d-4fd5-acf7-90c295e94ca2 ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.8.0-33-generic
}
menuentry 'Ubuntu, with Linux 3.8.0-33-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.8.0-33-generic-recovery-5bb9b055-184d-4fd5-acf7-90c295e94ca2' {
recordfail
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 849ea212-8008-42f4-b440-f67f8a8687be
else
search --no-floppy --fs-uuid --set=root 849ea212-8008-42f4-b440-f67f8a8687be
fi
echo 'Loading Linux 3.8.0-33-generic ...'
linux /vmlinuz-3.8.0-33-generic root=UUID=5bb9b055-184d-4fd5-acf7-90c295e94ca2 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.8.0-33-generic
}
menuentry 'Ubuntu, with Linux 3.8.0-31-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.8.0-31-generic-advanced-5bb9b055-184d-4fd5-acf7-90c295e94ca2' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 849ea212-8008-42f4-b440-f67f8a8687be
else
search --no-floppy --fs-uuid --set=root 849ea212-8008-42f4-b440-f67f8a8687be
fi
echo 'Loading Linux 3.8.0-31-generic ...'
linux /vmlinuz-3.8.0-31-generic root=UUID=5bb9b055-184d-4fd5-acf7-90c295e94ca2 ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.8.0-31-generic
}
menuentry 'Ubuntu, with Linux 3.8.0-31-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.8.0-31-generic-recovery-5bb9b055-184d-4fd5-acf7-90c295e94ca2' {
recordfail
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 849ea212-8008-42f4-b440-f67f8a8687be
else
search --no-floppy --fs-uuid --set=root 849ea212-8008-42f4-b440-f67f8a8687be
fi
echo 'Loading Linux 3.8.0-31-generic ...'
linux /vmlinuz-3.8.0-31-generic root=UUID=5bb9b055-184d-4fd5-acf7-90c295e94ca2 ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.8.0-31-generic
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Windows" {
search --fs-uuid --no-floppy --set=root 887D-F3E4
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
Re: GPT messed up, cant boot or access harddrive
Quote:
[18942.384760] EXT4-fs (sda3): bad geometry: block count 15800064 exceeds size of device (7903059 blocks)
This means that the size of the partition is too small for the size of the ext4 filesystem. The ext4 filesystem
uses 4096 byte blocks whereas the disk uses 512 byte logical sectors. So 7903059 blocks = 63224472 sectors, the
size of sda3.
The filesystem seems to be 15800064 blocks or 126400512 sectors or 60GiB. This is impossible because the disk is
not big enough. I am pondering how this might have come to be.
The filesystem may be repaired using fsck and then mounted to see what data remains. You need to look up how to
use fsck.
Re: GPT messed up, cant boot or access harddrive
Could it be, that sda2 is too big? Currently it is about 30GB big and that is way too much for a /boot partition. Is there any information in the ext4 superblock about the size of a partition? Like in most protocol headers?
Does the total block count help to find out the size of the partition and thus the beginning of the next partition?
https://ext4.wiki.kernel.org/index.p...he_Super_Block
Will set up Linux on a spare drive, to not be dependent on the Live OS. If you tell me something to do and it is better to do that from a Live OS, please tell me so ;)