Taperssection.com
Gear / Technical Help => Post-Processing, Computer / Streaming / Internet Devices & Related Activity => Topic started by: Simp-Dawg on January 31, 2011, 02:46:22 PM
-
i posted about this in another topic and wanted to get some more eyes on this if possible.
i had a WD MyBook Pro Edition II 1TB (2x 500GB drives) that has failed. the enclosure doesn't even power up anymore, but the drives themselves are fine. i've taken them out and hooked them up to my other computers, they spin up fine, just can't read the data because it is striped across 2 drives and no OS (i've tried windows 7, mac OSX 10.6, and ubuntu linux) can see a partition table.
I called a data recovery place and they quoted $2K for the recovery services...that's pretty damn steep.
I'm wondering if anyone has had to do this before and could make some recommendations, OR, does anyone have one of these enclosures that i could try putting my drives in?
-
http://tinyurl.com/4m33t92
Maybe buying a used MyBook and swapping the drives out?
-
http://tinyurl.com/4m33t92
Maybe buying a used MyBook and swapping the drives out?
yeah that's one thing i wanted to try...thanks for finding that one! i searched ebay earlier and didn't find anything...
-
are you trying on a raid controller or just looking at the drives one by one. Don't know the specifics about the mybook, but if it striped the drives, I'd try putting them onto another raid controller.
WD also has recovery and drive utils on its web site did you try any of that?
JAson
-
The Wikkipedia entry has a procedure to mount them with Debian. So that might also save your bacon....
http://en.wikipedia.org/wiki/Western_Digital_My_Book
From the article......
Internals
This article contains instructions, advice, or how-to content. The purpose of Wikipedia is to present facts, not to train. Please help improve this article either by rewriting the how-to content or by moving it to Wikiversity or Wikibooks. (November 2010)
Controller board for My Book World Edition
This drive runs BusyBox on Linux on an Oxford Semiconductor 0XE800 ARM chip which has the ARM926EJ-S core. In addition it uses a VIA Cicada Simpliphy vt6122 Gigabit Ethernet chipset, and a Hynix 32 Mbit DDR Synchronous DRAM chip. The webserver is the mini_http server, although older "bluerings" use Lighttpd. The drives of the World Edition are xfs formatted, which means that the drive can be mounted as a standard drive from within Linux if removed from the casing and installed in a normal PC.
The disk filesystems are also known to exist in a format created by linux multiple devices driver (Mdadm) which ultimately wraps an ext3 partition with some metadata that allows the inquiry of the position of the drive in a RAID set. Unfortunately, this makes mounting the drives outside of the enclosure a bit more complicated, it also requires a machine with a Linux (or possibly some other Unix) based operating system. For example, the best way to mount the drives on a Linux flavored operating system after they have been removed from the enclosure is to use the following set of commands (on Debian) for mirrored RAID 1 disks.
# modprobe md
# mknod /dev/md4 b 9 4
# apt-get install mdadm
# mdadm—assemble /dev/md4 /dev/sdb4
# mkdir /media/xyz
# mount /dev/md4 /media/xyz
# chmod -R 777 /media/xyz
The above set of commands assumes that the drives appear as /dev/sdb to Linux.
The following command set can be used for mounting a multidisk spanning RAID 0 set in Debian Linux:
# modprobe md
# mknod /dev/md4 b 9 4
# apt-get install mdadm
# mdadm -Cv /dev/md4 -l0 -n2 -c64 /dev/sdb4 /dev/sdc4
# mkdir /media/xyz
# mount /dev/md4 /media/xyz
# chmod -R 777 /media/xyz
The above set of commands assume that the drives appear as /dev/sda and /dev/sdb to Userspace.
With both sets of commands a utility such as Gparted can be used to determine which paths are relevant for a given setup.
Further details and support are available at the My Worldbook wiki.
-
are you trying on a raid controller or just looking at the drives one by one. Don't know the specifics about the mybook, but if it striped the drives, I'd try putting them onto another raid controller.
WD also has recovery and drive utils on its web site did you try any of that?
JAson
i don't have a raid controller other than the dead enclosure...so i'm not sure that i could even try any of the utilities you mention.
the debian thing...doesn't look easy but might give it a go if i can't pick up that drive on ebay.
thanks! keep 'em coming!
-
the debian thing...doesn't look easy but might give it a go if i can't pick up that drive on ebay.
thanks! keep 'em coming!
I don't think you would need to buy anything. Essentially they are saying the WD MyBook Pro Edition II 1TB runs the BusyBox Linux distro, and that you can used Debian to access the RAID 0 array. You should be able to take an old PC, install Debian http://www.debian.org/CD/ or you might try a Debian Live CD, then run the mount commands in the article and you might be done.
-
the debian thing...doesn't look easy but might give it a go if i can't pick up that drive on ebay.
thanks! keep 'em coming!
I don't think you would need to buy anything. Essentially they are saying the WD MyBook Pro Edition II 1TB runs the BusyBox Linux distro, and that you can used Debian to access the RAID 0 array. You should be able to take an old PC, install Debian http://www.debian.org/CD/ or you might try a Debian Live CD, then run the mount commands in the article and you might be done.
alright...this may have been a mistake because technically these instructions are for the Worldbook NAS model and mine is a Pro Edition II...but i created a bootable usb with linux mint debian on it and tried the commands from the wikipedia article (for mounting a multi-drive spanning RAID0 volume)...
i ran into a few snags getting "mdadm" installed but it seemed to work when i did it through the synaptics package manager. i got the command that starts with "mdadm -Cv" to work but when i got to mounting the drives i got hung up because the command doesn't specify a filesystem and when i tried adding "-t ext3" in the command as per some of the comments at http://mybookworld.wikidot.com/forum/t-90514/how-to-recover-data-from-wd-my-book-world-edition-nas-device it wouldn't recognize the file system on the drive...so i tried the "--assemble" command found in the comments on that second site, and then started trying some other commands i found while googling some of the error messages i got...things like when the resource was busy, i found a stop command, and then i tried very haphazardly at writing a new partition table (meaning i really didn't know what i was doing or if it would FUBAR the whole process)...here's what i could copy from the terminal window (it starts in the middle of a "fdisk -l" report) :
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/sda doesn't contain a valid partition table
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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: 0x6e58b354
Device Boot Start End Blocks Id System
/dev/sdb1 1 121601 976760001 7 HPFS/NTFS
Disk /dev/sdc: 1973 MB, 1973420032 bytes
255 heads, 63 sectors/track, 239 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
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 240 1927107 b W95 FAT32
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(239, 233, 63)
Disk /dev/md4: 1000.2 GB, 1000213577728 bytes
2 heads, 4 sectors/track, 244192768 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0xff8b0030
Disk /dev/md4 doesn't contain a valid partition table
mint mint # sudo su
_________________________________________
/ "I wonder", he said to himself, "what's \
| in a book while it's closed. Oh, I know |
| it's full of letters printed on paper, |
| but all the same, something must be |
| happening, because as soon as I open |
| it, there's a whole story with people I |
| don't know yet and all kinds of |
| adventures and battles." |
| |
\ -- Bastian B. Bux /
-----------------------------------------
\
\ \_\_ _/_/
\ \__/
(oo)\_______
(__)\ )\/\
||----w |
|| ||
mint mint # ls /dev
adsp hpet pts tty11 tty38 tty7
agpgart initctl random tty12 tty39 tty8
audio input rfkill tty13 tty4 tty9
block kmsg rtc tty14 tty40 ttyS0
bsg log rtc0 tty15 tty41 ttyS1
btrfs-control loop0 scd0 tty16 tty42 ttyS2
bus loop1 scd1 tty17 tty43 ttyS3
cdrom1 loop2 sda tty18 tty44 urandom
cdrom2 loop3 sdb tty19 tty45 usb
cdrw1 loop4 sdc tty2 tty46 vcs
cdrw2 loop5 sdc1 tty20 tty47 vcs1
cgroup loop6 sg0 tty21 tty48 vcs2
char loop7 sg1 tty22 tty49 vcs3
console lp0 sg2 tty23 tty5 vcs4
core MAKEDEV sg3 tty24 tty50 vcs5
cpu_dma_latency mcelog sg4 tty25 tty51 vcs6
disk md shm tty26 tty52 vcs7
dri md4 snapshot tty27 tty53 vcsa
dsp mem snd tty28 tty54 vcsa1
dvd1 mixer sndstat tty29 tty55 vcsa2
dvd2 net sr0 tty3 tty56 vcsa3
dvdrw1 network_latency sr1 tty30 tty57 vcsa4
fb0 network_throughput stderr tty31 tty58 vcsa5
fd null stdin tty32 tty59 vcsa6
fd0 parport0 stdout tty33 tty6 vcsa7
full port tty tty34 tty60 vga_arbiter
fuse ppp tty0 tty35 tty61 xconsole
fw0 psaux tty1 tty36 tty62 zero
hidraw0 ptmx tty10 tty37 tty63
mint mint # ls /dev | grep sd
sda
sdb
sdc
sdc1
mint mint # mknod /dev/md4 b 9 4
mknod: `/dev/md4': File exists
mint mint # mdadm -Cv /dev/md4 -l0 -n2 -c64 /dev/sda /dev/sdb
mdadm: super1.x cannot open /dev/sda: Device or resource busy
mdadm: failed container membership check
mdadm: device /dev/sda not suitable for any style of array
mint mint # mdadm -S /dev/md4
mdadm: stopped /dev/md4
mint mint # mdadm -Cv /dev/md4 -l0 -n2 -c64 /dev/sda /dev/sdb
mdadm: /dev/sda appears to be part of a raid array:
level=raid0 devices=2 ctime=Sat Apr 9 12:48:17 2011
mdadm: /dev/sdb appears to be part of a raid array:
level=raid0 devices=2 ctime=Sat Apr 9 12:48:17 2011
mdadm: partition table exists on /dev/sdb but will be lost or
meaningless after creating array
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md4 started.
mint mint # mkdir /media/xyz
mkdir: cannot create directory `/media/xyz': File exists
mint mint # mount /dev/md4 /media/xyz
mount: you must specify the filesystem type
mint mint # mount -t ext3 /dev/md4 /media/xyz
mount: wrong fs type, bad option, bad superblock on /dev/md4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mint mint # mdadm --assemble /dev/md4 --force /dev/sda /dev/sdb
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has no superblock - assembly aborted
mint mint # mdadm -S /dev/sda
mdadm: /dev/sda does not appear to be an md device
mint mint # mdadm -S /dev/md4
mdadm: stopped /dev/md4
mint mint # mdadm --assemble /dev/md4 --force /dev/sda /dev/sdb
mdadm: /dev/md4 has been started with 2 drives.
mint mint # mount /dev/md4 /media/xyz
mount: you must specify the filesystem type
mint mint # mount -t ext3 /dev/md4 /media/xyz
mount: wrong fs type, bad option, bad superblock on /dev/md4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mint mint # dmesg | tail
[ 2981.435833] raid0: done.
[ 2981.435837] raid0 : md_size is 1953542144 sectors.
[ 2981.435840] ******* md4 configuration *********
[ 2981.435843] zone0=[sda/sdb/]
[ 2981.435849] zone offset=0kb device offset=0kb size=976771072kb
[ 2981.435853] **********************************
[ 2981.435854]
[ 2981.435872] md4: detected capacity change from 0 to 1000213577728
[ 2981.456096] md4: unknown partition table
[ 3016.806521] VFS: Can't find ext3 filesystem on dev md4.
mint mint # fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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/sda doesn't contain a valid partition table
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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: 0x6e58b354
Device Boot Start End Blocks Id System
/dev/sdb1 1 121601 976760001 7 HPFS/NTFS
Disk /dev/sdc: 1973 MB, 1973420032 bytes
255 heads, 63 sectors/track, 239 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
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 240 1927107 b W95 FAT32
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(239, 233, 63)
Disk /dev/md4: 1000.2 GB, 1000213577728 bytes
2 heads, 4 sectors/track, 244192768 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0xff8b0030
Disk /dev/md4 doesn't contain a valid partition table
mint mint # fdisk /dev/md4
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x6ce3697c.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): m
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): l
0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris
1 FAT12 39 Plan 9 82 Linux swap / So c1 DRDOS/sec (FAT-
2 XENIX root 3c PartitionMagic 83 Linux c4 DRDOS/sec (FAT-
3 XENIX usr 40 Venix 80286 84 OS/2 hidden C: c6 DRDOS/sec (FAT-
4 FAT16 <32M 41 PPC PReP Boot 85 Linux extended c7 Syrinx
5 Extended 42 SFS 86 NTFS volume set da Non-FS data
6 FAT16 4d QNX4.x 87 NTFS volume set db CP/M / CTOS / .
7 HPFS/NTFS 4e QNX4.x 2nd part 88 Linux plaintext de Dell Utility
8 AIX 4f QNX4.x 3rd part 8e Linux LVM df BootIt
9 AIX bootable 50 OnTrack DM 93 Amoeba e1 DOS access
a OS/2 Boot Manag 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O
b W95 FAT32 52 CP/M 9f BSD/OS e4 SpeedStor
c W95 FAT32 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs
e W95 FAT16 (LBA) 54 OnTrackDM6 a5 FreeBSD ee GPT
f W95 Ext'd (LBA) 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/
10 OPUS 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC b
11 Hidden FAT12 5c Priam Edisk a8 Darwin UFS f1 SpeedStor
12 Compaq diagnost 61 SpeedStor a9 NetBSD f4 SpeedStor
14 Hidden FAT16 <3 63 GNU HURD or Sys ab Darwin boot f2 DOS secondary
16 Hidden FAT16 64 Novell Netware af HFS / HFS+ fb VMware VMFS
17 Hidden HPFS/NTF 65 Novell Netware b7 BSDI fs fc VMware VMKCORE
18 AST SmartSleep 70 DiskSecure Mult b8 BSDI swap fd Linux raid auto
1b Hidden W95 FAT3 75 PC/IX bb Boot Wizard hid fe LANstep
1c Hidden W95 FAT3 80 Old Minix be Solaris boot ff BBT
1e Hidden W95 FAT1
Command (m for help): p
Disk /dev/md4: 1000.2 GB, 1000213577728 bytes
2 heads, 4 sectors/track, 244192768 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x6ce3697c
Device Boot Start End Blocks Id System
Command (m for help): v
Remaining 1953542143 unallocated 512-byte sectors
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
mint mint # mount /dev/md4 /media/xyz
mount: you must specify the filesystem type
mint mint # mount -t ext3 /dev/md4 /media/xyz
mount: wrong fs type, bad option, bad superblock on /dev/md4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mint mint # dmesg | tail
[ 2981.435840] ******* md4 configuration *********
[ 2981.435843] zone0=[sda/sdb/]
[ 2981.435849] zone offset=0kb device offset=0kb size=976771072kb
[ 2981.435853] **********************************
[ 2981.435854]
[ 2981.435872] md4: detected capacity change from 0 to 1000213577728
[ 2981.456096] md4: unknown partition table
[ 3016.806521] VFS: Can't find ext3 filesystem on dev md4.
[ 3638.364434] md4:
[ 3653.430647] VFS: Can't find ext3 filesystem on dev md4.
mint mint # fdisk /dev/md4
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): m
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): p
Disk /dev/md4: 1000.2 GB, 1000213577728 bytes
2 heads, 4 sectors/track, 244192768 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x6ce3697c
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
1
Invalid partition number for type `1'
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-244192768, default 33):
Using default value 33
Last cylinder, +cylinders or +size{K,M,G} (33-244192768, default 244192768):
Using default value 244192768
Command (m for help): v
Remaining 255 unallocated 512-byte sectors
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
mint mint # fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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/sda doesn't contain a valid partition table
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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: 0x6e58b354
Device Boot Start End Blocks Id System
/dev/sdb1 1 121601 976760001 7 HPFS/NTFS
Disk /dev/sdc: 1973 MB, 1973420032 bytes
255 heads, 63 sectors/track, 239 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
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 240 1927107 b W95 FAT32
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(239, 233, 63)
Disk /dev/md4: 1000.2 GB, 1000213577728 bytes
2 heads, 4 sectors/track, 244192768 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x6ce3697c
Device Boot Start End Blocks Id System
/dev/md4p1 33 244192768 976770944 83 Linux
mint mint # mount -t ext3 /dev/md4 /media/xyz
mount: wrong fs type, bad option, bad superblock on /dev/md4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mint mint # mount /dev/md4 /media/xyz
mount: you must specify the filesystem type
mint mint # mount -t Linux /dev/md4 /media/xyz
mount: unknown filesystem type 'Linux'
mint mint # mkfs.ext3 /dev/md4
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=16 blocks, Stripe width=32 blocks
61054976 inodes, 244192768 blocks
12209638 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
7453 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
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
mint mint # mount /dev/md4 /media/xyz
mint mint # chmod -R 777 /media/xyz
mint mint # fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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/sda doesn't contain a valid partition table
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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: 0x6e58b354
Device Boot Start End Blocks Id System
/dev/sdb1 1 121601 976760001 7 HPFS/NTFS
Disk /dev/sdc: 1973 MB, 1973420032 bytes
255 heads, 63 sectors/track, 239 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
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 240 1927107 b W95 FAT32
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(239, 233, 63)
Disk /dev/md4: 1000.2 GB, 1000213577728 bytes
2 heads, 4 sectors/track, 244192768 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x00000000
Disk /dev/md4 doesn't contain a valid partition table
mint mint # mkdir /media/poo
mint mint # mount /dev/sdb1 /media/poo
mount: special device /dev/sdb1 does not exist
mint mint # mount /dev/sdb /media/poo
mount: unknown filesystem type 'linux_raid_member'
mint mint # fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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/sda doesn't contain a valid partition table
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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: 0x6e58b354
Device Boot Start End Blocks Id System
/dev/sdb1 1 121601 976760001 7 HPFS/NTFS
Disk /dev/sdc: 1973 MB, 1973420032 bytes
255 heads, 63 sectors/track, 239 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
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 240 1927107 b W95 FAT32
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(239, 233, 63)
Disk /dev/md4: 1000.2 GB, 1000213577728 bytes
2 heads, 4 sectors/track, 244192768 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x00000000
Disk /dev/md4 doesn't contain a valid partition table
mint mint #
...ultimately i got the array to mount but when i open up /media/xyz there's a "lost+found" directory and it's empty. pretty sure that i should not have tried writing a new partition table like i did, and not sure if i destroyed any data by doing that.
can anyone help figure out what i've done/can do from here?
-
i'm posting this in a few places as I had the same issues (I'm aware thread is old).
Use a PC, slave the WorldBook disk that was part of the RAID 0 or 1
download and install:
http://www.diskinternals.com/linux-reader/
browse all the drives that are now visible and you may just find what you need...
-
I have two MyBooks. Could it be the power supply? The one they provide is cheapo crap. One of mine went up in smoke and I no longer use the drives as I can't trust them.