Post by grayarea on Mar 22, 2007 19:18:56 GMT 7
Hi All,
I had a strange issue with a new 5200;
I patched up to 1.0.8 from 1.0.4 and then built a raid set on 5 Samsung t120 250Gb drives.
During initial copy of data onto the share I noticed that the fifth drive was not as active as the other drives, this I though was suspicious as I am a database consultant and regularly get involved in RAID builds etc. The only other visible issue was that the LCD had frozen.
Anyway I rebooted the device last night and the unit came up degraded. The problem drive was the fifth and I selected it as a spare and added it to the array and it rebuilt overnight.
This morning all appears OK and the fifth drive activity is now at the same level as all the other drives during access.
I check the log and saw that the array switched to degraded and recovered itself to normal status during the day yesterday. It appeared from the log to be OK when powered down.
This morning I have rebooted the system twice and all appears to be OK.
Later,
Grayarea.
I had a strange issue with a new 5200;
I patched up to 1.0.8 from 1.0.4 and then built a raid set on 5 Samsung t120 250Gb drives.
During initial copy of data onto the share I noticed that the fifth drive was not as active as the other drives, this I though was suspicious as I am a database consultant and regularly get involved in RAID builds etc. The only other visible issue was that the LCD had frozen.
Anyway I rebooted the device last night and the unit came up degraded. The problem drive was the fifth and I selected it as a spare and added it to the array and it rebuilt overnight.
This morning all appears OK and the fifth drive activity is now at the same level as all the other drives during access.
I check the log and saw that the array switched to degraded and recovered itself to normal status during the day yesterday. It appeared from the log to be OK when powered down.
This morning I have rebooted the system twice and all appears to be OK.
Later,
Grayarea.