The identical partititioning shemes of drives #1 and #2 could suggest this. The computer technician who usually cares for this company believes that the system was in RAID 1. So, there is some conflict between the two drives, as they were same.ĭrive #3 as well as drive #4 have a unique RAW partition which covers all the drive. The partitioning sheme of drives #1 as well as drive #2 is as follows: Code: 100 Mb (EFI system partition)ĥ528.78 RAW When drives #4 is attached to another computer, whilst drive #3 is, it is not "In line" but "Off line" in the disk manager.īut when attached alone, it is becomes "In line". The customer doesn't remember which kind of RAID was used, nor the total storage capacity. We also tried starting the system without the drive #3.Īccording to the Administrator's Guide,, the system supports RAID 1 and RAID 5. We swapped drive #3 with its clone, but this did not suffice to restore the system. The cloning revealed that the amount of bad sectors was about 67 Kb. We cloned it to a healthy drive of the same model (WD RE4-GP WD2002FYPS). They were ok, excepted for drive #3, which had a few bad sectors. The small display panel of the NAS displays: Code: Initializing OKįAILED: 0xD9 We checked the S.M.A.R.T. The four drives initialize and a small blue diode appears in front of each drive when it is ready. We received a WD Sentinel DX4000 NAS storage with 4 x 2 TB that the customer forgot to switch off before a planned power outage, and which now refuses to start.Ī priori, the NAS enclosure itself is working.
0 kommentar(er)
