voldak

Thanks @JorgeB! I tried another cable swap, and it came to the same result. Kind of wild that 3/4 of the new drives did this same thing.

I recently bought some new larger drives to upgrade my array. I've precleared all of the drives successfully. The first drive was successfully configured as the parity drive without issues. However, I've attempted to replace other drives (3 total times) and the drive disappears when it's selected. I've tried to replace a few different drives and it's the same issue every time. I was able to grab some diagnostics before I shutdown the machine and put the original drives back in. Does anyone have any pointers/suggestions? tower-diagnostics-20221218-2041.zip

Thanks for the comment. I’ve been away on work, but I’m back now for a bit. I performed a memtest and no errors were detected. As for the other stuff, I had no reason to be running an older version of UD so I updated it. I made the docker to be ridiculously large in the past. I do need to trim it down now that I have other play systems for docker in the network.

Hello all, I've recently started to get some errors on parity checks. This started last month, with 11 errors, and my most recent check just ended today with 8 errors. I've got the diagnostics attached to this post. I'm not sure what to look for since I haven't had this issue before. Any help would be greatly appreciated. tower-diagnostics-20211003-1329.zip

Hello everyone, I recently updated to v. 6.8.3. A few weeks after upgrading I had a disk become disabled. I figured since the disk was older it was a problem with the disk, so I ordered a new drive. I hooked the drive up today and went to rebuild. I initially had problems with the rebuild since it had been a while since I had performed one. I did go through the updated instructions on the FAQ and it seems to be in process now. I did start to receive 'UDMA CRC error count' errors on Disk 2 of my configuration. I had acknowledged the errors previously after an upgrade because they could have been historical errors, but the error count goes up. Is there anything else to look at to see if the drive is failing or if it is a deeper issue? I have attached the diagnostics. Any help is greatly appreciated. At this point, my biggest fear is losing data. tower-diagnostics-20201108-2233.zip

I'm looking into my first rackmount build. I have an old model i7 (I7-2600), RAM, and 7 HDDs covered. I'm just looking for a case, mobo (with video) and PSU. I'm currently running an AMD x 3 945 and it's working fine for my needs (mostly file server with small Plex usage). I don't have a set budget, but i'm looking to keep it cheap. I'm in the US. Does anyone have any recommendations?

Guys/Gals, I've been running a pretty low-key setup for a while and things have been well. I've bought another server to start setting up my own lab at the house. I've almost got the wife conned into a rack for the house, so i'm needing to get my ducks in a row to see what I need to get my tower converted to a rackmount server. I've never looked into doing this before, so any advice would be helpful. I wouldn't mind slight upgrades, but would prefer to keep spending at a minimum for the transfer. Thanks! Motherboard: Biostar A760G M2+ - http://www.biostar-usa.com/app/en-us/mb/introduction.php?S_ID=394#spec RAM: Kingston 10GB 800Mhz CPU: AMD Phenom II X4 945 CPU - https://www.newegg.com/Product/Product.aspx?Item=N82E16819103675 PSU: Corsair TX650W - http://www.newegg.com/Product/Product.aspx?Item=N82E16817139005 Drives - 7 Various drives (6x3.5", 1x2.5" cache drive). I have these 7 drives in 2 Icy Dock bays.

I swapped the drive to another slot (connected to my PCI-Express Add-on card) and the drive was mountable and looks functional. I'm going to keep it here to check it over the next few days. It seems that I may be having issues with only the slots on the motherboard, since the issue follows across two IcyDocks and only happens with motherboard ports. I may look at replacement to try. I'll keep this open and post updates just in case anyone else has similar issues.

Ok. So, I just booted the server back up with a brand new SSD to test out the Cache drive slot (this slot is plugged in straight to my mother board). I assigned the drive as cache, then I tried to format it. It didn't format. After checking the syslog, the following errors where in the syslog. Jan 17 11:16:22 Tower kernel: blk_update_request: I/O error, dev sdd, sector 0 Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 Jan 17 11:16:22 Tower kernel: blk_update_request: I/O error, dev sdd, sector 0 Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 0, async page read Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 CDB: opcode=0x28 28 00 00 00 00 08 00 00 08 00 Jan 17 11:16:22 Tower kernel: blk_update_request: I/O error, dev sdd, sector 8 Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 1, async page read Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 17 11:16:22 Tower kernel: sd 7:0:1:0: [sdd] tag#0 CDB: opcode=0x28 28 00 1b f2 44 a8 00 00 08 00 Jan 17 11:16:22 Tower kernel: blk_update_request: I/O error, dev sdd, sector 468862120 Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower kernel: Buffer I/O error on dev sdd, logical block 58607765, async page read Jan 17 11:16:22 Tower emhttp: shcmd (175): set -o pipefail ; mount -t auto -o noatime,nodiratime /dev/sdd1 /mnt/cache |& logger Jan 17 11:16:22 Tower logger: mount: special device /dev/sdd1 does not exist Jan 17 11:16:22 Tower emhttp: shcmd: shcmd (175): exit status: 32 Jan 17 11:16:22 Tower emhttp: mount error: No file system (32)

No. They aren't all connected to the motherboard SATA sockets when the problem arises. I have my original SSD back in the server now, and it's only showing up as a total of 32.8kb drive. It isn't mountable, and I can't preclear or format the drive. I will be trying a SSD tomorrow evening that is known to be good and will report back. Thanks again for the help!

John_M, Thank you for the reply. I went into the bios and changed all drives from "integrated IDE" to AHCI mode. Same story with the SSD. I actually have 2 IcyDocks in my server. My primary use is for ease of drive swaps. I ended up swapping the cache drive to one empty slot in my other IcyDock. FYI, my first IcyDock has all slots going straight into my motherboard, my second icy dock has 4 slots from a PCI-Express card that I use for expansion. Anyway, after swapping it still didn't show up. I also tried to swap the old cache drive with another drive. In doing this, the drive didn't show up, but it also made a data drive show up as missing.

Hello, I logged into my server yesterday because Plex wasn't working. Upon investigation, Plex and some other dockers were stopped and I couldn't start them. I tried to remove the dockers to remake them and I was given an error that the docker didn't exist. I restarted the server and the cache drive wasn't there. I had the drive for a while so I figured it may be having issues. I replaced the drive today with another SSD, turned the server back on and the drive still isn't an option as a cache drive. The drive shows up when I use "preclear_disk.sh -l", but it fails almost immediately whenever I try to actually preclear it. I then shut the server off and swapped locations in my icydock...same story. Attached are my diagnostic files. tower-diagnostics-20170113-2111.zip

Has anyone got this working on Unraid 6? If so, what was the fix?

Thanks for the quick response. It seemed that the reads were good even when the issues were happening. I'll test it out. Thanks again!

I do have one more question though. Since the SATA errors have went away, would it be possible to test to see what the issue was? I would like to expand to 2-3 more drives soon, and i'm curious if it is the 2nd Icy Dock that is having issues or if it was the aoc-saslp-mv8? Or, could all of those SATA errors just have came from a bad drive? Thanks!

My old gigabit switch was the culprit. Taking it out of the loop brought back great read/write speeds. I appreciate all of the help!

I copied some files in mc and the following results happened. The results are below. Cache to Disk 1 - 80mb/s Cache to Disk 2 - started at 130mb/s, kept dropping until around around 30mb/s Cache to disk 3 - started 100mb/s, continue to drop until around 30mb/s Disk 1 to Cache - 70mb/s Disk 1 to Disk 2 - 15 mb/s - 20 mb/s Disk 1 to Disk 3 - 40-70mb/s initially….got down to averaging around 25-28mb/s towards the end. Disk 2 to Cache - 70mb/s down to 30mb/s Disk 2 to Disk 1 - around 20mb/s Disk 2 to Disk 3 - 80mb/s down to 30mb/s Disk 3 to Cache - 80mb/s down to 30mb/s Disk 3 to Disk 1 - 70mb/s down to 30mb/s Disk 3 to Disk 2 - 80mb/s down to 30mb/s

Ok. So, I moved all of the drives into the first icy dock (the one that didn't have the Seagate drive inside it). Please see the attached diagnostic file. I can copy from the server at high speed, but copying files to the server is still in the 3.0mb/s range. tower-diagnostics-20151110-1641.zip

Motherboard is Gigabyte AM3+ AMD DDR3 1333 760G GA-78LMT-USB3. 4gb of RAM. This server originally had a lot more drives in, but about a year and a half ago I redid my configuration and took some drives, out, etc, etc. I have 2 Icy Dock MB-455SPF-B's. The top Icy Dock is using 5/6 of the onboard SATA slots (just 2 drives in this - Samsung 1.5tb drive, WD 2tb green). Bottom Icy dock has the remaining onboard SATA slot and the other 4 are filled up with a super aoc-saslp-mv8 (contains the cache drive - 320gb WD Blue, Seagate 2tb, and Hitachi 2tb). I just took off the side of the case and made sure all power connectors/sata connectors were snug. Leaving it offline and open in case there are further questions.

ljm42, Thank you for the reply. It has been sometime since i've been on the boards. I cannot remember the exact version I was on before, but I believe it was 5.0.6. The server is currently on 6.1.3. I have connected straight into my gigabit switch and the transfers are the same speeds, roughly 3.5mb/s - 5mb/s. I can tell by looking at the Syslog that i'm having some SATA issues also. Diagnostic Zip is attached below. Thanks again! tower-diagnostics-20151109-1649.zip

I'm experiencing really slow transfers across ethernet and over wireless (802.11ac). Transfers average 2.5mb/s to 4.0mb/s. My connection from the server to the router states that it is set to 1gb/s, but transfers are ungodly slow since i've upgraded to version 6. I am currently using a 4 drive array and a cache drive. I will gladly post any files/screenshots that are needed for assistance. I"m using the following motherboard - Gigabyte AM3+ AMD DDR3 1333 760G GA-78LMT-USB3

That's good to know. Thanks. I've only got one Hitachi drive in my rig at the moment, and that's my parity. I know which one my cache drive is too. Fantastic to know. Thanks!

I was having power issues with my server and it knocked out my parity drive. I rebuilt the server with a new parity drive and all was well for a few days. My server was only up for a few days before more power issues happened and now I can't boot to get a picture of the drive info (what drive is attached to what in unRAID). I am wondering if there is a way to pull the drive information from the config file so that when I upgrade my motherboard I won't run into any drive/data issues. Edit: I swapped out the motherboard with no issues. The drives pulled back just like they were on the other board with a different layout. Thanks!

I hate to bring up really old posts, but i'm looking at purchasing this board very soon (like today). Did you ever get this board up and going without issue?

I'm considering upgrading to this board (http://www.newegg.com/Product/Product.aspx?Item=N82E16813128565&nm_mc=AFC-C8Junction&cm_mmc=AFC-C8Junction-_-na-_-na-_-na&cm_sp=&AID=10446076&PID=3938566&SID=) and getting memory that will work with this board. I recently upgraded to an AMD Phenom II X4 945 and i'd rather not buy another CPU <3 months after this last one. The chipsets are the same for these boards. I don't think there will be any issues. Do you think this would be a good idea?