Storage Manager / Storage Pool shows all the drives: Drive 1, 2, 3, 4 all as "Healthy" for Allocation Status and "Healthy" for Health Status.Start Repair, add Drive 3 to volume, initializing Drive 3.
Repair option was not available when volume status was in Crashed status. Repair option on Action button is now available. Despite the bad sectors, Storage Manager / Storage Pool shows Drive 1, 2, 4 as "Healthy" for Allocation Status and "Healthy" for Health Status.Storage Manager shows Drive 3 detected and Uninitialized. Storage Manager displays message that Drive 1 and now Drive 4 have bad sectors (ugh, now Drive 4 is failing.).Beep alert says volume is Degraded (nothing new, I've been seeing this on restart for the past 2 days). Remove Drive 3 and replaced with brand new WD Red drive.No problems, despite previous error that Drive 1 had 1 bad sector and volume was Crashed. Copied all 2.5 TB of files and folders with File Station to the external USB drive.Backup export the DSM configuration from Control Panel.Purchased a 5 TB external USB 3.0 drive from Best Buy.Play-by-play attempt to repair/restore/recover: FWIW, I did backup the Synology configuration too. If I have to start with 4 new drives from scratch, that's ok, I have backups, but I'd prefer to repair the volume. I do Hyper Backup every night and Cloud Station Drive sync to my laptop, so I have backups of the data.Ĭan the volume be repaired if I replace Drive 3, then if it rebuilds replace Drive 1? I will certainly be replacing Drive 2 and 4 too. None of the packages would start but the files seem to be ok for the ones I tried. This morning, while still Degraded and I haven't received the blank drive yet, Drive 1 detected 1 bad sector and the volume went to Crashed status immediately. I ordered another WD Red drive next day air and knew the RAID would rebuild once the new drive arrives today. I had to shutdown and restart my NAS last night as I was moving it to a new location.ĭrive 3 wouldn't spin up and the volume went to Degraded status. This is used in my home for my IT consulting business, just by myself. But my theory is that these events when the disks were connected by ESATA, has caused the DS to "blacklist" these disks, as they have once caused "reset commands" due to flaky cables.I have a DS918+ with 4 WD Red NAS drives in one volume with SHR RAID. This was probably because of older unstable ESATA cables. First, I tried connecting the two problematic disks using the 2 ESATA ports of the DS1515+, but the disks did never appear in the storage manager, and I saw some reset/connection errors in the dmesg log (using the linux terminal). I suspect that the disks are rejected by the DS because of some historic data. So why is Storage Manager stuck on the Critical status?īoth disks work completely fine when connected to another computer, so I believe they are physically 100% OK. I've looked in the dmesg output from the linux terminal of the DS, with no errors for the disks that cause me trouble.īut I can see in all the extended views that no errors regarding reset/reidentification/reconnection etc have occurred. I've tried secure erasing one of the disks, with no luck. The error is "Multiple reset command errors have occurred.".įrom the Storage Manager, I cannot continue and the system won't let me intialize the disk to make it part of a storage pool.
#SYNOLOGY DRIVE CRASHED CANT ACCESS LOGIN PAGE INSTALL#
I have bought 3 of these drives, and 1 of them works fine and is now part of my storage pool, but the other 2 gives me an error when I install them in the DS. The hard drives are brand new Seagate Exos X. I am trying to install a new HDD in my DS1515+.
0 kommentar(er)
