DivideBy0

No idea where to even start. This is a brand new build and worked perfect. [ 1665.687896] mdcmd (46): spindown 1 [ 1667.489404] mdcmd (47): spindown 3 [ 1668.355199] mdcmd (48): spindown 5 [ 1669.117221] mdcmd (49): spindown 6 [ 1670.988363] mdcmd (50): spindown 2 [ 1671.400049] mdcmd (51): spindown 7 [ 1672.711065] mdcmd (52): spindown 0 [ 1673.235264] mdcmd (53): spindown 4 [ 1704.985031] sd 1:0:5:0: attempting task abort! scmd(000000000eb7137d) [ 1704.985038] sd 1:0:5:0: [sdi] tag#1739 CDB: opcode=0x85 85 08 2e 00 d0 00 01 00 00 00 4f 00 c2 00 b0 00 [ 1704.985042] scsi target1:0:5: handle(0x000e), sas_address(0x4433221104000000), phy(4) [ 1704.985044] scsi target1:0:5: enclosure logical id(0x500605b001f31400), slot(7) [ 1707.334599] sd 1:0:5:0: task abort: SUCCESS scmd(000000000eb7137d) [ 1714.456866] sd 1:0:6:0: attempting task abort! scmd(0000000036a10ce2) [ 1714.456873] sd 1:0:6:0: [sdj] tag#1739 CDB: opcode=0x85 85 08 2e 00 d0 00 01 00 00 00 4f 00 c2 00 b0 00 [ 1714.456877] scsi target1:0:6: handle(0x000f), sas_address(0x4433221105000000), phy(5) [ 1714.456879] scsi target1:0:6: enclosure logical id(0x500605b001f31400), slot(6) [ 1716.587485] sd 1:0:6:0: task abort: SUCCESS scmd(0000000036a10ce2) [ 1723.736696] sd 1:0:7:0: attempting task abort! scmd(0000000022e95427) [ 1723.736704] sd 1:0:7:0: [sdk] tag#1739 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00 [ 1723.736708] scsi target1:0:7: handle(0x0010), sas_address(0x4433221107000000), phy(7) [ 1723.736710] scsi target1:0:7: enclosure logical id(0x500605b001f31400), slot(4) [ 1727.547741] sd 1:0:7:0: task abort: SUCCESS scmd(0000000022e95427) [ 1734.616503] sd 1:0:0:0: attempting task abort! scmd(00000000f7ea3896) [ 1734.616510] sd 1:0:0:0: [sdd] tag#1739 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00 [ 1734.616514] scsi target1:0:0: handle(0x0009), sas_address(0x4433221101000000), phy(1) [ 1734.616516] scsi target1:0:0: enclosure logical id(0x500605b001f31400), slot(2) [ 1735.965906] sd 1:0:0:0: task abort: SUCCESS scmd(00000000f7ea3896) [ 1743.064350] sd 1:0:1:0: attempting task abort! scmd(0000000005f951d9) [ 1743.064357] sd 1:0:1:0: [sde] tag#1739 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00 [ 1743.064361] scsi target1:0:1: handle(0x000a), sas_address(0x4433221100000000), phy(0) [ 1743.064363] scsi target1:0:1: enclosure logical id(0x500605b001f31400), slot(3) [ 1745.517380] sd 1:0:1:0: task abort: SUCCESS scmd(0000000005f951d9) [ 1746.320544] sd 1:0:0:0: Power-on or device reset occurred [ 1746.617091] sd 1:0:1:0: Power-on or device reset occurred [ 1752.664178] sd 1:0:2:0: attempting task abort! scmd(0000000051428bb3) [ 1752.664185] sd 1:0:2:0: [sdf] tag#1739 CDB: opcode=0x85 85 08 2e 00 d0 00 01 00 00 00 4f 00 c2 00 b0 00 [ 1752.664189] scsi target1:0:2: handle(0x000b), sas_address(0x4433221102000000), phy(2) [ 1752.664191] scsi target1:0:2: enclosure logical id(0x500605b001f31400), slot(1) [ 1754.717920] sd 1:0:2:0: task abort: SUCCESS scmd(0000000051428bb3) [ 1754.954073] sd 1:0:2:0: Power-on or device reset occurred [ 1761.879991] sd 1:0:3:0: attempting task abort! scmd(00000000c8121b0e) [ 1761.879998] sd 1:0:3:0: [sdg] tag#1741 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00 [ 1761.880001] scsi target1:0:3: handle(0x000c), sas_address(0x4433221106000000), phy(6) [ 1761.880004] scsi target1:0:3: enclosure logical id(0x500605b001f31400), slot(5) [ 1763.994865] sd 1:0:3:0: task abort: SUCCESS scmd(00000000c8121b0e) [ 1764.454095] sd 1:0:3:0: Power-on or device reset occurred [ 1764.798221] sd 1:0:3:0: Power-on or device reset occurred [ 1771.415851] sd 1:0:4:0: attempting task abort! scmd(000000007c8ca53c) [ 1771.415858] sd 1:0:4:0: [sdh] tag#1743 CDB: opcode=0x85 85 08 2e 00 d0 00 01 00 00 00 4f 00 c2 00 b0 00 [ 1771.415862] scsi target1:0:4: handle(0x000d), sas_address(0x4433221103000000), phy(3) [ 1771.415864] scsi target1:0:4: enclosure logical id(0x500605b001f31400), slot(0) [ 1773.783703] sd 1:0:4:0: task abort: SUCCESS scmd(000000007c8ca53c) [ 1774.209400] sd 1:0:4:0: Power-on or device reset occurred [ 1774.548365] sd 1:0:4:0: Power-on or device reset occurred [ 1776.706407] sd 1:0:5:0: Power-on or device reset occurred [ 1777.113346] sd 1:0:6:0: Power-on or device reset occurred [ 1777.328910] sd 1:0:7:0: Power-on or device reset occurred [ 1904.050210] sd 1:0:2:0: Power-on or device reset occurred root@NAS-UNRAID-BKP:~# nas-unraid-bkp-diagnostics-20200721-2035.zip

I did google it and found some similar errors but not a real clear fix. I already moved on but I guess this is free support right I am glad it works for others

Well I guess I uninstalled and moved on to something else. This place is pretty DEAD

Thanks for putting this together mate. I got it all configure but I get some errors during the backup. See attached pic. Couldn't find anything related so I posted here. Any ideas?

I tried balance-alb and still does not work. This should be straight forward

I tried this option but it looks like it still needs to go through a switch I just want run the 4 cables across the 2 boxes and the bond them together somehow. Snap, why is always so hard

I have 2 Unraid boxes with 4 ethernet interfaces each. Is it possible to do bonding / link aggregation - 802.3ad with direct cables (box to box) rather than going through a switch capable of 802.3ad? If I need to go through a switch I will have to waste 8 ports with 8 cables when I can just run 4 cables between the 2 unraid boxes. Is it possible? This links claims is possible. -->. I tried it but it does not work

Thanks and sure gents here is the enclosure link: Case: U-NAS NSC-800 Server Chassis http://www.u-nas.com/product/nsc800.html or eBay https://www.ebay.com/itm/NEW-U-NAS-8-Bay-Mini-ITX-NAS-Storage-Server-Case-Chassis-Kit-with-PSU-Cabling/264615987529?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649

Any ideas? [238880.231100] mce: [Hardware Error]: Machine check events logged [238880.231105] mce: [Hardware Error]: Machine check events logged root@NAS-UNRAID:~# mcelog Hardware event. This is not a software error. MCE 0 CPU 6 BANK 5 ADDR 443c14058 TIME 1593517768 Tue Jun 30 06:49:28 2020 MCG status: MCi status: Error overflow Corrected error Error enabled MCi_ADDR register valid MCA: MEMORY CONTROLLER RD_CHANNEL0_ERR Transaction: Memory read error STATUS d400008000900090 MCGSTATUS 0 MCGCAP 806 APICID c SOCKETID 0 MICROCODE 12d CPUID Vendor Intel Family 6 Model 77 Hardware event. This is not a software error. MCE 1 CPU 3 BANK 5 ADDR 443c14058 TIME 1593517768 Tue Jun 30 06:49:28 2020 MCG status: MCi status: Error overflow Corrected error Error enabled MCi_ADDR register valid MCA: MEMORY CONTROLLER RD_CHANNEL0_ERR Transaction: Memory read error STATUS d400008000900090 MCGSTATUS 0 MCGCAP 806 APICID 6 SOCKETID 0 MICROCODE 12d CPUID Vendor Intel Family 6 Model 77 root@NAS-UNRAID:~# root@NAS-UNRAID:~# 7.3.2020 root@NAS-UNRAID:~# root@NAS-UNRAID:~# mcelog Hardware event. This is not a software error. MCE 0 CPU 1 BANK 5 ADDR 443c14040 TIME 1593741488 Thu Jul 2 20:58:08 2020 MCG status: MCi status: Corrected error Error enabled MCi_ADDR register valid MCA: MEMORY CONTROLLER RD_CHANNEL0_ERR Transaction: Memory read error STATUS 9400004000900090 MCGSTATUS 0 MCGCAP 806 APICID 2 SOCKETID 0 MICROCODE 12d CPUID Vendor Intel Family 6 Model 77 Hardware event. This is not a software error. MCE 1 CPU 4 BANK 5 ADDR 443c14040 TIME 1593741488 Thu Jul 2 20:58:08 2020 MCG status: MCi status: Corrected error Error enabled MCi_ADDR register valid MCA: MEMORY CONTROLLER RD_CHANNEL0_ERR Transaction: Memory read error STATUS 9400004000900090 MCGSTATUS 0 MCGCAP 806 APICID 8 SOCKETID 0 MICROCODE 12d CPUID Vendor Intel Family 6 Model 77 Hardware event. This is not a software error. MCE 2 CPU 2 BANK 5 ADDR 443c14040 TIME 1593741488 Thu Jul 2 20:58:08 2020 MCG status: MCi status: Corrected error Error enabled MCi_ADDR register valid MCA: MEMORY CONTROLLER RD_CHANNEL0_ERR Transaction: Memory read error STATUS 9400004000900090 MCGSTATUS 0 MCGCAP 806 APICID 4 SOCKETID 0 MICROCODE 12d CPUID Vendor Intel Family 6 Model 77 root@NAS-UNRAID:~# root@NAS-UNRAID:~#

This place id DEAD This stuff ain't working It scaned for 2 freaking days and now is STUCK. Any ideas? It won't move or transfer anything

CyberPower here. Works perfect with the Unraid and replacement batteries are much cheaper. I have 2 of these

SanDisk 64GB Cruzer Fit USB Flash Drive - SDCZ33-064G-G35 This is a 2.0 and runs fine and at a very low temperatures. Read the reviews on them. I use them on my PBX and they've been running fine for years. I think you're over engineering this one

What I noticed on the SAS drives is that they're running hotter than SATA. I guess the 72K RPM does that for you. You will need better airflow and ventilation if you go with SAS. Ask me how I know

Define slow?

Thank you Sir

Anything I can do to tune or make my "iowait" better. I am doing a large files move 4.2 TB between drives and this is what I get The transfer speed is horrible as well 25.8 MB/s

Or Rufus for windows Agreed

Try this: # screen (install it from nerdools if you don't have it) #screen #cd / # while true; do ps -eocomm,pcpu | egrep -v '(0.0)|(%CPU)' >> cpu.log; echo "do a little dance, get down tonight"; sleep 1; done & If the servers dies and your reboot get back to and do # cd / # tail -f cpu.log # cat cpu.log |more and look for the app taking the most CPU? But the idea of elimination as suggested here is the way to go, turn everything off and then turn each docker/container/vm on one at the time.

Salute the scouts Now they have their own Minecraft server

I think sky is the limit but will take some upfront work to get all your requirements satisfied. Start small, one by one, and make sure you have a good backup strategy to recover your work environment in case of need. I can't speak from experience but I see most of requirements being satisfied by various plugins and dockers. You may need a beefed up server to run all of this. If raid file system is not a requirement I would rather go a full Linux distro server more geared toward like small business. Also depends on your *nix knowledge and appetite to learn on the fly? Many variables

Absolutely Sir. Here it is for both unraids: UNRAID -1 - Case: U-NAS NSC-800 Server Chassis - Power: Model: KW-3011F-1M1 - Mobo: Supermicro A1SRi-2758F - Mini ITX - Intel Atom C2758 - CPU: Intel Atom C2758 4 cores / 8 threads - built in motherboard - 4 Ethernet ports + IPMI Management Port with license - RAM: Samsung 32GB ECC (2 x 16) - USB Drive Sandisk 64G - on the motherboard - 2 X SSD Drives - Kingston 480GB - cache drives - SATA: LSI 9220-8i IBM M1015 SAS P20 IT Mode For ZFS FreeNAS unRAID 6Gbps SAS HBA US - Pcie Riser Cable PCI-e PCI Express 8X Extension pci-e 8X Card - 8 X 8 TB SATA Segate drives 5200 RPM UNRAID -2 - Case: U-NAS NSC-800 Server Chassis - Power: Model: KW-3011F-1M1 - Mobo: Supermicro A2SDi-4C-HLN4F - Mini ITX - Intel Atom C3558 - CPU: Intel Atom C3558 4 cores / 4 threads - built in motherboard - 4 Ethernet ports + IPMI Management Port with license - RAM: Supermicro 64GB ECC (2 x 32) - USB Drive Sandisk 64G - on the motherboard - 2 X SSD Drives - Kingston 480GB - cache drives - 1 X NVME Drive - Samsung 960 - 256 GB - FreeNAS dual boot or cache drive - SATA: LSI 9220-8i IBM M1015 SAS P20 IT Mode For ZFS FreeNAS unRAID 6Gbps SAS HBA US - Pcie Riser Cable PCI-e PCI Express 8X Extension pci-e 8X Card - 4 X 5TB SATA Segate drives 5400 RPM - 4 X 4TB SATA Segate drives 5400 RPM

Yes run it the root prompt# #cd / #mcelog > mce.log #cat mce.log Copy here the cat mce.log output please

Well did you run the mcelog command? What was the output? #mcelog You do have something in the syslog: Jun 21 05:02:07 Tower kernel: mce: [Hardware Error]: Machine check events logged

Some info here I guess?