- Below is the output of fdisk, mke2fs, e2fsck, and mount command for one drive which was in an iOmega ix2-200 set up as RAID1. The iOmega died, but the drives still appear to be in good shape. When placed in a Windows machine, the files can be seen but have no names (e.g. 1000.xls). The drive is located at /def/sdf and the particular partition I'm trying to mount is /dev/sdf2. I have no experience with mdadm, and thought I could simply mount the disk like any other -- I'm assuming I'm wrong, though. Any tips?
- --------------------------------------------------------------------------------
- fdisk -l /dev/sdf:
- Disk /dev/sdf: 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: 0x000d3a8d
- Device Boot Start End Blocks Id System
- /dev/sdf1 1 254 2040254+ 83 Linux
- /dev/sdf2 255 121602 974722329 83 Linux #PARTITION I ASSUME DATA IS ON
- --------------------------------------------------------------------------------
- sudo mke2fs -n /dev/sdf2
- mke2fs 1.41.11 (14-Mar-2010)
- Filesystem label=
- OS type: Linux
- Block size=4096 (log=2)
- Fragment size=4096 (log=2)
- Stride=0 blocks, Stripe width=0 blocks
- 60923904 inodes, 243680582 blocks
- 12184029 blocks (5.00%) reserved for the super user
- First data block=0
- Maximum filesystem blocks=4294967296
- 7437 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
- --------------------------------------------------------------------------------
- e2fsck -f /dev/sdf2 -b 32768
- #and all the other backups listed (except the rather long ones caused an argument error)
- e2fsck 1.41.11 (14-Mar-2010)
- e2fsck: Bad magic number in super-block while trying to open /dev/sdf2
- 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>
- --------------------------------------------------------------------------------
- mount /dev/sdf2 /media/tmpMount2
- mount: unknown filesystem type 'linux_raid_member'
- --------------------------------------------------------------------------------
- mount -t ext3 /dev/sdf2 /media/tmpMount2
- mount: wrong fs type, bad option, bad superblock on /dev/sdf2,
- missing codepage or helper program, or other error
- In some cases useful info is found in syslog - try
- dmesg | tail or so
- --------------------------------------------------------------------------------
- Using testdisk finds a partition table:
- TestDisk 6.11, Data Recovery Utility, April 2009
- Christophe GRENIER <grenier@cgsecurity.org>
- http://www.cgsecurity.org
- Disk /dev/sdf - 1000 GB / 931 GiB - CHS 121601 255 63
- Partition Start End Size in sectors
- 1 P Linux LVM 254 0 1 121601 254 63 1949455620
- --------------------------------------------------------------------------------
SHARE
TWEET
Untitled
a guest
Apr 9th, 2012
83
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
RAW Paste Data
