September 28, 20241 yr About a week ago I bought a 12tb Western Digital hard drive from ebay to add to my array. So I shutdown my server added the hard drive as my 6th drive and restarted my server. Once I logged back in to unraid I noticed it showed my 5th drive as missing. Ignoring that for the moment I attempted to do a preclear on the 12tb drive and I don’t think it was successful. I then restarted my sever a few time removing then reconnecting both drive 5 and 6. Eventually I was able to see drive 5 again but both drive 5 and 6 were showing unmountable disc. I was able to fix drive 5 with -v in check filestatus system. However drive 6 I could not get to run -v nor could I get it to format. I then shut down and removed drive 6 and attempted to plug it into my desktop. The drive did not show up in “my computer” but it did show up in “device manager” Being new to all of this I’m not sure if there is anything I can do to get the drive to work or if I should contact the ebay seller. And have any of you experienced a drive dissapearing after connecting a new drive? Also I’m not sure if it is related but while I was dealing with the drives Qbittorrent stopped working. Adjusting some of the setting I accidentally uninstalled it. After reinstalling Qbittorrent and adjusting the “Host Path for /data” I was able to download again. It appeared to be working fine. New episodes automatically started to download but after the download finishes Sonarr no longer automatically pulls the episode. Checking on Sonarr it says it cant find the file to import it. So I checked the download folder and I cant find any of the episodes that should have been downloaded to the folder.
September 28, 20241 yr Community Expert Please post the diagnostics after a format attempt of the new disk.
September 29, 20241 yr Author Well it seems my issues dont stop there. After removing drive 6 from my server to check it on my desktop I did not put it back in my server. I then performed "New Config" while preserving all current assignments to remove drive 6. I wanted to get my serverback to how it was before I tried adding a new drive. I then restarted my array and found drive 1 is now showing "Unmountable". I then restarted the array in maintenance mode and checked drive 1 and found the file system switched from XFS to Auto and the partition format is MBR while the rest of the drives are GPT. Not sure if that matters. I did switch the file system back to XFS but I'm assuming to change the partition format would require me to format the drive which would earase all the data on the drive? And -v is not working on drive 1. Another issue now is after doing the New Config it is now running Parity Sync. I'm guessing it doesnt matter since drive 1 is Unmountable? Though the reads on drive 1 is going up. Also now drive 5 is showing alot of errors during this parity sync. I've included the current diagnostics postserver-diagnostics-20240929-0530.zip
September 29, 20241 yr Community Expert 6 minutes ago, Smp524 said: I'm guessing it doesnt matter since drive 1 is Unmountable? No, that's normal after a new config, unless you check "parity is already valid". There are constant read errors with disk5, cancel the parity sync, replace cables for that disk, and post new diags after array start.
September 30, 20241 yr Author Alright I swapped the data cable and it was still getting errors. So I tried switching which port it was connected to and now it shows "Not Installed" So I treied a couple differtent ports and then went back to the original port but it is still showing "Not Installed". I then changed the power cable with no change. postserver-diagnostics-20240930-0713.zip
September 30, 20241 yr Community Expert See if the disk is power up, or test it in a different computer, if the disk is not detected, not much you can do, since parity wasn't yet valid.
October 1, 20241 yr Author I removed drive 5 and connected it to my desktop and it looked like it was reading but it showed as a 16tb drive even though it is supposed to be a 3tb drive. I then hooked up drive 5 and drive 6 back into the server. I can see both of them when I use the drop down menu to choose which disk I want for the drive. Disk 5 is showing as emulated. And now Drive 3 is showing that the disk is missing. I’ll mess around with it and try it on the desktop when I get home.
October 3, 20241 yr Author Alright. A couple days ago I was able to get all of the drives to connect and when I started the array it started a data rebuild on drive 5. Data rebuild is slow going. Only 8.5% in 1 day 20 hrs but so far no errors. So I guess I'll let the data rebuild finish before trying to get drive 1 back and add drive 6. postserver-diagnostics-20241003-1555.zip
October 4, 20241 yr Community Expert There are constant ATA errors with multiple disks, looks like a power/connection issue.
October 7, 20241 yr Author Well shit. I tried another PSU as well as another PCIE card as well as new cables for power and data. And now the parity drive is showing missing. I've been messing with which sata ports I use and have not been able to get the parity back. Since I've changed everything else I'm guessing it is probably the board. Unless you have any other ideas.
October 7, 20241 yr Community Expert Could be the board, but it's not the most likely, do you hear the parity drive spinning up?
October 7, 20241 yr Author Parity drive is spinning up. If it is the drive is there any way to get info off of it. Drive 5 shows it is being emulated and I'd rather not lose everything from it.
October 8, 20241 yr Community Expert Swap both cables from parity with a different disk, then post new diagnostics.
October 8, 20241 yr Author I dont know if it matters for the download but it is not letting me start the array with the parity missing. I swapped the power and data cables from drive 1 and still no change. postserver-diagnostics-20241008-0524.zip
October 8, 20241 yr Community Expert If swapping cables didn't help it looks like parity is really dead, so no option to rebuild, in that case you can do a new config to see if the actual disk still has some valid data: Tools - New config
October 8, 20241 yr Author No luck. Still not showing as an option. On the bright side I do have that 12TB drive I was originally trying to add to the array. I guess I'll use that for the Parity now. What's the best way of getting Drive 1 and 5 working hopefully losing the least amount of data possible. BTW I just want to say I appreciate all the help you've been giving me.
October 9, 20241 yr Author Sorry I forgot to add the diag to my last post. Both 1 and 5 are showing Unmountable. postserver-diagnostics-20241008-1552.zip
October 9, 20241 yr Author On disk 1 I get 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. And for disk 5 I got Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... agf_freeblks 28301873, counted 28301834 in ag 2 agf_freeblks 11276465, counted 11276478 in ag 3 agf_freeblks 33841640, counted 33841636 in ag 0 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 imap claims a free inode 736710638 is in use, correcting imap and clearing inode cleared inode 736710638 imap claims a free inode 736710639 is in use, correcting imap and clearing inode cleared inode 736710639 imap claims a free inode 736710640 is in use, correcting imap and clearing inode cleared inode 736710640 imap claims a free inode 736710641 is in use, correcting imap and clearing inode cleared inode 736710641 imap claims a free inode 736710642 is in use, correcting imap and clearing inode cleared inode 736710642 imap claims a free inode 736710643 is in use, correcting imap and clearing inode cleared inode 736710643 imap claims a free inode 736710644 is in use, correcting imap and clearing inode cleared inode 736710644 - agno = 1 imap claims a free inode 2148296833 is in use, correcting imap and clearing inode cleared inode 2148296833 imap claims a free inode 2148296834 is in use, correcting imap and clearing inode cleared inode 2148296834 imap claims a free inode 2148296835 is in use, correcting imap and clearing inode cleared inode 2148296835 imap claims a free inode 2148296836 is in use, correcting imap and clearing inode cleared inode 2148296836 imap claims a free inode 2148296837 is in use, correcting imap and clearing inode cleared inode 2148296837 imap claims a free inode 2148296838 is in use, correcting imap and clearing inode cleared inode 2148296838 imap claims a free inode 2148296839 is in use, correcting imap and clearing inode cleared inode 2148296839 imap claims a free inode 2148296840 is in use, correcting imap and clearing inode cleared inode 2148296840 imap claims a free inode 2148296841 is in use, correcting imap and clearing inode cleared inode 2148296841 imap claims a free inode 2148296842 is in use, correcting imap and clearing inode cleared inode 2148296842 imap claims a free inode 2148296843 is in use, correcting imap and clearing inode cleared inode 2148296843 imap claims a free inode 2148296844 is in use, correcting imap and clearing inode cleared inode 2148296844 imap claims a free inode 2148296989 is in use, correcting imap and clearing inode cleared inode 2148296989 imap claims a free inode 2148358084 is in use, correcting imap and clearing inode cleared inode 2148358084 imap claims a free inode 2148358085 is in use, correcting imap and clearing inode cleared inode 2148358085 imap claims a free inode 2148358086 is in use, correcting imap and clearing inode cleared inode 2148358086 imap claims a free inode 2148358087 is in use, correcting imap and clearing inode cleared inode 2148358087 imap claims a free inode 2148358088 is in use, correcting imap and clearing inode cleared inode 2148358088 imap claims a free inode 2148358089 is in use, correcting imap and clearing inode cleared inode 2148358089 imap claims a free inode 2148358090 is in use, correcting imap and clearing inode cleared inode 2148358090 imap claims a free inode 2148358091 is in use, correcting imap and clearing inode cleared inode 2148358091 imap claims a free inode 2148358093 is in use, correcting imap and clearing inode cleared inode 2148358093 imap claims a free inode 2148358099 is in use, correcting imap and clearing inode cleared inode 2148358099 imap claims a free inode 2148358102 is in use, correcting imap and clearing inode cleared inode 2148358102 imap claims a free inode 2148358103 is in use, correcting imap and clearing inode cleared inode 2148358103 imap claims a free inode 2148358104 is in use, correcting imap and clearing inode cleared inode 2148358104 imap claims a free inode 2148358105 is in use, correcting imap and clearing inode cleared inode 2148358105 imap claims a free inode 2148358106 is in use, correcting imap and clearing inode cleared inode 2148358106 imap claims a free inode 2148358107 is in use, correcting imap and clearing inode cleared inode 2148358107 imap claims a free inode 2148358109 is in use, correcting imap and clearing inode cleared inode 2148358109 imap claims a free inode 2161571648 is in use, correcting imap and clearing inode cleared inode 2161571648 imap claims a free inode 2161571649 is in use, correcting imap and clearing inode cleared inode 2161571649 imap claims a free inode 2161571650 is in use, correcting imap and clearing inode cleared inode 2161571650 imap claims a free inode 2234810073 is in use, correcting imap and clearing inode cleared inode 2234810073 - agno = 2 imap claims a free inode 4300476805 is in use, correcting imap and clearing inode cleared inode 4300476805 imap claims a free inode 4300476806 is in use, correcting imap and clearing inode cleared inode 4300476806 imap claims a free inode 4300476807 is in use, correcting imap and clearing inode cleared inode 4300476807 imap claims a free inode 4300476808 is in use, correcting imap and clearing inode cleared inode 4300476808 imap claims a free inode 4300476809 is in use, correcting imap and clearing inode cleared inode 4300476809 imap claims a free inode 4300476810 is in use, correcting imap and clearing inode cleared inode 4300476810 imap claims a free inode 4382556855 is in use, correcting imap and clearing inode cleared inode 4382556855 imap claims a free inode 4382556856 is in use, correcting imap and clearing inode cleared inode 4382556856 imap claims a free inode 4382556857 is in use, correcting imap and clearing inode cleared inode 4382556857 imap claims a free inode 4382556858 is in use, correcting imap and clearing inode cleared inode 4382556858 imap claims a free inode 4382556859 is in use, correcting imap and clearing inode cleared inode 4382556859 imap claims a free inode 4382556860 is in use, correcting imap and clearing inode cleared inode 4382556860 imap claims a free inode 4382556861 is in use, correcting imap and clearing inode cleared inode 4382556861 - agno = 3 imap claims a free inode 6494313648 is in use, correcting imap and clearing inode cleared inode 6494313648 imap claims a free inode 6494313649 is in use, correcting imap and clearing inode cleared inode 6494313649 imap claims a free inode 6494338476 is in use, correcting imap and clearing inode cleared inode 6494338476 imap claims a free inode 6651213018 is in use, correcting imap and clearing inode cleared inode 6651213018 imap claims a free inode 6671684566 is in use, correcting imap and clearing inode cleared inode 6671684566 imap claims a free inode 6671684567 is in use, correcting imap and clearing inode cleared inode 6671684567 imap claims a free inode 6671684568 is in use, correcting imap and clearing inode cleared inode 6671684568 imap claims a free inode 6671684569 is in use, correcting imap and clearing inode cleared inode 6671684569 imap claims a free inode 6671684570 is in use, correcting imap and clearing inode cleared inode 6671684570 imap claims a free inode 6671684571 is in use, correcting imap and clearing inode cleared inode 6671684571 imap claims a free inode 6671684572 is in use, correcting imap and clearing inode cleared inode 6671684572 imap claims a free inode 6671684573 is in use, correcting imap and clearing inode cleared inode 6671684573 imap claims a free inode 6671684574 is in use, correcting imap and clearing inode cleared inode 6671684574 imap claims a free inode 6676233442 is in use, correcting imap and clearing inode cleared inode 6676233442 imap claims a free inode 6676233443 is in use, correcting imap and clearing inode cleared inode 6676233443 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 entry "S01" in shortform directory 2644158 references free inode 2148296833 junking entry "S01" in directory inode 2644158 entry "S03" in shortform directory 2644158 references free inode 4300476805 junking entry "S03" in directory inode 2644158 entry "S04" in shortform directory 2644158 references free inode 6494313648 junking entry "S04" in directory inode 2644158 corrected i8 count in directory 2644158, was 2, now 0 corrected directory 2644158 size, was 25, now 17 entry "6d6a0a5176c6831c628042dcd5ed636317c58d3c.torrent" at block 0 offset 576 in directory inode 2148298049 references free inode 2234810073 clearing inode number in entry at offset 576... entry "c40c1206329a630e9ceb2b7ca2b667fc0ae0a5a3.torrent" at block 0 offset 1528 in directory inode 2148298049 references free inode 2148358084 clearing inode number in entry at offset 1528... entry "4ce58a9f55f23867133a09a9aac1830ee805b144.torrent" at block 0 offset 1664 in directory inode 2148298049 references free inode 2148358085 clearing inode number in entry at offset 1664... entry "0a4f02260482d6d77a9eb32e26c1af046605baf9.torrent" at block 0 offset 1800 in directory inode 2148298049 references free inode 2148358086 clearing inode number in entry at offset 1800... entry "18505bc5116dfcfcab64780e6bb95ac21a110d3a.torrent" at block 0 offset 1936 in directory inode 2148298049 references free inode 2148358087 clearing inode number in entry at offset 1936... entry "5df5b5c235f48158039b72291ddedcae5b3676ce.torrent" at block 0 offset 2072 in directory inode 2148298049 references free inode 2148358088 clearing inode number in entry at offset 2072... entry "173afbc07a4e07e4839f6d8575dc9e957e57e117.torrent" at block 0 offset 2208 in directory inode 2148298049 references free inode 2148358089 clearing inode number in entry at offset 2208... entry "3c6f09670f4f5e130975bc252228e85a3284e436.torrent" at block 0 offset 2344 in directory inode 2148298049 references free inode 2148358090 clearing inode number in entry at offset 2344... entry "112955497e3b0e6f6fb5d0cba8337804134e577e.torrent" at block 0 offset 2480 in directory inode 2148298049 references free inode 2148358091 clearing inode number in entry at offset 2480... entry "0330918b8ca202ad19e5b0a10d5312db1635844f.torrent" at block 0 offset 2752 in directory inode 2148298049 references free inode 2148358093 clearing inode number in entry at offset 2752... entry "c630cf0ba8e9461c5c6ddc0f61bd13852d726550.torrent" at block 0 offset 2952 in directory inode 2148298049 references free inode 2148358109 clearing inode number in entry at offset 2952... entry "4029da56c180cc31b0d007598417f5b18c0ef53d.torrent" at block 0 offset 3488 in directory inode 2148298049 references free inode 2148358099 clearing inode number in entry at offset 3488... - agno = 3 entry "736710638" in shortform directory 3797983 references free inode 736710638 junking entry "736710638" in directory inode 3797983 entry "736710640" in shortform directory 3797983 references free inode 736710640 junking entry "736710640" in directory inode 3797983 entry "2148296989" in shortform directory 3797983 references free inode 2148296989 junking entry "2148296989" in directory inode 3797983 entry "4382556855" in shortform directory 3797983 references free inode 4382556855 junking entry "4382556855" in directory inode 3797983 entry "6671684566" in shortform directory 3797983 references free inode 6671684566 junking entry "6671684566" in directory inode 3797983 entry "6676233442" in shortform directory 3797983 references free inode 6676233442 junking entry "6676233442" in directory inode 3797983 corrected i8 count in directory 3797983, was 5, now 2 entry "Foster's Home For Imaginary Friends - Season 4" at block 0 offset 224 in directory inode 4300859500 references free inode 2148358102 clearing inode number in entry at offset 224... Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... fixing ftype mismatch (0/2) in directory/child inode 2644158/2644159 bad hash table for directory inode 2148298049 (no data entry): rebuilding rebuilding directory inode 2148298049 bad hash table for directory inode 4300859500 (no data entry): rebuilding rebuilding directory inode 4300859500 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 2161537149, moving to lost+found disconnected inode 2161537150, moving to lost+found disconnected inode 2161537151, moving to lost+found disconnected inode 6651212882, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 2644158 nlinks from 6 to 3 resetting inode 3797983 nlinks from 14 to 8 resetting inode 4300859500 nlinks from 8 to 7 Maximum metadata LSN (4:420) is ahead of log (4:380). Format log to cycle 7. done
October 10, 20241 yr Author Alright I got that done, added a parity and started the array. Everything seems to be okay. it is currently running parity check. Now I need to get another drive to expand my array. postserver-diagnostics-20241010-0538.zip
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.