and 'crashed' once I reboot it after it freezes out at the end of the disk check process. the NAS lists it as 'not initialized' when it goes in clean at first, 'initialized' once it's building the volume. Checking filesystem on /dev/md2 UUID: 7a29febb-e9b5-4f77-afd7. btrfsck /dev/md2 Syno caseless feature on. In order to stop I/O to the volume (although it was already in RO mode per the output of dmesg above. I don't believe it has anything to do with the drive, since I am running the exact same drive in it already. This stops the WebUI etc., but keeps SSH on. (Be sure you have alerts working, especially if your NAS is in a location. Checking email confirmed my suspicion that a drive had failedthe storage pool was in a degraded state. What I've done so far: I've bought two new 4TB WD Red Plus drives. This is very annoying, and I can't figure out why the NAS is being uncooperative with loading this volume/HDD. Today I arrived in my office to hear my new Synology DS-1520+ NAS beeping softly. It gives a 'Crashed/Healthy status' I can't get an extended smart test to complete (hangs at 90) I can't back up to the new drive I can't add the new drive to the existing pool I can't get repair the old drive / pool. I loaded the HDD to my desktop to look at it, and it had several small partitions on it (presumably from the multiple times I've added the volume), so I formatted it to nothing, tried again. I've repeated this several times, exact same behavior each time. Upon restart it tells me the new volume on the new disk has crashed. I have to physically pull the power plug (it won't shut down when I press the power button) to restart it. after disk checking (which takes hours), the NAS locks me out, and drops off the network. I added a NEW WD Black 500GB drive (exactly the same as one that's already running in the NAS), and configured it, adding a volume on the new standalone drive (No RAID). The OS and configuration are held within a partition on each drive. Common reasons of a volume crash A drive has been kicked from its corresponding storage pool because of severe bad sectors the number of drives kicked from a RAID configuration has reached the maximum drive fault tolerance. As for a NAS failure, you can move the drives (in the same order) to another NAS and youll be good. To solve this problem, we recommend contacting Synology Technical Support. However, you can just click on the volume and run a repair. When the status of a volume becomes Crashed, you cannot repair the volume by yourself. I have the Synology ds411slim NAS, no problems thus far. When the drive is reinserted it will still show as crashed.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |