I've updated to 6.2.3 and now one of my 4 volumes is crashed. I'm running on VMWare and I applied the synoboot fix from here:
The sata drives that appeared wrongfully are gone, so that's good, but my volume1 is still crashed. The pool and disk both still are good. All volumes and pools are on a separate disk and are basic, no RAID or something. I believe SHR. IIRC it was btrfs.
I can still cd to /volume1 via SSH, but I only see a `@database' folder with mariadb10 it seems. So can this be fixed somehow? Or is everything gone?
Question
Bose321
I've updated to 6.2.3 and now one of my 4 volumes is crashed. I'm running on VMWare and I applied the synoboot fix from here:
The sata drives that appeared wrongfully are gone, so that's good, but my volume1 is still crashed. The pool and disk both still are good. All volumes and pools are on a separate disk and are basic, no RAID or something. I believe SHR. IIRC it was btrfs.
I can still cd to /volume1 via SSH, but I only see a `@database' folder with mariadb10 it seems. So can this be fixed somehow? Or is everything gone?
Thanks in advance.
Link to comment
Share on other sites
10 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.