i managed to boot up the hdd by removintg following line in the fstab file:
Code: Select all
/dev/mapper/bubba-storage /home ext3 defaults 0 2
now i'm able to check things on the hdd directly using ssh (putty)
Code: Select all
root@joseserver:/# sfdisk -l
Disk /dev/sda: 121601 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ 1216 1217- 9775521 83 Linux
/dev/sda2 1217 121456 120240 965827800 8e Linux LVM
/dev/sda3 121457 121600 144 1156680 82 Linux swap / Solaris
/dev/sda4 0 - 0 0 0 Empty
Disk /dev/dm-0: 120239 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/dm-0: unrecognized partition table type
No partitions found
well, i don't know what the dm-0 disk is. the problematic lvm partition is on sda > sda2
Code: Select all
root@joseserver:/# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 bubba lvm2 -- 921.08g 0
root@joseserver:/# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
storage bubba -wi-a- 921.08g
root@joseserver:/# lvdisplay
--- Logical volume ---
LV Name /dev/bubba/storage
VG Name bubba
LV UUID TlYu8Y-JahI-lnNT-Y8Tk-w8TE-CEn7-WD8Ytc
LV Write Access read/write
LV Status available
# open 0
LV Size 921.08 GiB
Current LE 235797
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
root@joseserver:/# mount -t ext3 /dev/bubba/storage /mnt/mydata
mount: wrong fs type, bad option, bad superblock on /dev/mapper/bubba-storage,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
done now the fsck.ext3 check
[code]
root@joseserver:/# fsck.ext3 -n /dev/bubba/storage
e2fsck 1.41.12 (17-May-2010)
fsck.ext3: Superblock invalid, trying backup blocks...
The filesystem size (according to the superblock) is 485646336 blocks
The physical size of the device is 241456128 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? no
Bubba_home contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 241467394 (Invalid argument) while getting next inode from scan. Ignore error? no
Error while scanning inodes (120733696): Can't read next inode
e2fsck: aborted
root@joseserver:/# dmesg | tail
EXT3-fs (sda1): using internal journal
nf_conntrack version 0.5.0 (3996 buckets, 15984 max)
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
PHY: mdio@e0024520:00 - Link is Up - 100/Full
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
sshd (1836): /proc/1836/oom_adj is deprecated, please use /proc/1836/oom_score_adj instead.
eth1: no IPv6 routers present
EXT3-fs (dm-0): error: can't find ext3 filesystem on dev dm-0.
[/code]
when i fsck.ext3 the /dev/sda2 or /dev/bubba/storage while running a live cd i got folloiwng:
Code: Select all
Bad magic number in super-block while trying to open <device>
<device>:
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>
i newly found a command to show up alternate superblocks. it showed me a list of blocks while using the live cd but now i get following:
Code: Select all
root@joseserver:/# mke2fs -n -S /dev/sda2
mke2fs 1.41.12 (17-May-2010)
/dev/sda2 is apparently in use by the system; will not make a filesystem here!
the alternate superblock command on /dev/bubba/storage worked:
Code: Select all
root@joseserver:/# mke2fs -n -S /dev/bubba/storage
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
60366848 inodes, 241456128 blocks
12072806 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
7369 block groups
32768 blocks per group, 32768 fragments per group
8192 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, 214990848
seems that fsck.ext3 and e2fsck lead to the same check:
Code: Select all
root@joseserver:/# fsck.ext3 -b 819200 /dev/bubba/storage
e2fsck 1.41.12 (17-May-2010)
The filesystem size (according to the superblock) is 485646336 blocks
The physical size of the device is 241456128 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no
Bubba_home contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 241467394 (Invalid argument) while getting next inode from scan. Ignore error<y>? yes
Force rewrite<y>? no
Error reading block 241467395 (Invalid argument) while getting next inode from scan. Ignore error<y>? no
Error while scanning inodes (120733696): Can't read next inode
e2fsck: aborted
root@joseserver:/# e2fsck -b 819200 /dev/bubba/storage
e2fsck 1.41.12 (17-May-2010)
The filesystem size (according to the superblock) is 485646336 blocks
The physical size of the device is 241456128 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no
Bubba_home contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 241467394 (Invalid argument) while getting next inode from scan. Ignore error<y>? no
Error while scanning inodes (120733696): Can't read next inode
e2fsck: aborted
i'm not sure to accept the rewrite question.