deltaexray

Qucik question? Is it normal that the speed the parity check runs drops over time? Like by a good amount?

Yeah, after I posted it, I thought so too that it was already included. I wanna find out what caused it and I'm going to do a parity check, without writing corrections to the array. We'll see what's happening afterwards I guess

That's the SMART Report of the drive that has these issues. May take a look at this, maybe this will say something server-smart-20210820-2225.zip

It did finish, without errors. Everything was good Well, I'd like to hope that this was only because of a connection issue. But on the other hand, that HBA that is in that server works like champ. And, if it really is an issue like it, why is it only one drive when all of them are on the same channel on the HBA? I'm just curious because of the word "sector" in the error message, which could be the drive, If I'm not wrong? Yeah, I still need to set them up but I'm always confused how to set them up. I do need to do a ton of other stuff, like security and stuff

I forgot that this is/was the best way to get answers, ups. There you go, server-diagnostics-20210820-2052.zip EDIT: The drive that spitted out theses errors has no self reported SMART Errors, even after the extended self test that I had running thru the day. Doesn't surprise me tho

So, last night I played a couple movies thru plex until this error message popped up: Aug 19 21:47:21 Server kernel: blk_update_request: I/O error, dev sdc, sector 173824 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Is this a, more or less, the start of a faliling disk or what could be happening here?

So, long update: Drives work with the HBA and the new cable, even better then before which makes sense given that internally it was Sata 3G, the HBA is Sata 6G. But there's another "thing", that's why I asked if anyone has had issues with MTU and Network Transfers, given that the Systems still crashes. Big time. When I built the systems, I set the MTU value in the Network Settings Tab to 9000, as I usually do based on my knowledge, higher is better and least on one hand. So, after I put in the HBA rebooted the system and started the 200GB again. After 65%, it crashed. But this time the Networking Timeout Error/Networking Address not reachable anymore, gave me some, kind of, thoughts of why it is like this. So to put a long story very short: The MTU value on the Server side, is the reason it keeps crashing. If I set the value to the, standard, 1500, it works with everything I copy onto it. If I set it to 9000 or 9198, the letter is the maximum of Unraid, it crashes at multiple points during the transfer. So know coms the question part: Is the MTU Value singly responsible for the constant crashes or, is it, still a drive issue given that it only crashes when the MTU is set to 9000, in terms of 4K sectors on the Ironwolfs? And yes, I could just set the value to 1500 and forget about it but I want to find out, what is the real issue. Not just a 5 day fix to something that keeps popping up all the time. At this point, I'm just really out of ideas so yeah If you have any ideas, I'd be really happy to hear them.

Quick question: As anyone ever encountered any issues or problems with the MTU Value in the Unraid Network Settings, specially with the on board Nic/Nic's and any issues with copying over the network/network copy's timing out/won't finish?

My guess is that the cable was a reverse one, not a forward one. The card shows up fine, but the cable connected no drives showed up. So ordered a new cable, send back the one I ordered and we will see. Buying a *new* mobo doesn't really make sense, given that the socket is that old and only eBay would be possible. and before I pay 80-90 for that mobo, I'd rather pay that money for an HBA and have more ports anyway

Yep, thinking that the one I got is a reverse one, even thought the description says not really specific. Guess I´ll have to buy another one.

Quick update: HBA came today, put it in and it shows up. The Drives do not show up. Seriously, I´m out of ideas. Cable is new, should work. Do not have one on hand. Could be the cable, I don´t think and hope so. No clue

I get these crashes when, and I've posted this before here, I copy large amounts of data through the onboard Sata Controller. It will crash then, presumably of the fact that 1 drive will link out, given that when I boot the system only 2 of 3 show up. and Yes, all of the drives are healthy and good. HBA should arrive today, I'm gonna keep you posted on this one

First of all: Sorry for the late reply, I haven't even noticed that this thread now has a second page so yeah, my mistake here. And secondly: Zip. File attached, my Mac was opening those files directly so I haven't noticed it. So yeah, sorry for replying so late :´) server-diagnostics-20210105-1959.zip

@trurl Well, I´m lacking an explanation myself here, given that in every thread on this forum it´s always a ZIP file but I downloaded it on a Mac OS X machine so maybe that´s why it was no zip.

I know. And in this case, there are a lot of things not going as planned.. CPU is Ivy Bridge, board must be 8 Years old by now. So yeah, it's funny but on the other hand should work in one way or the other I will, I have to if it's not working

So update: I have let the extended SMART Test run over night on all drives, with no error reporting on all of them. So the drives are out of play at this time. Then, I looked at the BIOS and the SATA Configuration. Noticed that 2 drives show up but the third, Parity, not. So I swapped one of the drives that show up with the one that doesn't and? It showed up, the other that usually shows up doesn't. Did the same with the third, the same happened. So I figured it's not a drives issues, it's a Motherboard Sata Controller issue. When I connect 3 1TB drives, all of them show up. 3 8TB drives, only 2 show up. 3 8TB Drives and an old 120GB SSD, only 2 8TB show up. It's the board, nothing else makes sense. Everything else is checked. So what I did now? Bought a "Broadcom 9207-8i SAS2308 6G SATA SAS HBA PCIe x8 3.0 LSI RAID IT Dell 0VGXKD" on Ebay, should arrive on Wednesday and the Cables are from a good retail seller, brand new. We will see how that goes and if it works, if not I'm honestly completely out of ideas. If it does, I guess that's why it's called Troubleshooting. I just hope that the HBA won't interfere with the sleep mode setting or with the drive spin down / sleep mode and the spin up respectively because that would cause a lot of other issues. Well, I just hope this works sigh

1. I guess that's why it's called troubleshooting. I am guessing I am gonna pre clear that drive, If I can't use the server I might as well do a pre clear with that drive. 2. I know that feeling very very well. All of my networking, server, Unraid and so on knowledge is from learning by doing and YouTube/forums. 3. I might as well gonna put it in my main rig and let it start with the system to figure it out. Swapped cables like 4 times now, they all work. PSU works. it can only be a drive or Sata controller issue. I can do that but I can't write to the parity disk, bc of format issues, so I can't test it. On the other hand, if the other two work without the parity drive/do not spit out error while copying, it's clear what it is I've tested all of the ports on the board, they all work. Only the parity drive is the one that doesn't show up while booting, regardless of the port or cable, at least with the first boot, after a restart it's there. I will look at it, cannot hurt to have one on hand in order to do more/better stuff with it. Usually the onboard ones are enough but in this case? Hell I do not know.

I am running a full extended Smart Test over night on all the drive, see if that will help or give anything new. Thought so myself, I can change it but they are only 3 drives each with 9 watts of power consumption on a Corsair RM650M on one Sata power connector/rail (the cable where 4 connections are on one rail), with no issues at all in the past but I can try it out tomorrow. If anyone has a go to HBA/Raidcard in IT Mode recommendation, I'll get one. besides I thought about this before building this machine to avoid the internal controller entirely but did not want to spend another 100€, at least, extra on it. It definitely makes a sound, I just do not know if it's a bad one or not. In the other PC, it shows up with the same noise. I got a 6TB Ironwolf in my main rig that also makes noises, which is normal at 7200rpm, and works just fine. As said, I'm running the Smart extended test within Unraid over Night. I tried the Seagate tool before today, it's actually just the same as what Unraid does so I skipped it. The funny thing is just, it all started with locking up while making a data transfer and now we are here talking about if the drives dead/damaged or the board is the issue. Try me but if the drive is dead, would it not cause issues all the time? And just to clarify, I am tech guy for over 10 years now so I kinda know a lot but still I'm new to Unraid:D

@brent3000 I thought so and it makes sense. I have the feeling the parity may causes all of this but as mentioned before, I do not know if it's the Mobo or the Drive, given that the drive shows up in another system. I may be doing a complete array rebuild tomorrow. But it's always the same drive that is involved in every crash cause it's the parity drive. I'm just not sure if it's the drive or the mobo, cause it's shows up on a different one but not on the one in the server on the first boot, only on the second, yet it's the parity and therefore always involved in a read/write operation. So I am kinda thinking that it's the drive not the mobo. But Idk. I'm just confused.

So based on how I progress with this issue, I'm guessing this is going to be the last post regarding the topic because I start to turn insane. Turns out, on my main PC all of the drives show up and can be formatted in Windows, regardless of what I do. On the Intel System, or to be precise the P8H77-V, 2 Drives are showing up, the third only when I do a restart. So drives aren't the issue, at least at this point, I boot into Unraid and start the array, start copying files and it locks up and random points and at the same points with the same transfers, u can recreate everything. I'm at this point, completely out of ideas with what could work or not except buying a complete new Mobo, which with this CPU and Socket is "new" impossible at this date and time. I have the feeling that one drive, I don't know because of the drive or the SATA Controller of the Mobo, drops out while being in operation of Unraid, specially given that the drive that doesn't naturally shows up in the BIOS is the Parity drive of the Array. So, yeah. A days worth of troubleshooting and here I am. Maybe someone else has an Idea.

I am stupid: The HDD that spits out errors, is the parity disk. So, it doesn't matter to what drive I copy, if the parity is damaged I will always get a crash right?

Quick update: System crashes both times while transferring 200GB of Data, doesn't matter if the share is only on Disk 2 oder Disk 3. Disk 2 is the one which made noises and doesn't show up in the bios after a restart but now it also crashes while only copying onto Disk 3? What the hell? On the Windows PC it says: Networked timeout, cannot copy File to Network disk, which makes sense due to the fact that Unraid locks up. I´m just a little confused now

I do think so too. That's the plan, moving the existing data from the drive to the other, given that the other one is healthy and then just add the new one back in. Not going for speed, system doesn't even has a cache drive, just 32GB RAM and a bunch of HDDs, only running Gigabit Networking so no need for cache, works just fine if it works;D We will see, I'm going to find out if the drive is dead first now

Germany, I can still return the drive and get a new one, it's only 2 weeks ago when I bought it. Doubt that a FW will help, every restart of the system makes the drive not showing up and also has a sound to it, like you would crush metal on metal. But I can try that.

That's actually a really good idea, will try that now! I have, sort of, until I had to roll out the machine because of storage limitations, it was my mistake not to do a complete pre-clear there Tested 4 cables, drive doesn't shop up regularly with all of them, BIOS runs in AHCI, RAID doesn't even work on this mobo;D