Public Pastes
daily pastebin goal
15%
SHARE
TWEET

Untitled

a guest Apr 9th, 2012 16 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. 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?
  2.  
  3. --------------------------------------------------------------------------------
  4. fdisk -l /dev/sdf:
  5.  
  6. Disk /dev/sdf: 1000.2 GB, 1000204886016 bytes
  7. 255 heads, 63 sectors/track, 121601 cylinders
  8. Units = cylinders of 16065 * 512 = 8225280 bytes
  9. Sector size (logical/physical): 512 bytes / 512 bytes
  10. I/O size (minimum/optimal): 512 bytes / 512 bytes
  11. Disk identifier: 0x000d3a8d
  12.  
  13.    Device Boot      Start         End      Blocks   Id  System
  14. /dev/sdf1               1         254     2040254+  83  Linux
  15. /dev/sdf2             255      121602   974722329   83  Linux #PARTITION I ASSUME DATA IS ON
  16.  
  17. --------------------------------------------------------------------------------
  18. sudo mke2fs -n /dev/sdf2
  19.  
  20. mke2fs 1.41.11 (14-Mar-2010)
  21. Filesystem label=
  22. OS type: Linux
  23. Block size=4096 (log=2)
  24. Fragment size=4096 (log=2)
  25. Stride=0 blocks, Stripe width=0 blocks
  26. 60923904 inodes, 243680582 blocks
  27. 12184029 blocks (5.00%) reserved for the super user
  28. First data block=0
  29. Maximum filesystem blocks=4294967296
  30. 7437 block groups
  31. 32768 blocks per group, 32768 fragments per group
  32. 8192 inodes per group
  33. Superblock backups stored on blocks:
  34.         32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
  35.         4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
  36.         102400000, 214990848
  37.  
  38. --------------------------------------------------------------------------------
  39. e2fsck -f /dev/sdf2 -b 32768
  40. #and all the other backups listed (except the rather long ones caused an argument error)
  41.  
  42. e2fsck 1.41.11 (14-Mar-2010)
  43. e2fsck: Bad magic number in super-block while trying to open /dev/sdf2
  44.  
  45. The superblock could not be read or does not describe a correct ext2
  46. filesystem.  If the device is valid and it really contains an ext2
  47. filesystem (and not swap or ufs or something else), then the superblock
  48. is corrupt, and you might try running e2fsck with an alternate superblock:
  49.     e2fsck -b 8193 <device>
  50.  
  51. --------------------------------------------------------------------------------
  52. mount /dev/sdf2 /media/tmpMount2
  53.  
  54. mount: unknown filesystem type 'linux_raid_member'
  55.  
  56. --------------------------------------------------------------------------------
  57. mount -t ext3 /dev/sdf2 /media/tmpMount2
  58.  
  59. mount: wrong fs type, bad option, bad superblock on /dev/sdf2,
  60.        missing codepage or helper program, or other error
  61.        In some cases useful info is found in syslog - try
  62.        dmesg | tail  or so
  63.  
  64. --------------------------------------------------------------------------------
RAW Paste Data
Pastebin PRO WINTER Special!
Get 40% OFF Pastebin PRO accounts!
Top