Herdie27

So I found my Unraid giving me a warning that the USB is corrupted. (At the time of this writing I haven't seen the warning in a while, I don't know if this means anything but I doubt anything fixed itself because I still have other problems. When I click on the USB on the main page I see a long list of this these errors... Jun 8 09:17:18 Tower kernel: I/O error, dev sdh, sector 36896 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2 Jun 8 09:17:18 Tower kernel: Buffer I/O error on dev sdh1, logical block 34848, lost async page write Jun 9 20:43:18 Tower kernel: FAT-fs (sdh1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 6955717b) Jun 9 20:47:48 Tower kernel: FAT-fs (sdh1): error, fat_get_cluster: invalid start cluster (i_pos 513378305, start 16ce9dfe) I've attached my diagnostics to this post. As per my research I've backed up my USB, apparently it's still readable. Here is my course of action right now based on the research I've gathered. Check the current corrupted USB for with windows CheckDisk and see if it can be repaired, if yes, boot up Unraid and go from there. If no, go to step 2. Make another install USB of unraid and do a custom install from my backed up USB config file. ( I was lucky that the corrupted USB is still readable) I need to figure out how to transfer my license to the new USB. Boot/install? From new USB. Question: Do I even need to do this if I have a cache drive I can run Unraid on? My research tells me I can use my cache drive as the boot drive as well, so do I even need to do anything with a new USB? These are the lots of other issues that I have but I'm guessing that most of them are caused by my boot USB being corrupted. I know the UDMA crc errors are due to power connectors so I'm reseating them after I post this. They've also only gone up once and they haven't got any higher. Custom Name "Warlock" Disappeared and now it's named "Tower" API is offline and can't get it working again 8 Plugin File Install Errors gpustat.plg dynamix.file.manager.plg fix.common.problems.plg folder.view3.plg nvidia-driver.plg tailscale.plg unbalanced.plg dynamix.unraid.net.plg Parity 1: 2 UDMA CRC errors Parity 2: 1 UDMA CRC errors Disk 2: 411 UDMA CRC errors Disk 4: 1 UDMA CRC errors Disk 5: 3 UDMA CRC errors tower-diagnostics-20260609-2348.zip

Okay, 1) I have the other extended SMART report for my data drive attached. I'd appreciate a quick check just for my own sanity. 2) I replaced the two quad sata splitters with y-splitters. Two attached to sata, the other two to molex Assuming I've read enough about it I can enable the parity and the data drive at the same time without issue. 1) Stop the array 2) Un-assign drives 3) Start in maintenance mode 4) Stop the array again 5) Reassign drives to original slots 6) Start the array and unraid will rebuild both drives (I do this little summary for archival purposes) data drive SMART report.zip

So here's the crazy thing I didn't mention, at least for me. The cable that came with the unit splits 3 ways. 1) 3 molex connectors. 2) 3 Sata connections. 3) The same 10 pin that powers 8 Small Form Factor drive bays, I don't use these.

Yeah, I always have to remind myself of this because it works all the time and I don't open it up often. But without getting too wordy about my setup, I have two 15 Pin SATA to 4 SATA Power Splitters https://www.amazon.ca/dp/B012BPLW08?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_2 to power 7 total drives. One splitter per row of drives in my HP Proliant 350p Gen 8 and the two drivers that have errors on them are right next to each other. I also have mini sas cables for my drives as well. https://www.amazon.ca/dp/B07B9SBSVW?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_1 I've taken a look at things and nothing is loose or mis-connected, etc. Come to think of it, even though my server is connected to a UPS there's been some strange things going on with my power at my place. I have an Led light connected to the same outlet as my UPS and it the light flickers and the UPS will sometimes kick on and then off within a couple seconds. So there is some where power things going on. In this case, could my problem be solved my rebuilding my data drive?

So all of a sudden I've got read errors on one parity drive and one data drive. In total, I have 2 parity drives and 5 data drives. Being an arm chair sys admin the only thing I know how to do is change out the drives. Luckily they're both under warranty still. And correct me if I'm wrong, I can change out the parity drive and the data at the same time, yes? But before we get to that I've posted my extended SMART self test for my parity drive and diagnostics in this post. parity drive SMART test.zip warlock-diagnostics-20260218-1330.zip

Since I have 2 parity drives my data should be just fine and re-enabling both drives at the same time should be okay? Or should I do one at the time?

So how can I get my Parity disk and Data Disk back up? Everything I've read says the data disk needs to rebuild on itself and I can't find anything on getting my parity disk re-enabled. Additionally, I decided to do another SMART test on each disk and it's been a day and a half and they're still not done testing. They both say 20% complete. I also attached the current diagnostics. warlock-diagnostics-20250823-1555.zip

No power splitters. I have two power supplies each with what I would say are pretty old power cables hooked up to a UPS. Do you think the power cables themselves could be the problem? The errors aren't listened anymore and the drives are still disabled

warlock-diagnostics-20250821-0102.zip warlock-diagnostics-20250821-0102.zip

It's been a while. I finally got a new cable in. I've replace the cable for the parity drive because it started with the parity drive and then there were errors on my new 12TB data drive, so I'm hoping the parity drive errors had had the errors which then caused errors in my data drive. But anyway, I've replace the cables for my parity drive, now what? I errors are still there when I started the array, how can I clear them and "restart" so to speak.

So recently I had some issues with a data drive that I had some questions about here... But I recently saw there were read errors on one of my parity drive, I have 2 parity drives, about 2300 errors. Since I didn't have time to address it over the weekend, outside of a extended SMART test, attached in this post, I'm here now to try and fix things. All the sources I've read say to simply replace the parity drive. As if there are any errors on the drive, it's in decline and isn't worth keeping. This parity drive is also one of my newest ones and it also passed the extended SMART test. Everything also stopped a read-check at 2.7%, it's now paused. I'm not sure what the best course of action is, other than replacing drives. warlock-diagnostics-20250811-1711.zip parity disk warlock-smart-20250811-1709.zip data drive warlock-smart-20250811-1742.zip

No errors during rebuild. Checked the log as well and didn't see anything wrong. Everything looks to be back to normal.

😬 aaah okay. If any errors I'll let you know, thanks so much for your help!

Yes, after I pressed the FIX button it did it's thing and I decided to check it again. This check came up with no problems so I started a rebuild. Currently it's 50% rebuilt and doesn't have the "Unmountable" warning next to the disk.

Every time I think I have a handle on things I seem to make a mistake. So I wanted to make sure. I pressed the FIX button and now the drive is rebuilding.

So after some reading, I did a check of the drive via the GUI and I got this output... I've yet to click the "fix" button in the GUI under "Check Filesystem Status" 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 ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... agf_freeblks 2271491, counted 2271401 in ag 4 agf_freeblks 1876851, counted 1876759 in ag 6 block (2,80781038-80781199) multiply claimed by cnt space tree, state - 2 agf_freeblks 4125404, counted 4125712 in ag 2 agf_freeblks 519469, counted 519516 in ag 7 agf_freeblks 1871672, counted 1871668 in ag 5 agf_freeblks 2316713, counted 2316761 in ag 1 agf_freeblks 13222371, counted 13222420 in ag 3 sb_fdblocks 20450170, counted 34075088 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 data fork in ino 3129813387 claims free block 393742246 data fork in ino 3263282003 claims free block 407656320 - agno = 2 data fork in ino 4321751974 claims free block 540216784 data fork in ino 4321751976 claims free block 540217030 data fork in ino 4321751979 claims free block 540216224 data fork in ino 4321751981 claims free block 540211746 data fork in ino 4321751983 claims free block 618228804 data fork in ino 4321751988 claims free block 540216932 data fork in ino 5188886533 claims free block 648680731 - agno = 3 data fork in ino 6451319329 claims free block 822665964 data fork in ino 6451319331 claims free block 821131745 data fork in ino 6451319333 claims free block 820201564 data fork in ino 6451319335 claims free block 824908196 - agno = 4 data fork in ino 9389366867 claims free block 1206826617 data fork in ino 9389366869 claims free block 1168505373 data fork in ino 9389366869 claims free block 1168505515 data fork in ino 9389366876 claims free block 1168510252 - agno = 5 - agno = 6 data fork in ino 13180588852 claims free block 1619548451 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (2,1802628-1802669) only seen by one free space btree free space (2,3345611-3345842) only seen by one free space btree free space (2,80781200-80781324) only seen by one free space btree free space (2,111656941-111657049) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 0 - agno = 4 - agno = 1 - agno = 3 - agno = 2 - agno = 6 - agno = 5 - agno = 7 setting reflink flag on inode 6451319323 setting reflink flag on inode 6451319337 setting reflink flag on inode 15101598200 Missing reference count record for (3/16405905) len 115 count 2 Missing reference count record for (4/94768151) len 277 count 2 Missing reference count record for (7/39302994) len 137 count 2 setting reflink flag on inode 15214246528 setting reflink flag on inode 15214246552 setting reflink flag on inode 15214246564 setting reflink flag on inode 9359712613 setting reflink flag on inode 9359712618 setting reflink flag on inode 9389366871 setting reflink flag on inode 9389366874 setting reflink flag on inode 9389366876 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.

Okay I'll give context to all this because this is really annoying me at this point and I really want to resolve this and get back to working on other things. This is what I get for wanting a storage solution for my photos and videos. (I'm a photographer/videographer). Anyway, I had a 8TB drive that had an error on it that caused me to rebuild the drive. It worked for about 2 weeks and then it said it was "Unmountable: wrong or no file system". So I said screw it, instead of trying to fix it, I'll replace the drive with a 12TB drive. So I put this new 12TB in and rebuilt the drive. I didn't preclear or format the drive before rebuilding and it still says it's "Unmountable: wrong or no file system". So I know from the main page that I can format the drive, my issue is the warning that comes up before I format it. There's one line that says "discarding all data currently on the disks and update parity to reflect this." So will parity be updated and remove all the data that was on the 8TB drive? (it was almost full) Am I understanding this correct? If so, what is the next course of action?warlock-diagnostics-20250726-0050.zipwarlock-smart-20250726-0048.zip

How do I know if the physical connection is back to normal? I restarted everything and the drive is still disabled. Will the drive show as reenabled when the connection is good? If that is the case should I get new cables? Or, could I stop the array, unassign the drive, start the array in maintenance mode, stop the array again, reassign the drive and let it rebuild? Or could I do a New Config?

Bah! I knew I forgot something. Updated.

The title says it all. I suddenly got a disabled drive on my Unraid, version 7.1.4. I have 2 parity drives and 5 storage drives. The drive that's disabled is 8TB and there is 83.8GB free on it. I've attached the SMART report for the drive. One thing I've tried is... 1. Stopping the array Unassigned the drive and started the array in maintenance mode Stopped the array again and reassigned the drive Started the array and the drive started to rebuild Then it paused at 6.7% with a read error and I'm kinda back where I started. After this I also made sure all my physical connections were good. I also did a extended SMART test, which it passed. I don't know what to do from here. I usually try to read as much as I can before going to the forums, but I also like to know what I'm doing is correct by confirming with other people. But like I said I'm back where I started with a drive that's disabled and I'm not sure what to do other than replacing the drive. warlock-smart-20250704-2149.zip warlock-diagnostics-20250717-0056.zip

Okay, let me start by saying I'm at my wits end with this. Nextcloud has literally never worked. This is an extra project for me so I've had this on the bac-burner for a while, probably over a year and I've spent about 8 hours trying to figure things out. Put simply, I've never been able to access the web ui since installing nextcloud (linus server repository)...a while ago. Clicking the "webui" button in unraid or going directly to the ip address itself, I get a "site cannot be reached" ERR_CONNECTION_REFUSED. I wanted nextcloud to be a replacement for google drive so I wanted to set it up with a custom domain and things so I'm using cloudflare, Nginx Proxy Manager, port forwarding on my router and all that jazz. I can access jellyfin and 2 other docker apps through the domain name but never nextcloud, even though I'm doing the exact same thing with all the other docker apps like jellyfin. By typing in the domain I've setup with nextcloud I get error code 502, bad gateway. This last stint of trying to fix it myself I looked at the logs for nextcloud and it says the following. "Can't start Nextcloud because the version of the data (27.1.3.2) is more than one major version behind the docker image version (30.0.4.1) and upgrading more than one major version is not supported. Please run an image tagged for the major version 28 first." So if nextcloud can't start I need to fix my data version problem, yes? What I've been able to come up with is I have to downgrade from version 30 to 27 in order to upgrade the data version and nextcloud can actually start working. In trying to do this I've needed to use the terminal from UNRAID or the console by clicking on nextcloud. (Hope that makes sense) An extra few questions because of all the research I've done. Is it better to use the UNRAID terminal? Or when dealing with a docker app, use the docker apps console? Or when should I use either? I hope all this makes sense because I'm learning A LOT every time I dive into this stuff.

Okay, kinda new to unraid but I've been doing a lot of reading, which is why my data isn't at risk. I just want to know if this hard drive is good to use or not. I'll give you the highlights of this saga. First, it started with UDMA CRC errors on Disk 2. 411 if I remember correctly. This drive was then emulated and I needed to fix things. Secondly, I replaced the drive with a new drive, rebuilt the data, but because I'm borrowing this drive I used the Unbalanced plugin to transfer the newly rebuilt data to the rest of the array. So non of my data is at stake. Thirdly, I've put the old disk 2 back in hoping I can just format it, clear it, or something and all will be good again. From what I can tell the drive is still running fine, but that's also coming from my more basic knowledge. It still comes up as having 411 UDMA CRC errors. I started the array and Disk 2 is still being emulated. So I have a few questions, could clear the drive to fix it, if so how? Should I not take the chance with this drive and get a new one? Is there anything I can do to save the drive? Using Unraid 6.12.13 And I've attached a SMART extended self test and attached it to this post. Let me know if I should post any other info for ya'll. ST4000VN008-2DR166_ZGY71P97-20241221-1338.txt

Thanks very much! I've done more reading about the new config tool and everything went through just fine. Everything looks like it's working perfectly.

Updated my post with the diagnostics

So I recently upgraded my server from an old dell to a newer HP server and transferred all my drives from one to the other. I have 7 total drives plus a cache drive. After working through some other problems (I'll list them for reference) and solving them via googling there's one thing I can't figure out/ wanted to make sure of because I'm pretty sure of what to do. Problems fixed before this point: 1. Had to swap USB drives my new server didn't like my kingston USB and wouldn't boot. Got Unraid on a new USB and it's working and booting fine 2. Couldn't connect to the internet with on board ethernet ports and used the 2.5 Gig Nic I installed to connect to the internet so I could accomplish problem 3 (During this time I also upgraded Unraid to version 6.12.11). 3. Had to replace the key for my UNRAID OS as the new license had to be attached to the new GUID of the new USB After booting up the new server all of the drives are labeled as "wrong". This is stopping me from spinning up the drives and starting the array. Even though every single drive has the exact same name/ serial number attached to it and they are reassigned in the exact same way. From what I can gather I have to "new config" the whole thing. From what I can gather this won't do anything to the data on my drives. FYI, I'm a photographer/ videographer and the family data hoarder so the data drives need to stay intact, this is also why I have 2 parity drives. If anyone can detail out what I should do/ point me in the right direction it'd be much appreciated. Please let me know if you have any questions for me. warlock-diagnostics-20240802-1528.zip