Fireball3

Hi @stinger303, did you solve your issue? Is your card in RAID mode? The Dell website is a pain to search for, but on the Broadcom (LSI) site you can find the card. https://www.broadcom.com/products/storage/host-bus-adapters/sas-9217-8i#downloads You can give that a try, although I'm not sure if there is a vendor check that could stop you from flashing. I will compare the content of that file, because it seems like the same firmware as used for the H200/H310 cards. If that's the case, chances are good that you can do it with the tools we have already. Edit: Looks like the files are not identical. A crossflash with the 9211 IT firmware is risky! The card uses another chip, so it is highly possible to brick it when trying the old firmware. Unfortunately, I'm also not able to find a Dell taylored firmware for IT mode. The most reasonable step would be to open a ticket with the Dell support and try to get the IT firmware for the card or at least a confirmation that there is none. But before doing so, give the LSI firmware a chance. Maybe there is no vendor check!?

Not sure if I fully understand your problem. The expander needs the PCIe slot for power. It won't work standalone - that's right. But you can connect it to your newly flashed HBA. I've seen a pic around here of an expander not plugged into the PCIe slot. Possibly powered by another source. Check the manual for details maybe. Edit: I found the pic.

The H97 should be UEFI, but I cant check right now. The toolset used for the Dell H310 has the necessary files for an EFI boot. Cant post a link as I'm on my mobile only.

Is your BIOS up-to-date?

Do you have your boot stick prepared with EFI files? Usually on the last BIOS page (the save and exit page) you can select to override boot. There you can select your boot stick in EFI mode.

Stick to an i7 to have the HT onboard! The 8700 without K is also a viable option to reduce costs and heat. :-)

Not sure about the origin of those china cards. Risk is that you get a faked one. Usually not.

Right, the LSI SAS2008 based cards can be recommended. They can handle state of the art SATAIII disks to their full potential. The only issue might be availability. In EU those cards and the rebranded ones (the ones that need crossflashing) can be shot in the bay for ~40€. DELL and Fujitsu cards are often on ebay in EU. LSI and IBM not so. You have to check what's the situation at your place. The LSI SAS 9201-16i is also often cited around here. PCIe 3.0 cards can handle SSDs.

https://wiki.lime-technology.com/Hardware_Compatibility#PCI_SATA_Controllers

Have your partiy checks always been like that?

In order to do so you would need a copy of your old config - afaik. It's always a good idea to pull a copy of the unRAID stick before changing the setup! Exactly.

You can try preclear on that drive once you have replaced it. That may reveal more issues. If it stays stable, you can still have it as a data drive but keep an eye on it and maybe copy less valuable data on it.

Not impossible, but very, very unlikely. The more plausible scenario is that your plex didn't notice that the files were moved. If the parity check should have solved that issue it would have noticed errors. According to your introducing post, there were no sync errors. Probably the plex scraper ran in the meantime and updated the database.

Adding some background information: It happened while the mover was running. The process is read-modify-write. That means, the parity bits are read, modified according to the new data that has to be written and subsequently the write of the new bits on the parity will take place. Now the "read" was not successful at some sectors. I suppose the parity is being calculated and written to the parity regardless of the read error. During a parity check unRAID will do the same. A read error on any disk will be corrected by using the redundant information available - either by rebuilding the parity, if the error is on the parity drive, or by rebuilding from parity, if the error is on a data drive. There were no write errors, else the drive would have dropped out. In a single-drive scenario, this issue would have been data corruption. I wonder why the errors are not counted in the smart log. Taking into consideration that you ran the parity check a few days ago and no error manifested, you should have an eye on this drive. If it's throwing more read errors you should consider replacing it. Replacing the parity is fine, as the data drives seem to be healthy. But if you had this kind of issues on a data drive and would replace the parity drive you would risk a rebuild error.

Read errors on the parity disk. Try to run an extended smart test on that disk. IIRC the option is available through the dashboard in the drive properties. Nov 6 03:41:35 Slipstream kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 6 03:41:35 Slipstream kernel: ata11.00: irq_stat 0x40000001 Nov 6 03:41:35 Slipstream kernel: ata11.00: failed command: READ DMA EXT Nov 6 03:41:35 Slipstream kernel: ata11.00: cmd 25/00:d8:b0:ed:a3/00:03:2e:01:00/e0 tag 13 dma 503808 in Nov 6 03:41:35 Slipstream kernel: res 51/40:60:28:f1:a3/00:00:2e:01:00/0e Emask 0x9 (media error) Nov 6 03:41:35 Slipstream kernel: ata11.00: status: { DRDY ERR } Nov 6 03:41:35 Slipstream kernel: ata11.00: error: { UNC } Nov 6 03:41:35 Slipstream kernel: ata11.00: configured for UDMA/133 Nov 6 03:41:35 Slipstream kernel: sd 11:0:0:0: [sdl] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 6 03:41:35 Slipstream kernel: sd 11:0:0:0: [sdl] tag#13 Sense Key : 0x3 [current] Nov 6 03:41:35 Slipstream kernel: sd 11:0:0:0: [sdl] tag#13 ASC=0x11 ASCQ=0x4 Nov 6 03:41:35 Slipstream kernel: sd 11:0:0:0: [sdl] tag#13 CDB: opcode=0x88 88 00 00 00 00 01 2e a3 ed b0 00 00 03 d8 00 00 Nov 6 03:41:35 Slipstream kernel: blk_update_request: I/O error, dev sdl, sector 5077462448 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462384 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462392 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462400 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462408 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462416 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462424 Nov 6 03:41:35 Slipstream kernel: ata11: EH complete Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462432 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462440 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462448 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462456 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462464 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462472 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462480 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462488 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462496 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462504 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462512 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462520 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462528 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462536 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462544 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462552 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462560 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462568 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462576 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462584 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462592 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462600 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462608 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462616 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462624 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462632 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462640 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462648 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462656 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462664 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462672 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462680 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462688 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462696 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462704 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462712 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462720 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462728 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462736 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462744 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462752 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462760 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462768 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462776 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462784 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462792 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462800 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462808 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462816 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462824 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462832 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462840 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462848 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462856 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462864 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462872 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462880 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462888 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462896 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462904 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462912 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462920 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462928 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462936 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462944 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462952 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462960 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462968 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462976 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462984 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077462992 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463000 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463008 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463016 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463024 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463032 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463040 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463048 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463056 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463064 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463072 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463080 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463088 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463096 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463104 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463112 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463120 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463128 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463136 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463144 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463152 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463160 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463168 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463176 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463184 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463192 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463200 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463208 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463216 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463224 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463232 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463240 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463248 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463256 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463264 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463272 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463280 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463288 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463296 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463304 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463312 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463320 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463328 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463336 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463344 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463352 Nov 6 03:41:35 Slipstream kernel: md: disk0 read error, sector=5077463360 edit: how 2 make the code windows expandable?

SATA cables may be prone to crosstalk if tied together. Depends on cable quality and source of EMI.

Have you tried another cable?

How is the disk itself connected to the sata port? Through a backplate/hot swappable bay? Directly via cable?

Thanks for your feedback! Can you post the content of the your (stock) config.sys? v4 config.sys looks like this DEVICE=c:\fdos\himemx.exe DOS=HIGH,UMB BUFFERS=25 I wonder what rufus does to get more xms.

HDMI has way higher data rates than Gbit ethernet! Are those externders/converters using some kind of compression? Lossless? Lag? I'm very curious about the performance. There are expensive ones too. Are they performing better or what? Seeing 2k and 4k video on the horizon, I feel it makes little sense to install max. 1080p capable hardware. I have Cat7 running all over the place, going to a patch panel in the basement. Pulling HDMI is no viable option, that's why I'm interested in those things.

Maybe you can check if this post offers a solution for you? https://rog.asus.com/forum/showthread.php?2668-Wake-On-Lan-Maximus-IV-Extreme&p=55088&viewfull=1#post55088 It seems there is one more option you need to set. Sounds like it is a windows specific setting... Is your WOL packet send correctly? Have you tried another tool/app? I'm also using the Ben Finnigan's app on my mobile - works perfect. Windows clients may have firewall issues you need to take care of first. one last edit: Some routers offer to wake up clients from within their GUI. Not practical, but interesting for testing.

No, only if you interrupt the mains to the machine or in case you reboot your router. I just checked the manual of your board. For me, it's not so clear if the option PCI-e/PCI includes the NIC.

The BIOS setting affects only the onboard NIC. If you're using an add-on card it might not work. Also the unRAID server has to run once because the router needs to learn his MAC/IP.

https://en.wikipedia.org/wiki/Parity_bit A cleared drive is not affecting the parity bit as it has all "0" on it.

I had to google that...never heard of. Interesting read https://drbobtechblog.com/ssd-makes-legal-hold-nightmare-process/ Seems the enterprise grade SSD's do the DZAT https://www.win-raid.com/t1366f25-Nightmare-to-find-a-SSD-with-functional-TRIM-on-LSI-SAS.html