Search the Community
Showing results for tags 'volume crash'.
Hi together i got a problem with a crashed volume and my knowledge is now on a point where I need some help I already did a few lines to identify a failure (attached because the forum doesn't like it) I found in the above response these two error lines, but couldn't find anything else about it Found dropping subvolume ID:10011501971644612608 dropping progress: key (259824214343680 UNKNOWN.0 697453126021545984) level: 0 Errors found in extent allocation tree or chunk allocation commands.txt
After 4-5 years happy usage of Debian9 + Proxmox5.2 + Xpenology dsm 5.2 I upgraded six months ago to DSM6.2.3 Proxmox6.3-3 Debian10. All went well, until a few weeks ago... One night at 3am my volume 2 crashed! Since then I can read my shares from volume 2, but not write. It is read-only. I suspect the activation of write back cache in proxmox is the reason. Status of SMART and all my harddrives and raid controller is just fine, so I suspect no hardware issue. After using google, this forum and youtube I still have no solution. The crashed volume has all my musi
Hello everyone, Please Help, my xpenology has Volume 1 crashed error and all the data in it is not accessible How do i fix that? I install xpenology on ESXi 6.7 Here is the screenshot of the error
Hello, I am trying to either get the system to mount or recover the data. My volume crashed with no system reboot or OS crash. I have looked through the forums and have performed some items with no success and I'm hoping someone can assist with the issues. I have gone through all the steps other than the repair command by following the info found in this thread Volume Crash after 4 months of stability . Below are the commands that I have run so far and I have attached a text file with the results since I kept getting an error when posting the results. fdisk -l