jordan

Thanks. I had this drive fail yesterday, so DB is currently not running and I'm rebuilding; then I'll be moving the entire array to a new (better cooled) system. Christmas break is coming up, so I'll have a couple days to dive into it for real. If I do find the problem I'll post a solution back.

Quick followup - is anyone else getting tornado warnings in their log? From older threads it seems to be a connection error with the Dropbox backend but isn't critical. Still if there's an easy fix to remove them it would make my logs a bit cleaner.

I should add that all of my really important stuff is backed up to a cloud service and all but the last couple of days is on a portable drive in my fire safe (because as much as I love cloud backup, a multi-TB download on my internet connection would be painful). edit: by "important stuff" I pretty much mean all of my personal content. My commercial media...well, others have already uploaded that to the cloud, mostly in better quality than my own rips. I:-)

Everything - photos of the kids, home video, all my college coursework, my business files, everything. Poof - it's just locked inside a dead hard drive. So I just want to say a little thanks to the community and unraid because, of course, the server emailed me the drive suddenly failed, the server is running perfectly fine serving my files from the cache, and I only needed a few minutes to power down the server, and swap in a spare drive which is now being rebuilt. It's been pretty good for a "bad Monday."

I'm in the middle of switching from an old generic case with an icy-dock 5-in-3 (awful cooling - can't recommend)) to a DS380 from Silverstone with an ASRock Z390M-ITX/ac MB (6 SATA onboard + PCIe x4 M.2, one PCIe x16, 2x Intel 1000bt + wifi). One advantage I just found out about is that the HD trays are powered by a 4 pin Molex and I just confirmed that there is no 3.3v on the power bus for the rack. That means no messing with the pin-bypass hack on shucked drives - it's not powered in this system. I'm not sure about the cooling as I've not run it full of disks (SoonTM), but the placement of fans is good. The only issue I can see is that, while one side of the 8x bay is covered with two large fans, the opposite side is the sliding case is flush, so the drive fans pressurize the case and the rear fan draws that air from the drives, over the CPU cooler, then out. I'm running an i5-9400 with the stock cooler and it's about 4x the CPU I need, so I don't expect it to be an issue. The unit is reasonably quiet with the three fans running. The PS (300W Silverstone Bronze/80) hasn't fired up the fan yet (it's fanless at idle), but I'm just working through a memory test with no drives.

Sorry to dig up an old thread, but I've had piss-poor luck choosing MBs for unraid in the past. Did you ever get quick sync working on your i5-9 series on the asrock ITX board? I'm looking to move to a nicer box and this board seems like a winner if I can get hardware transcoding on the iGPU.

If you have a reference/tutorial you have seen for creating this, would you drop me a link in the reply? If not I can go through the google, but there are some exceptionally common terms in my likely query so any help or shortcut to resources would be appreciated. :-)

Okay, thanks. That's definitely going to take some reading.

That got it running. One last question (I hope) - After linking I'm greeted with the ominous [ALERT]: So your files continue to sync, sign in to your Dropbox account and move Dropbox to a supported file system. I just paged back through this thread, and I see where it came up last year when DB kicked everything but ext4 to the curb, but I can't tell whether there was a workaround built in, or everyone just bailed on the protected array and using external USB formatted to ext4? Or are those using it installing a trick like https://www.linuxuprising.com/2018/11/how-to-use-dropbox-on-non-ext4.html ?

Ah - makes sense. I didn't think to go back and scrub the old directories out manually. I'll try that.

I've clearly done something wrong, but I'm at a loss as to what. I initially tried updating the container and came up with an error so I deleted the container and reinstalled from Community Applications. I got (effectively) the same error: Did I miss some dependency or other pre-installation setup requirement?

No need for apologies; volunteer support when you're moving away from a platform is a tough spot. Thanks for checking, though! If it doesn't update, I'll try a different method. Thanks, again!

(warning: Docker newbie) I just installed it and am getting the error. I saw a post from back in 2017 that this was an issue, but am not clear on how it was resolved. The docker interface in unRaid claims that the application is up to date (and have already executed a check for updates). Apologies if I'm leaving out any critical information, this is my first experience with docker containers.

Thanks for the answers!

Hi, just upgraded to v6; went for a clean install so I could start my "new" build with just the parity-protected array intact. [edit: upgrade from 5.0.6] I see that the default setup is to set every top level directory as a Share. Convenient, except that I only need/want three of the forty shared. I also see that the default is to not share any of the Disk mounts as accessible, which is what I would prefer. I have two(-ish) questions: 1. How do I share the disks? (i.e. if I go into a Windows browser and type \\tower\disk1, the location doesn't exist, nor is it in the \\tower directory list) [edit] found this one in an old thread - enabling sharing for Disks is under Settings|Global Share Settings instead of in the Share tab 2. Can I mass-delete all of the existing Shares (not the folders/files, just the shares), or do I have to manually go into all 37 shares I don't want and set them to Export = no? 2a - if I set the shares to export=no and access the files from the /diskn share, does unRaid ignore the split, or must I also set allocation to fill-up and split level to manual? Thanks!

The Intel NIC looks like it has done the job. I've done 70-80GB of transfers with zero errors to multiple discs and in both directions (reading from and writing to to the server). As a bonus, my read transfers are now about double the speed they were with the old NIC. Thanks for the suggestion to disable the onboard NIC - I'm sure I said some choice words about it not being supported back when I installed the board, but didn't actually disable it in the BIOS when I installed the other card. I've also replaced the drive cable on Disk 1 - thanks for that!

I may have spoken too soon. I had success with files in the 800MB range, but I'm still having issues with network transfers of larger files (1.5+GB). To eliminate network gear, I connected directly between the server NIC and the client computer. That still produced CRC errors. The errors occur in both directions (to and from the server) and occur over both SMB and FTP. Multiple copies of the same file result in different checksums. I have a new (Intel) network card on order, but I'm open to any other suggestions.

Alright - first, thank you for taking a look at this, and I apologize for being a bit paranoid. Upon further testing, it seems that my *primary* machine has either a bad network cable or a bad network port. SOB. I do so much work on that machine I just never suspected it was wonky, and I rarely transfer big files except at that machine because it's on the gigabit switch with the server (so I get great throughput). You'll have to excuse me while I go collect the hair (I've been pulling out) that's all of the office and see about gluing back onto my head.

Thanks for your patience...the corrected smart for the cache is attached. System: Gigabyte GA-78LMT-S2P [southbridge = AMD SB710 -> 6 x SATA 3Gb/s onboard] AMD Bios 3.0.A AMD FX8320 CPU 2 x G.Skill 4GB DDR3-1333 RAM NetGear GA311 (rev A1) 1000bT NIC (onboard NIC is not recognized in unRaid) ICY Dock MB155SP-B 5 disk cage (for data and parity) XFX 550W power supply (20A 5V rail, 45A 12V rail) The system hasn't been physically moved in at least a year, probably more. I've re-booted. In the interim I ran a Memtest once through, using all CPU cores, and the results were zero errors. I reseated all the drives and checked (physically) the cable on Disk 4. It's locking-style, and seemed to be seated securely (not that it would matter if the cable was dodgy). Note that Disk 4 is currently not used for storage. It is set up as an overflow for Disk 2. Disk 1 has known corruption (executable files and archives which are failing CRC or other checks), Disk 2 I also suspect has data corruption, but it's all movies so it's harder to tell. Disk 3 Is either stuff I never use (archived/non-active DVD rips) or downloaded TV - and they quality of that is poor in the best of times ;-) Attached is the correct cache SMART, a new Syslog created after bootup, then a second from late in the day (after all of the testing below). --------------- Further testing done today: Note: I know almost nothing about how an MD5 hash is created, so all of this may have just been pissing in the wind, but I'm going to post it just in case there is something useful... I tried transferring a two test files (500MB zip file full of drivers, and a 4kB text file) and computed an MD5 hash of the file 500GB File: PC - PC -> Pass (using FVIC utility) PC - Disk 1 -> fail (using md5sum in telnet session) PC - Disk 3 -> fail (using md5sum in telnet session) PC - Disk1 - PC -> fail PC - Disk3 - PC -> fail *After this test I removed the cache drive from the array and restarted the tests, just to make sure I wasn't hitting the cache only Disk1 - Disk3 -> Pass (using telnet session using cp, md5sum) 4kB file PC - PC -> Pass (using FVIC utility) PC - Disk 1 -> Pass (using telnet and md5sum) PC - Disk 1 - PC -> Pass PC - Disk 3 - PC -> Pass Tests which failed were re-run after switching the port on the switch, all failed Tests which failed were re-run after switching the cable to the switch, all failed Tests which failed were re-run after switching the server to the main router, all failed Tests which failed were re-run after switching the PC to a new cable and connected to the main router, all failed As a network test: I copied the files to a second laptop (windows sharing) through the main router, the 500MB failed MD5 and SHA1, the 4kB passed. I then put two laptops on a separate router, isolated from the rest of the network, and the file transferred correctly.Now that I know that works, tomorrow I'll try isolating other parts of the network. Syslogs.zip

Oops - didn't even think to put the SMART for the cache drive in that zip. The cache SMART is attached. cache.txt

Syslog is attached. SMART with disks labeled. Known errors are on discs 1 and 3 (sdc, sdf), others may have errors but it's unknown at this time. I'll be going through the wiki this afternoon. Thanks a bunch for the help! syslog.zip SMART.zip

BAsics: v5.0.5, Plus license 5 disks, 4TB ea, plus a cache drive (120GB SSD) I switched from a 4.x server to a new 5.x server about two years ago. it's becoming clear to me that I have widespread file corruption over at least two of the four data disks. The corruption typically is only seen in large files (250MB and larger, but it could very well exist everywhere and I'm just not seeing it. I've had issues with video files which used to play fine having problems (unable to copy file, or artifacts that did not used to be there), and now that I'm reinstalling a bunch of software on a new PC, many of my installation archives are bad - they simply fail CRC checks or other pre-install verifications of container integrity. It is a "current" and not a past or data transfer issue from the old server as I have verified that recent files (placed in the last 3 months) are also corrupt. Most of the data is commercial, or re-rippable, but there are personal files on there as well, and - being 1-2 years into this server - almost everything in the distant past has been overwritten on backups, and the new backups are likely to be corrupted. (edit, a parity check runs every month on the 1st, which suggests to me that the errors are introduced at write time) My question is: how do I go about testing to determine the cause of the corruption? Is there a simple way to isolate whether it's an OS issue, a disk issue, a memory issue, a network error, or some other error? I'm at a loss for efficiently assessing the likely causes and getting them corrected. Any suggestions are appreciated. Note that I rarely work with linux - I'm perfectly comfortable with the command line, but I primarily work in windows so most of the internals of unRaid are fairly black-box to me. TIA Edit: my only reason, currently, for not moving to v6 is to prevent things up worse than they already are. If upgrading will make the troubleshooting easier, then I'll do that first.

Yes, and I've started that with one drive before realizing that I could just cp. However, on my Win7 box the LinuxInternals application steals the focus of the system cursor for 3-4 second every 1-2 minutes, so I can't do day-job work at the same time the application is copying files without going batty. It sure beats the interface of the YAReG reader I used a couple of years ago to get a couple of files off of an old drive, though! I may try it on another machine, but I'm running out of "spare" machines that are otherwise idle!

Thanks! Yup, I would have been caught with that and probably wondered what happened.

System up, parity calculated and being verified, backups copying (everything but movie/tv media). One last question...is there anything non-obvious that would preclude me from mounting the *known good* old drives (which are still installed) and simply cp the movie/tv media (unbacked up stuff) data over? There is no overlap between the backups and un-backed up files - they're in a different top-level folder - and user shares are turned off until I can get all the data back and re-organized on the new server. I have successfully test-mounted one of the old drives, and can't see a problem with a straight cp command to a new folder, but better to ask first.