Synology drive crashed12/10/2023 Thanks all involved for helping me navigate my way though this & fingers crossed for the last few steps. I then removed /volume1 and have re-created it and am copying everything back onto it.įuture steps will be to then remove volume2 & re-add to the volume1 storage pool & get the RAID fixed back up. Sudo btrfs restore -x -m /dev/mapper/cachedev_0 /volume2/Recovery I then took 1 drive out of my 4 drive array & created a seperate volume (/volume2) and ran another recovery but this time using -x and -m to restore date/file stamps and other file metadata: The contents came out but all the timestamps etc. During the run I did get a few warning messages but nothing fatal. I didn't run it with any other switches at this point because I just wanted to see if I could rescue / pull files out. Sudo btrfs restore /dev/mapper/cachedev_0 /volumeUSB1/usbshare However I did attach a USB HDD (as /volumeUSB1 - and I made a share on it so I could see stuff coming back) and was able to do a file recovery using: Sudo mount -o recovery,ro /dev/mapper/cachedev_0 /volume1 Potential Problems with Synology NAS Systems Faulty RAID Controller Circuit problems Hit head on one or more hard disks Dirty read/write head Surface. Sudo mount -o recovery /dev/mapper/cachedev_0 /volume1 ![]() Sudo mount -o clear_cache /dev/mapper/cachedev_0 /volume1 ![]() PV UUID d55Kcs-wujY-TVXZ-Fcyz-8jqd-J2ts-Id5iFvįor anyone following along in future (and indeed myself) I didn't have any success mounting the FS using any of: LV UUID FpSGKA-76kU-3RsJ-rfwx-pona-3ydg-I4pII1 VG UUID ox16tw-smba-XftF-ckPN-7aO6-tPaz-OFKU35 I'm also being cautious after a Qnap failure years ago where I made things worse!Īny pointers for picking through what might be wrong much appreciated. I've opened a ticket to Synology but as I have a background in computer stuff wanted to try and understand what might have happened. Given that there hasn't been a drive failure (all seem happy in SMART - but know that isn't perfect) or a PSU/power failure issue to spark corruption I'm hoping I might be able to kick things a bit back into life. While I have backups of the critical bits I'd like to work through what might be possible to bring it back to at least a read-only state to take more complete backups. I have a 4 drive (12TB) array that all of a sudden went read-only & has now "crashed" so that it isn't mouting any file system.ĭevice was running DSM 6 when the volume was created and migrated to DSM 7 successfully a few months ago. Would really appreciate some help with unpicking what might have happened here.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |