December 1, 20241 yr Hello, Completely at random sometime tonight, perhaps during my monthly parity check my cache disk went boom. I was able to use dockers earlier in the evening but sometime after midnight I tried to use a docker and it was offline. I was unable to stop/start/restart containers so I stopped Docker service and could not restart. So I turned it off and on again I did a reboot of Unraid. Once the server was back online the cache disk showed Unmountable: Unsupported or no file system. I tried to fix it myself following guidance elsewhere on these forums but ran into an error so I'm reaching out for helppies. Here is the output of what I attempted to do, also Attached is the diagnostics. ----------- oot@Magnetar:~# sfdisk /dev/nvme0n1 Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 970 EVO Plus 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x300c166f Old situation: Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 2048 1953525167 1953523120 931.5G 83 Linux Type 'help' to get more information. >>> 64 Created a new DOS disklabel with disk identifier 0x2e0db9a5. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. /dev/nvme0n1p1 : 64 1953525167 (931.5G) Linux /dev/nvme0n1p2: ^C root@Magnetar:~# sfdisk /dev/nvme0n1 Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 970 EVO Plus 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x300c166f Old situation: Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 2048 1953525167 1953523120 931.5G 83 Linux Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0xfca7f540. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o: No /dev/nvme0n1p1 : 2048 1953525167 (931.5G) Linux /dev/nvme0n1p2: write New situation: Disklabel type: dos Disk identifier: 0xfca7f540 Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 2048 1953525167 1953523120 931.5G 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. /dev/nvme0n1: fsync device failed: No data available root@Magnetar:~# magnetar-diagnostics-20241201-0417.zip
December 1, 20241 yr Community Expert 1 hour ago, faefangirl said: I tried to fix it myself following guidance elsewhere on these forums You should not run commands you see in the forum without asking for help first, they may not apply to you and do more damage, though in this case, it didn't matter, since the device is the problem: === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: FAILED! - available spare has fallen below threshold - media has been placed in read only mode
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.