ktran

My unRAID server has been rebooting on its own recently and after running the "Fix Common Problems" tool, I see the following error [Machine Check Events detected on your server - Your server has detected hardware errors]. I have generated and attached Diagnostic file as suggested. skynet-diagnostics-20240912-1522.zip

Thank you so much! This fixed my issue. Server has been up since I applied the change in my BIOS.

I have an issue with my unRAID server where I can't access the GUI after a day or two of it being online. A hard restart of the server would fix the issue but then the server would go offline again after a day or two. At first, I thought it might be the USB flash drive, which I had replaced but then the issue happened again two days ago. One thing I want to note is that there has been a few power outages at my place before and after I replace the USB flash drive. Diagnostics log has been attached. Thank you in advanced. skynet-diagnostics-20230313-1125.zip

So basically rebuilding my disk1 from parity is no longer an option? Thank you everyone for all your help with this. I might have to turn to a data restore software to try to retrieve the data. Once again, thank you again so much for all the help. I greatly appreciate it.

So if data were added recently, would that cause any issues while rebuilding disk1? As for disk4, that's where my most recent data are stored.

I've attached the original config of the disks prior to the incident as well as the current config (which was done to get the system online temporarily). In the current config, I did not add back the 14tB parity disk since I'm hoping I can rebuild DISK 1 (SN# 8CJLUPOE - sdb), and was afraid if I had re-add the parity disk, the data would get overwritten.

Please see output below: root@SKYNET:~# xfs_repair -v /dev/sdb1 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .....found candidate secondary superblock... unable to verify superblock, continuing... ...found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... ............................................ Sorry, could not find valid secondary superblock Exiting now.

New diagnostics attached Thanks. skynet-diagnostics-20211205-1907.zip

When I came back to check the repair status on the GUI/CLI, the tab for the terminal was closed out. I didn’t get to see the result and the disk is not able to mount. The “Mount” option is still greyed out. At this point, what are my other options?

So I ran xfs_repair -v /dev/sdb1 and it looks like it completed. However, I'm not sure where to go to grab the logs. Can someone help me please? Thank you.

Thanks. Running repair now. Will let you know how it turns out.

Thank you for the clarification. So does that mean both my Parity Disk 1 and my Data Disk 1 are no longer accessible since the option to mount them are greyed out? Also, if I assign disk 2, 3 & 4 back into the Array devices without the Parity Disk 1 and Data Disk 1, will my unRAID system will be able to function? And if so, will it affect my array or my data without the other two disks? I was hoping I can still have my unRAID system running while we look into options to try to restore data to Disk 1 if possible.

I haven't assigned any disks to the Array devices because I was afraid if I did, it would overwrite any data I have on the affected disk (DISK 1). However, I do know what my disk assignments are supposed to be prior to the mishap. As for the Unassigned Devices, the "Mount" option is greyed out on the affected disk (DEV 5) so I'm assuming it's already mounted?

Affected disk mounted and new diagnostics attached. Thank you. skynet-diagnostics-20211203-0924.zip

Diagnostic has been attached. Thank you. skynet-diagnostics-20211202-1701.zip