Ira Posted November 10, 2021 Share Posted November 10, 2021 So i let my Unraid server shutdown and didnt use it for about 1-2 months when i came back and booted it up i was meet with my drive dont wanna mount. It say error but i ran extended S.M.A.R.T test no problems there. So what do i do now as this is my Data drive and the other is almost empty >_< Screenshot show server after start. Added diagnostics in case they are needed. I hope someone can help me please. tower-diagnostics-20211110-2047.zip Quote Link to comment
trurl Posted November 10, 2021 Share Posted November 10, 2021 https://wiki.unraid.net/Manual/Storage_Management#Drive_shows_as_unmountable Quote Link to comment
trurl Posted November 10, 2021 Share Posted November 10, 2021 Looks like you were having connection problems with disks 1 & 2 while you were running a correcting parity check, so parity might not be good. 03:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11) Marvell controllers are NOT recommended. Probably also the cause of your unmountable disk. Dual parity is overkill for only 2 data disks. Quote Link to comment
Ira Posted November 12, 2021 Author Share Posted November 12, 2021 So i ran a check as the guide said and this is what i got but i dont know what it mean about "mount the filesystem" Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. Quote Link to comment
Ira Posted November 12, 2021 Author Share Posted November 12, 2021 Also for some reason i have 1 drive in xfs and 1 btrfs im pretty sure they should be the same but im 100% i didnt change anything like filesystem Quote Link to comment
trurl Posted November 13, 2021 Share Posted November 13, 2021 3 hours ago, Ira said: use the -L option to destroy the log and attempt a repair. Quote Link to comment
Ira Posted November 13, 2021 Author Share Posted November 13, 2021 Will my date be gone if that fails? Quote Link to comment
JorgeB Posted November 13, 2021 Share Posted November 13, 2021 There could always be some data loss after a filesystem repair, it depends how corrupt it is, most times there isn't any or anything relevant, check for a lost+found folder after it finishes. Quote Link to comment
Ira Posted January 6, 2022 Author Share Posted January 6, 2022 I ran the -L and this is what i got back Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 7 - agno = 2 - agno = 8 - agno = 4 - agno = 3 - agno = 6 - agno = 9 - agno = 10 - agno = 1 - agno = 5 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:2869553) is ahead of log (1:2). Format log to cycle 4. done Stoped the system after and started it again and all seem fine But is it fine? If not please let me know what i need to if yes then... Thank you very much for you help. Quote Link to comment
ChatNoir Posted January 6, 2022 Share Posted January 6, 2022 You should check if there is a lost+found share on this drive and how much might be in it. Quote Link to comment
Ira Posted January 6, 2022 Author Share Posted January 6, 2022 7 minutes ago, ChatNoir said: You should check if there is a lost+found share on this drive and how much might be in it. How do i see that? Quote Link to comment
ChatNoir Posted January 6, 2022 Share Posted January 6, 2022 On the Main page, open check the content for this drive. Quote Link to comment
Ira Posted January 6, 2022 Author Share Posted January 6, 2022 Ah i knew i had been there befor just forgot where to look >_< No new folders in there so all is good? Quote Link to comment
ChatNoir Posted January 6, 2022 Share Posted January 6, 2022 3 hours ago, Ira said: Ah i knew i had been there befor just forgot where to look >_< No new folders in there so all is good? If there are no lost+found folder on the top level, it probably means that everything was recovered OK. Quote Link to comment
Ira Posted February 14, 2022 Author Share Posted February 14, 2022 Now i have problems again multiple drives is getting error. Can this be a cable problem? I have removed the SATA controller and all are connected to MB. tower-diagnostics-20220214-1217.zip Quote Link to comment
JorgeB Posted February 14, 2022 Share Posted February 14, 2022 Looks more like a power/connection problem. Quote Link to comment
Ira Posted February 14, 2022 Author Share Posted February 14, 2022 so i need new power cabel? Quote Link to comment
JorgeB Posted February 14, 2022 Share Posted February 14, 2022 It's affecting multiple disks, so depending on how they are connected could be cable/splitter, bad PSU or just how the load is distributed. Quote Link to comment
Ira Posted February 14, 2022 Author Share Posted February 14, 2022 Holy hell >_> I had 4 drive and 12 fans on same power cable with 3 splitter.... I have now changed this to 2 HDD for each cable and Fans on its own cable. Now it say my Parity drive is disable (maybe there were befor i changed around on cables i didnt notic) so how do i re-enable them? Quote Link to comment
Ira Posted February 14, 2022 Author Share Posted February 14, 2022 Found this and tried now it say "Parity-Sync/Data-Rebuild in progress." Quote Rebuilding a drive onto itself There can be cases where it is determined that the reason a disk was disabled is due to an external factor and the disk drive appears to be fine. In such a case you need to take a slightly modified process to cause Unraid to rebuild a 'disabled' drive back onto the same drive. Stop array Unassign disabled disk Start array so the missing disk is registered Important: If the drive to be rebuilt is a data drive then check that the emulated drive is showing the content you expect to be there as the rebuild process simply makes the physical drive match the emulated one. Is this is not the case then you may want to ask in forums for advice on the best way to proceed. Stop array Reassign disabled disk Start array to begin rebuild. If you start the array in Maintenance mode you will need to press the Sync button to start the rebuild. This process can be used for both data and parity drives that have been disabled. Does this mean that all shoud be okay now? Quote Link to comment
trurl Posted February 14, 2022 Share Posted February 14, 2022 50 minutes ago, Ira said: Found this and tried now it say "Parity-Sync/Data-Rebuild in progress." Does this mean that all shoud be okay now? That is the correct way to proceed. On Main, you should see lots of Writes on parity, lots of Reads on all other disks, zero Errors for all disks. Quote Link to comment
Ira Posted February 21, 2022 Author Share Posted February 21, 2022 So its done all looks fine i have had to shutdown due to move but now it have up time of almost 48 hrs no problems with error. Thank you all for now Quote Link to comment
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.
Note: Your post will require moderator approval before it will be visible.