Hi Steeldriver,
ok, i'm a dope! I didn't realise that there was a page 2 to this message so I didn't see your reply until now! Duh!
I turned off the PC and restarted it and now (of course!) it is saying something different to me. When I run "sudo mdadm --assemble --scan" it tells me:
Code:
mdadm: /dev/md0 has been started with 1 drive (out of 2).
mdadm: failed to add /dev/sdb2 to /dev/md1: Invalid argument
mdadm: failed to add /dev/sda2 to /dev/md1: Invalid argument
mdadm: /dev/md1 assembled from -1 drives and 1 spare - not enough to start the array.
mdadm: failed to add /dev/sdb2 to /dev/md1: Invalid argument
mdadm: failed to add /dev/sda2 to /dev/md1: Invalid argument
mdadm: /dev/md1 assembled from -1 drives and 1 spare - not enough to start the array.
running "sudo mdadm --detail /dev/mdX" tells me:
Code:
/dev/md0:
Version : 0.90
Creation Time : Fri Mar 27 06:32:58 2009
Raid Level : raid1
Array Size : 1020032 (996.29 MiB 1044.51 MB)
Used Dev Size : 1020032 (996.29 MiB 1044.51 MB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun May 20 16:44:28 2012
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : f4bbf855:b2d100c6:39ef04d2:f61103c6
Events : 0.1473386
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 1 1 active sync /dev/sda1
and, rather dissapointingly ...
Code:
mdadm: cannot open /dev/md1: No such file or directory
You are right, as I was having problems with the NAS I did try replacing the poorer disk with a new disk hoping that would cause it to spring back into life ... it didn't. And it confirmed to me that there was a fault with the device itself, not just a disk problem. It sounds like trying that did not help. Sorry for that.
When I look at the disk utility it tells me that each disk has two RAID components. One of 1GB (sda1 and sdb1) and one of 999GB (sda2 and sdb2). I am assuming that the data is in the "2"s and the "1"s are maybe where the device keeps some software etc.
In case it helps, here are the latest "sudo mdadm --examine /dev/sdX2" results:
Code:
/dev/sda2:
Magic : a92b4efc
Version : 0.90.00
UUID : 00000000:00000000:00000000:00000000
Creation Time : Sat May 19 05:43:43 2012
Raid Level : -unknown-
Raid Devices : 0
Total Devices : 2
Preferred Minor : 1
Update Time : Sun May 20 15:08:26 2012
State : active
Active Devices : 0
Working Devices : 2
Failed Devices : 0
Spare Devices : 2
Checksum : 82b4eeca - correct
Events : 1
Number Major Minor RaidDevice State
this 0 8 2 0 spare /dev/sda2
0 0 8 2 0 spare /dev/sda2
1 1 8 18 1 spare /dev/sdb2
and
Code:
/dev/sdb2:
Magic : a92b4efc
Version : 0.90.00
UUID : 00000000:00000000:00000000:00000000
Creation Time : Sat May 19 05:43:43 2012
Raid Level : -unknown-
Raid Devices : 0
Total Devices : 2
Preferred Minor : 1
Update Time : Sun May 20 15:08:26 2012
State : active
Active Devices : 0
Working Devices : 2
Failed Devices : 0
Spare Devices : 2
Checksum : 82b4eedc - correct
Events : 1
Number Major Minor RaidDevice State
this 1 8 18 1 spare /dev/sdb2
0 0 8 2 0 spare /dev/sda2
1 1 8 18 1 spare /dev/sdb2
I have a feeling I need to go down the "pull everything apart route" that you talked about. Sounds fun!
Bookmarks