June 17, 20224 yr Just now, In2Photos said: The server had been working fine until today since 2015 when I did the conversion. Do you have a screenshot or diagnostics from when it was working?
June 17, 20224 yr Community Expert Can you actually access any data from your server? If the disks were mounted, your user shares should work, and their data would be available.
June 17, 20224 yr Author I have already installed a fresh OS on the flash drive and verified that it boots. I've done basic configuration of things like static IP. Just waiting for the new drives to arrive. Should I go into maintenance mode and check the disks?
June 17, 20224 yr Do you have the disk filesystems set as auto or did you force it to XFS? It won't hurt anything to set them as ReiserFS just to see if they mount, just don't ever click the format button if it asks.
June 17, 20224 yr Author 2 minutes ago, JonathanM said: Do you have a screenshot or diagnostics from when it was working? No I don't believe I do. Here is where the system sits right now. I'm basically where I was this morning before checking for updates.
June 17, 20224 yr Community Expert 4 minutes ago, JonathanM said: Do you have a screenshot or diagnostics from when it was working? Only one other thread between that one and this, shortly after "conversion", and nothing there to clear this up.
June 17, 20224 yr Community Expert 2 minutes ago, trurl said: Can you start the array and post new diagnostics?
June 17, 20224 yr Author 4 minutes ago, trurl said: Can you start the array and post new diagnostics? Here you go. And a screenshot. mytower-diagnostics-20220617-1654.zip
June 17, 20224 yr Community Expert Disk1 unmountable but we already know it is bad and its data may be lost. User shares are working.
June 17, 20224 yr Well, the screenshot proves me wrong on the ReiserFS theory, and it also shows data that you probably want to keep on the 500GB drive, so removing it without copying the data elsewhere probably isn't what you want. Have you run the filesystem check on disk1 with the new version of Unraid in maintenance mode yet?
June 17, 20224 yr Community Expert And parity disk is bad as we already knew. No point in even having it in the array unless you want to try and fake unraid into emulating disk1 with it.
June 17, 20224 yr Author 5 minutes ago, JonathanM said: Well, the screenshot proves me wrong on the ReiserFS theory, and it also shows data that you probably want to keep on the 500GB drive, so removing it without copying the data elsewhere probably isn't what you want. Have you run the filesystem check on disk1 with the new version of Unraid in maintenance mode yet? I have not run filesystem check but I can. 1 minute ago, trurl said: And parity disk is bad as we already knew. No point in even having it in the array unless you want to try and fake unraid into emulating disk1 with it. Are we absolutely sure the parity disk is bad?
June 17, 20224 yr Community Expert 1 minute ago, In2Photos said: Are we absolutely sure the parity disk is bad? Even worse than disk1. Parity: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 1871 197 Current_Pending_Sector -O--CK 196 196 000 - 2164 198 Offline_Uncorrectable ----CK 198 196 000 - 1264 199 UDMA_CRC_Error_Count -O--CK 200 198 000 - 5 200 Multi_Zone_Error_Rate ---R-- 054 048 000 - 50224 Disk1: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 197 Current_Pending_Sector -O--CK 196 196 000 - 1160 200 Multi_Zone_Error_Rate ---R-- 199 199 000 - 270
June 17, 20224 yr Community Expert Just now, In2Photos said: I can't run the check on disk 1 since it is not mountable. Running filesystem check on unmountable disks is the way to make them mountable. You have to start the array in Maintenance mode.
June 17, 20224 yr 1 minute ago, In2Photos said: I can't run the check on disk 1 since it is not mountable. You can't run the check if it is mounted. It must be unmounted to check it.
June 17, 20224 yr Author OK, so that's not the reason, but I still can't run the check. The option isn't there for disk 1.
June 17, 20224 yr Community Expert It doesn't know what filesystem check to run since it doesn't know what filesystem it is supposed to be (and neither do we).
June 17, 20224 yr Try changing filesystem type to XFS, run a check and post the results, if no good outcome, we can try changing to ReiserFS and see if the results are any better. Leave the -n so we just get a view of what may happen, it won't commit any changes.
June 17, 20224 yr Community Expert 3 minutes ago, JonathanM said: Change the filesystem type on disk 1 to XFS. But don't start the array or let it format the unmountable disk. Just try to do the check.
June 17, 20224 yr Community Expert Just now, JonathanM said: Leave the -n so we just get a view of what may happen Capture the results and post them
June 17, 20224 yr Author Same results as earlier today. Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error
June 17, 20224 yr Community Expert Just now, In2Photos said: Same results as earlier today. Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error That is with xfs I assume. That might indicate that the disk isn't xfs.
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.