Frank1940

It seems to me, a few years ago, that there was a particular SATA card that could do this. If you are using any SATA expansion cards, list the Manufacturer(s) and model number(s). One thing to do is to post up your Diagnostics file ( Tools >>> Diagnostics in a new post) and let the real Gurus have a look at it.

Biggest problem with this is that the backup is on the array. If your flash drive fails, you probably will not be able to boot up the server to get at it.

This should not be the case! Do you have an Popup Blockers, Privacy, or Security apps installed on Firefox. If you do, whitelist your Unraid server GUI address. This is the usual cause for these types of issues. UnRaid's GUI has been designed and tested to work with all of the major browsers.

The other solution is to use a Molex-to-SATA power cable. (The Molex connector has no provision for +3 volt power on it.)

This problem can also often the result of this 'Fix' that MS has added as a security upgrade. See Here for more details:

First, try using the Windows Explorer to as the destination window that you drag-and-drop the file into: If that does not work. MS is trying to add more and more security to SMB usage in Windows. Here is a thread to read. Start on page three as it contains the most recent stuff that MS is doing to the default settings. https://forums.unraid.net/topic/53172-windows-issues-with-unraid/ Do check to see if Your computer has updated on April 9th or later. (The April updates are a real disaster! They should be fixed with re-released updates sometime later this month...) If it was, see if you roll them back and see if that fixes things.

Have you found this one: https://windowsreport.com/network-error-0x8007003b-fix/ (Found with Google and 'Error 0x8007003B: An unexpected network error occurred' as the target.) As much as you may not like it, it appears that MS is 'owning' this one. I can tell you that my WIN10 Pro-64Bit (version 1809) is not having this problem. (If you don't know what version is currently running on your Windows computer, type winver in the search box and click on the result.) By the way, when asking about Win10 issues, always list the version number, variety --Home, pro, etc-- and whether 32-or-64 Bit. All of these have minor differences that make them unique! EDIT: Are you using a Mapped drive or working from the Network location in Windows Explorer?

You can turn the reporting of that Attribute off for just the cache drive under the Device properties for that drive only ( Main tab, click on the drive you need to modify under the Device column)

Found this with Google: https://forums.crucial.com/t5/Crucial-SSDs/Current-pending-sector-count-on-Crucial-MX500-1TB-SSD-s/m-p/187948 PErhaps you will find something in it that might be of help to you.

You have the latest version for the Stable release Branch--- 6.6.7. The updated version is only for the Next (Read, 'Beta') release Branch--- now 6.7.0-rc7. I have the same issue on my Media server. You will be able to update under two conditions. (1) you change to the Next Branch or (2) 6.7.0 is released as the Stable Branch version.

@limetech, it appears that this request is on the to-do list. Any idea when we might see it?

When I update, it always pauses at this point for (what seems to be) a substantial period of time. Did you wait a couple of minutes to see if it would actually continue?

Have you tried this? (The GUI boot process is different from the non-GUI boot.)

Did you reboot the router and any switches connected to the server and the router? These things all are computer like chip sets and a reboot will often solve problems...

I looked through your Diagnostics file and saw that in the syslog, there were a lot of errors that involved disk 1. This is the beginning of that sequence: Mar 23 01:25:28 MediaNAS kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 23 01:25:28 MediaNAS kernel: ata3.00: irq_stat 0x40000001 Mar 23 01:25:28 MediaNAS kernel: ata3.00: failed command: READ DMA EXT Mar 23 01:25:28 MediaNAS kernel: ata3.00: cmd 25/00:40:a8:f2:98/00:05:81:01:00/e0 tag 23 dma 688128 in Mar 23 01:25:28 MediaNAS kernel: res 51/40:00:08:f6:98/00:00:81:01:00/00 Emask 0x9 (media error) Mar 23 01:25:28 MediaNAS kernel: ata3.00: status: { DRDY ERR } Mar 23 01:25:28 MediaNAS kernel: ata3.00: error: { UNC } Mar 23 01:25:28 MediaNAS kernel: ata3.00: configured for UDMA/133 Mar 23 01:25:28 MediaNAS kernel: sd 3:0:0:0: [sdd] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 23 01:25:28 MediaNAS kernel: sd 3:0:0:0: [sdd] tag#23 Sense Key : 0x3 [current] Mar 23 01:25:28 MediaNAS kernel: sd 3:0:0:0: [sdd] tag#23 ASC=0x11 ASCQ=0x4 Mar 23 01:25:28 MediaNAS kernel: sd 3:0:0:0: [sdd] tag#23 CDB: opcode=0x88 88 00 00 00 00 01 81 98 f2 a8 00 00 05 40 00 00 Mar 23 01:25:28 MediaNAS kernel: print_req_error: I/O error, dev sdd, sector 6469251752 Mar 23 01:25:28 MediaNAS kernel: md: disk1 read error, sector=6469251688 Mar 23 01:25:28 MediaNAS kernel: md: disk1 read error, sector=6469251696 Mar 23 01:25:28 MediaNAS kernel: md: disk1 read error, sector=6469251704 I am not sure what is going on here (as I no Guru when it comes to these types of problems) but you could could google things like failed command: READ DMA EXT and print_req_error: I/O error, dev sdd, sector 6469251752 Or wait until someone more knowledgeable comes along.

One thing to remember that when you change your server configuration and still have the same problem, it is wise to attach a new Diagnostics file which contains the time frame during which you had the problem. You have to realize that you seem to have an unique problem. (If this were a common problem/issue, this board would be have hundreds of threads similar in nature to yours.) One thing I would be tempted to try is to pull that ethernet card and set the server up using a single ethernet port. That would give you a setup virtually identical to what a lot of users employ. If the problem exists then, it is something besides the bonding setup. By the way, what are you using all of that i7 processing power for? It seems to be overkill for a simple server setup...

As I recall, this has been a problem in the past but I can not remember the solution. Try googling unraid server gui boot mode and see if the solution is there.

If you are filling up your array, you could be saturating the hard drive as it could now be the slowest link in the chain and buffering could become an issue if you are both writing a new file and reading a different file from the same disk. (Most of the time the slowest link has been the network speed!) As I recall, most Hard drives can not use all of the bandwidth which SATA2 provides.

So you are writing directly to the array with a 3Gb stream and expecting to be able to read from the array at the same time? I see you have a cache drive but you will quickly fill it up at 3Gb/sec and the writes will then bypass the cache and go straight to the array. Are these writes small data type files or BluRay ISO's? Small files can generate tremendous amounts of file handling overhead. Plus in the SMART section is this report: ST4000DM000-1F2168_Z30158FJ-20190320-0234 parity (sdb) - DISK_INVALID.txt Is this true? What is going on here? Are you rebuilding parity while you are attempting to read and write from the array?

You should really post up the Diagnostics file. Tools >>> Diagnostics

This is a bit outside of my area of comfort but I do have a couple of suggestions. First, rather than the separate files goto Tools >>> Diagnostics. That will download a 'zipped' of all the files which will give the Gurus what they are looking for. Second item, don't panic. It is telling you that there is a problem on IRQ16 but no process, program, or device (That's the "nobody") has complained about the problem---Yet.

I did a quick search and I don't believe this is what you want. It is a dedicated RAID card and won't work with Unraid. Read here for a details on the type of card that you should be looking for: https://forums.unraid.net/topic/69018-sata-controller-replacement-question-and-advice/?tab=comments#comment-630097

In Linux, directories that begin with a dot (.) are considered to be hidden directories. Also, a Linux directory must have the "execute" attribute turned on to be browse-able. (i.e., to be able to list the contents of the directory.) I suspect that they are housekeeping files and directories used by the Apple OS and for internal use by other programs. I am not an Apple user but I would suggest that you use Google (Google is your friend if you have to support different computing environments..) and see if you can find out what these contents of these directories are. I know that the Apple OS's are based on UNIX and the file permissions are probably very similar. What you have run into is always an issue when you mount a disk using a 'foreign' format on another OS. One thing to try is to copy these files/directories to your server using SMB from an Apple computer. You have done the heavy lifting by getting the data files across. The permissions will probably get converted as they come across...

Try it with the switch in the other position...

That's how I would read it too!!! Each SATA outlet is limited to 40A. And you REALLY don't want 40 amperes flowing down the wire used in any of those SATA connectors. I would be tempted to use the "Multiple" position just to provide a bit of protection in case something really screwy happens. (There have been a few cases where molded SATA power connectors have shorted out (manufacturing defects) and caused a fire (or fire-like conditions).