Update: 01/27/2009 - 3:18 am EST. (see bottom of posting)
Issue: (Pardon the length of this - it has been hours in the creating, and I won't be able to describe it in 20 seconds.)
I have a "My World Book II - 1 T (dual drive) version that I have owned for a year or so now. I have left it formatted as a linear (spanned / JBOD) system to utilize the entire 1 T of storage.
Today - this afternoon - I noticed that the WBII was (God Only Knows Why) not allowing r/w access - it is as if the entire system was mounted R/O. I went looking around on the admin pages - nothing out of the ordinary there - it claimed the drives were "peachy key OK!" and etc. I could see the drive, but not touch anything anywhere.
So, I took the drive down - literally - off the shelf on my server stack where I keep it - placed it on my workbench, fired it up, and tried to work with it. Still R/O.
I took it apart (the back cover off) unclipped the drives and took them out. They were quite warm, but not so hot I could not handle them. I replaced them, put the plugs back in (to make sure they were seated properly), and tried it again. (being careful to make sure the drives were replaced in their original positions!)
I tried going so far as to do a hard-reset (holding the reset button down while I applied power).
When I would apply power - I would get wierd LED patterns (right now, having re-booted the thing, I am getting the inner-outer sequential flashing that - were I using RAID - would indicate a fuzzed drive somewhere.)
It would get locked into a "fading in circles" or "blinking" or whatever mode that would not respond to attempts to shut it down. (or anything else for that matter.)
I can ping it. I cannot access it's setup web page, and I cannot access the share(s) created there.
The device began it's "broken RAID" dance with the lights, and it was absolutely un-responsive for a while. Then - Praise God! - it started responding to the network HTTP requests and I got the admin pages. There it reported "Drive A failed".
If I read these fora (and the notes, and etc.) rightly, the bulk of the operating system is on drive A, right? (with just enough intelligence in the firmware to light up the network and get a "firmware" download and write it to the "A" drive) Or am I missing something?
Let's assume (for arguments sake) that "Drive A Failed" doesn't necessarily mean that drive A is D-E-A-I-D, deaid, but is in enough trouble that the limited abilities of the built in O/S doesn't know what to do with them. Or maybe drive A is just fine, but drive B has issues, but because it's a "linear" set, it thinks of BOTH drives as "drive A"?
Therefore - if this IS true - I should be able to mount the drive(s) on a linux system and investigate what is going on (perhaps do a full-court-press FSCK and see what comes up…)
1. What filesystem do these drives use?
2. Assuming that I go out and grab a SATA card from Best Buy (or some such), slap it into a handy Linux box (with Ubuntu linux on it), and fire the beastie up:
(a) Since the drives were set up as a spanned (linear / JBOD), set, do I have to mount them as a pair?
(b) Having never even DREAMED of mounting a pair of drives as a JBOD / linear / RAID-0 set, how do I put them in the fstab? (or do I have to? Can Linux detect a spanned set?) Do I have to do something different to mount the beasties?
(c) What else do I have to know before I paint myself so far into a corner I may NEVER see the light of day again?
3. Assuming that both drives are not 100% dead meat, (and if they are, I'm screwed…), any ideas on the likelihood of resurrecting them? (i.e. has anyone else in TV Land experienced this?)