Thread: An superblock tale of woe
goodly men , womenfolk of ubuntu-land. tale starts many electrical blackouts, followed exploding graphics card, end result system that, when booting, gives continuous input output errors , boot-eth not.
herein follows saga of tragedy not told since days of romeo , juliet. sda1, ghostboot partition, appeareth fine, , verily, ntfs partition, yea, windows 7, boot-eth fine , workest in forms. tis linux partition booth-eth not, point of not being address-able in fashion. should merely hope mount volume , save data, , start on option nuclear pavement. data yet hast reached salvation, , end doth seek.
1) sayeth fdisk?
2) more sayeth fdisk?code:knoppix@microknoppix:~$ sudo fdisk -l disk /dev/sda: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders units = cylinders of 16065 * 512 = 8225280 bytes sector size (logical/physical): 512 bytes / 512 bytes i/o size (minimum/optimal): 512 bytes / 512 bytes disk identifier: 0x9201fe6f device boot start end blocks id system /dev/sda1 * 1 2 16033+ 1 fat12 /dev/sda2 3 50994 409593240 7 hpfs/ntfs /dev/sda3 50995 121601 567150727+ 8e linux lvm disk /dev/sdb: 1000.2 gb, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders units = cylinders of 16065 * 512 = 8225280 bytes sector size (logical/physical): 512 bytes / 512 bytes i/o size (minimum/optimal): 512 bytes / 512 bytes disk identifier: 0x9201fe50 device boot start end blocks id system /dev/sdb1 1 15 120456 83 linux /dev/sdb2 16 121602 976641024 8e linux lvm knoppix@microknoppix:~$
3) mounteth not, read-onlycode:knoppix@microknoppix:~$ sudo fdisk -l /dev/sda3 disk /dev/sda3: 580.8 gb, 580762344960 bytes 255 heads, 63 sectors/track, 70607 cylinders units = cylinders of 16065 * 512 = 8225280 bytes sector size (logical/physical): 512 bytes / 512 bytes i/o size (minimum/optimal): 512 bytes / 512 bytes disk identifier: 0x00000000 disk /dev/sda3 doesn't contain valid partition table knoppix@microknoppix:~$ sudo mke2fs -n /dev/sda3 warning: 545 blocks unused. filesystem label= os type: linux block size=4096 (log=2) fragment size=4096 (log=2) stride=0 blocks, stripe width=0 blocks 35516016 inodes, 141787136 blocks 7089384 blocks (5.00%) reserved super user first data block=0 maximum filesystem blocks=0 4327 block groups 32768 blocks per group, 32768 fragments per group 8208 inodes per group superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000
4) o, fsck, sayest thou?code:knoppix@microknoppix:~$ knoppix@microknoppix:/media$ sudo mount -o,ro /dev/sda3 mount: unknown filesystem type 'lvm2_member' knoppix@microknoppix:/media$
5) , you, e2fsck, canst thou add tale of woe?code:knoppix@microknoppix:~$ sudo fsck /dev/sda3 fsck: fsck.lvm2_member: not found fsck: error 2 while executing fsck.lvm2_member /dev/sda3 knoppix@microknoppix:~$
code:knoppix@microknoppix:~$ e2fsck /dev/sda3 e2fsck: superblock invalid, trying backup blocks... e2fsck: bad magic number in super-block while trying open /dev/sda3 superblock not read or not describe correct ext2 filesystem. if device valid , contains ext2 filesystem (and not swap or ufs or else), superblock corrupt, , might try running e2fsck alternate superblock: e2fsck -b 8193 <device> knoppix@microknoppix:~$
6) mke2fs , e2fsck chant in harmony siren saga
code:knoppix@microknoppix:~$ sudo mke2fs -n /dev/sda3 warning: 545 blocks unused. filesystem label= os type: linux block size=4096 (log=2) fragment size=4096 (log=2) stride=0 blocks, stripe width=0 blocks 35516016 inodes, 141787136 blocks 7089384 blocks (5.00%) reserved super user first data block=0 maximum filesystem blocks=0 4327 block groups 32768 blocks per group, 32768 fragments per group 8208 inodes per group superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000 knoppix@microknoppix:~$ sudo e2fsck -y -b 32768 /dev/sda3 e2fsck: bad magic number in super-block while trying open /dev/sda3 superblock not read or not describe correct ext2 filesystem. if device valid , contains ext2 filesystem (and not swap or ufs or else), superblock corrupt, , might try running e2fsck alternate superblock: e2fsck -b 8193 <device> knoppix@microknoppix:~$ sudo e2fsck -y -b 98304 /dev/sda3 e2fsck: bad magic number in super-block while trying open /dev/sda3 superblock not read or not describe correct ext2 filesystem. if device valid , contains ext2 filesystem (and not swap or ufs or else), superblock corrupt, , might try running e2fsck alternate superblock: e2fsck -b 8193 <device> knoppix@microknoppix:~$ sudo e2fsck -y -b 163840 /dev/sda3 e2fsck: bad magic number in super-block while trying open /dev/sda3 superblock not read or not describe correct ext2 filesystem. if device valid , contains ext2 filesystem (and not swap or ufs or else), superblock corrupt, , might try running e2fsck alternate superblock: e2fsck -b 8193 <device> knoppix@microknoppix:~$ sudo e2fsck -y -b 229376 /dev/sda3 e2fsck: bad magic number in super-block while trying open /dev/sda3 superblock not read or not describe correct ext2 filesystem. if device valid , contains ext2 filesystem (and not swap or ufs or else), superblock corrupt, , might try running e2fsck alternate superblock: e2fsck -b 8193 <device> knoppix@microknoppix:~$ etcetera, etcetera until ... knoppix@microknoppix:~$ sudo e2fsck -y -b 102400000 /dev/sda3 e2fsck: invalid argument while trying open /dev/sda3 superblock not read or not describe correct ext2 filesystem. if device valid , contains ext2 filesystem (and not swap or ufs or else), superblock corrupt, , might try running e2fsck alternate superblock: e2fsck -b 8193 <device> knoppix@microknoppix:~$
if (as indicated fdisk) actual filesystem (ext2/3/4 or whatever) on top of lvm volume, need mount *that* - don't think able mount /dev/sda3 directly
if do
code:sudo pvdisplay sudo vgdisplay sudo lvdisplay
Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [SOLVED] An superblock tale of woe
Ubuntu
Comments
Post a Comment