davejcb

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by davejcb

  1. Alexandro, That sounds EXACTLY like what happened to me! I was thinking the same thing that these problems have only started happening since RC8a...
  2. Any kind of help, please? I would truly appreciate suggestions.
  3. OK, I need help here- I've copied over the data from my 2nd data drive to USB drive, data is safe. Both the 2nd data disk and the parity disk are yellow, and show as DISK_INVALID under unMENU. I've run SMART reports on the data drive it seems fine, only the filesystem is corrupt. I try and format the drive from the main menu, but nothing happens. If I pop in a fresh disk it says "Invalid expansion" and won't accept it. I can't format, can't add a disk, can't remove the parity drive, what CAN I do here???
  4. Little update- I've taken the 2nd data drive and connected it to an Ubuntu PC, and was able to mount it and see the contents, all of which seem to be intact. I have a brand new drive, not sure of the order of things I should take... The drive is currently unformatted. Should I: 1- leave the data drive disconnected, connect the new drive and pre-clear it, assign it to the array, then return the data drive and copy it over? 2- copy the data via dd after pre-clearing the new drive and assigning it to the array? Thanks for the advice!
  5. The SMART reports... sda.txt sdc.txt sdd.txt sde.txt
  6. Not a lot more to find in the log... log.txt
  7. Apologies for missing that. Here it is... log.txt
  8. Good morning all, I'm running the latest 5.0-rc8a, with two 2TB WD Green data drives, 1 2TB WD Green parity drive, and one 500GB Maxtor cache drive. I noticed yesterday that my second data drive was unassigned, and in unMENU was showing as DISK_INVALID. Shut the server down, checked cables, rebooted, the disk was there, but had a yellow dot next to it. Tried rebuilding it, was taking forever (300kb/sec), cancelled it. At this point, my parity drive showed as unassigned! Rebooted, the drive is assigned but with a blue dot (new drive). I'm not sure where to go from here- I fear that I now have a lost second data drive with an invalid parity drive that I can't use to rebuild from. I have the option of starting the array and parity-syncing, but I fear what would happen if I did this. I'll be heading out today to pick up a new 2TB disk. I'm thinking of dd'ing the second data disk to this new drive as a backup in case the worst happens. So to recap, I currently have my second data drive with a yellow dot and my parity drive with a blue dot, array is not started. I welcome your advice. Dave