firrae

Members
  • Posts

    36
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

firrae's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Cool, thanks. Will do tomorrow after work. With its ominous wording I figured I'd make sure before doing it ha. Sometimes it actually means something.
  2. OK, what I care about on it is being backed up again. So it's good to die if it needs to.
  3. Hi there, I'm in a weird issue. the UnRAID disk check says my drive has filesystem corruption, but I find it interesting that the system is fine until I've written 1 or 2 GBs of data to it. At that point it becomes I/O errors galore. So clearly it's messed up. When I went through the wiki article here on repairing drives with issues: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui. It returns the following through both the UI and through a SSH session: xfs_repair -v /dev/md6 Phase 1 - find and verify superblock... - block cache size set to 1507224 entries Phase 2 - using internal log - zero log... zero_log: head block 2248359 tail block 2247490 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. So now I'm not sure what that means for me. I don't think there's anything awfully important on the drive and am about to boot it up as normal to double check, but like I said I can read off it perfectly fine, even after writes start to fail, so if there is anything important on it I can presumably recover it. Now though is the crux of my question, what is the best method? I have a spare 4TB drive sitting here if replacing it 1:1 will work and letting the parity re-build (there's maybe 20GB on the drive so far as I can remember) so not much, otherwise do I drop that `-L` flag on it and hope it fixes things (from the wiki the tool seems unreliable for positive outcomes at best)? I'm going to check what's on the drive now aby spinning it back up and hopefully someone can help me go from there. If you need anything else to help out let me know. tower-smart-20201119-2112.zip tower-diagnostics-20201119-2112.zip
  4. While this was not the fix, it did help me generate a useful error in the logs. Seems like something went weird on one of my disks causing I/O locks in specific containers and even some whole shares (the downloads folder being one of them). After a reboot and some clean-up this seems to be working again, though I will need to keep an eye on the drive which is normal procedure I guess (it's one of my oldest). Though thanks for trying and showing me that Chrome add-on, I'm totally using it!
  5. Hi there, maybe someone could help me out. I posted the issue on the GitHub issue tracker here because that's my default place to put issues as a developer lol: https://github.com/binhex/arch-delugevpn/issues/224. Synopsis is that the container is running, VPN is seemingly connected fine, web UI shows up, but when I try to add a torrent by Torrent file (.torrent) I get "Failed to upload torrent" and there doesn't seem to be a log in sight about it. Since the UI works otherwise I can only assume the setting are correct. I've tried turning off Privoxy AND VPN all together and still get the same issue. Magnet links work and the stuff begins to download fine, but adding .torrent files is a complete no go, and as I only use torrents from a private tracker, they don't offer magnets so this is a deal breaker for me. At this point if I can't figure it out, I'm back on the hunt for a VPN protected torrent container after spending too much time on this one already sadly.
  6. Well, I can't thank you enough @johnnie.black! After updating the firmware I see 0 read errors and the CRC errors have completely stopped increasing on all drives. Thanks a bunch for pointing this out, I would NEVER have thought of this being an issue.
  7. OK, will try that. Thanks for pointing me in a direction @johnnie.black!
  8. What would be the path forward do you think then? I'm not sure what I should do. I have multiple disks reporting read errors, but none show issues other than the CRC errors in SMART. Should I stop the rebuild, flash the firmware, and then... what? Rebuild if a parity check goes well?
  9. Interesting. Otherwise, if you don't me asking, but does the system look fine at a cursory glance? I do still have UNRAID reporting high read errors as well. Other than the glaring "its rebuilding a drive" thing of course.
  10. @johnnie.black is that a newer issue or has it been that way since before v6? I only got into UNRAID as v6 was launching and don't remember there being an issue until recently?
  11. Quick update. After I finished writing this I noticed that my SATA cable based drives were also getting these errors, but not all of them. The Parity drive is reporting 0 over its entire life, but the drive nearest it is showing an increasing, but slower than other drive on the SAS to SATA breakouts, number of CRC errors. This maybe leads to a combination of the cables and the cages? I really don't know at this point.
  12. Hi there, After digging around on Google and the forums I believe the issues with my array come down to the issue that I am getting UDMA CRC errors on a number of my drives, but honestly I'm not sure where to begin looking at the cause. In my eyes, and from reading, I believe it could be one or a combination of 3 things: My SAS to SATA cables (maybe they are cross-talking and the likely candidate?) - I've tried 2 different brands but still get the issue, though both brands the cables looked the same, just slightly different colours. - https://www.amazon.ca/gp/product/B0736J45V2/ My drive cages: I have a Rosewill RSV-L4412 which came with 3 drive cages (can't remember the part number for them) - https://www.rosewill.com/product/rosewill-rsv-l4412-4u-rackmount-server-case-or-chassis-12-sata-sas-hot-swap-drives-5-cooling-fans-included/ My SAS controller which is a Fujitsu (?) card flashed to be an LSI 9211-8i in "IT" mode At this point I believe the cables but I'd be interested in hearing what others think. 8 of my disks use these breakout cables as the way they connect, the other 4 go directly to the motherboard SATA ports. What I find interesting is it seems like the drives on these breakout cables have the issue much worse, though this is only so far a short term observation since I read about this, and the cage that's wired directly currently only has 3 drives in it, the rest are fully loaded with 4. I'm curious if people think I'd be better served with which of the potential options to try and solve this: Get different breakout cables. Get new drive cages. change out the controller. In any case I'd be interested in seeing the recommendations people have on this. This all comes from my seeing what I think are VERY high read error counts as I'm rebuilding my array after changing out a drive. Attached is my diagnostics file from the server. Its in the middle of building that drive as I mentioned, so whatever decision I make I'm a couple of days away from actually implementing at least assuming I can eve get the parts to do it at this point. I'm interested to see what people think. Thanks! tower-diagnostics-20200318-1415.zip
  13. You may have found it. I thought I had updated it, and while I need to go into the BIOS to be sure this is one of the update features on the second to last update they gave: I have VT enabled. I will try these BIOS updates if the server crashes otherwise I'll try them tomorrow night by gracefully shutting it down.
  14. 1) It seems the BIOS is fully updated, but I'll check again. 2) brand new PSU, replaced the original PSU. Tested the PSU on my main PC and it ran it fine for 3 days. 3) All the RAM is identical and was purchased at the same time. 4) RAM meets the mobo's requirements and is within their spec. 5) This is the one I can't decide if it is the problem. I have 4 fans in the case, one over the HDDs that's an intake, 1 more intake on the side, and 2 exhaust (back and top). I've had this issue happen with the fans in place and the case closed and with the side fan removed and the case fully open. 6) I cleaned pretty well everything before I put it in there. I moved the old PC into a new case and took that time to basically clean everything via compressed air before putting it back in. I'll follow up with the BIOS though and for heat, I figured there'd be some sort of warning or error log somewhere, but I can't find anything that indicates that.
  15. I have a monitor hooked up to it and was looking at it once when it happened, there was no shutdown procedure so it was a hard power off, the screen just went black and then the BIOS boot screen, that's where my thought of it being the PSU came from originally.