-
UnRaid identified two disks as the same and became umountable after data rebuild.
Started data rebuild on disk 15 now but seems it lost 90% of its data somwhere along the way.
-
UnRaid identified two disks as the same and became umountable after data rebuild.
Check filesystem did indeed find a corrupt filesystem and was able to fix it. I did not unfortunately, possibly faulty HBA card?
-
UnRaid identified two disks as the same and became umountable after data rebuild.
First reboot all my 16 disks were missing. Proceeded to boot again in safe mode and all disk were identified correctly. Third normal boot all disks are still identified correctly and running. However disk 15 is still unmountable. horserver-diagnostics-20260614-1334.zip
-
UnRaid identified two disks as the same and became umountable after data rebuild.
It started with problems on disk 14, disk 14 was disabled and giving lots of UDMA CRC error count. I was suspecting bad sata cable so i wanted to switch sata cable between disk 14 and disk 15 to see if the problem followed. No problems on disk 15 and array was valid since disk 14 was emulated. I proceeded to stop the array, unplugged both sata data and power from both drives, and swapping sata data cable between the two drives. Started the array without disk 14 which was disabled and emulated. Stopped the array. Started the array and initiated a data rebuild on disk 14. However as soon data rebuild started, both disk 14 and disk 15 showed up in the array as unmountable. As seen in the screenshots unRaid gave both drives the same identifier (sdm) and the same serial number. How did this happend and what can do to prevent this in the future and whats my best course of action to save as much data as possible? horserver-diagnostics-20260613-1400.zip
virre
Members
-
Joined
-
Last visited