DivideBy0

CrashPlan Performance Question & Guidance Am I doing something wrong? I have gigabit ISP and yet I am pushing just 4 megs up I will be at this for 70 some days Is this common? Any tweaking I can do? Anything I should know? Best practices?

Thank you Sir. Still learning the ropes Cheers

I just finished this new build from scratch all new parts. I used only quality parts. I can give your remote access to pock around. I built this system as a backup / spare but I need the money for another fancy project List below with price per parts I purchased: - Case: U-NAS NSC-800 Server Chassis - $199 - Power: Model: KW-3011F-1M1 - $40 - Mobo: Supermicro A2SDi-4C-HLN4F - Mini ITX - Intel Atom C3558 - $370 - CPU: Intel Atom C3558 - built in motherboard - 4 Ethernet ports + IPMI Management Port with license - $25 - RAM: 64GB ECC (2 x 32) - $240 - USB Drive Sandisk 64G - on the motherboard - $20 - 2 X SSD Drives - Kingston 480GB - cache drives - $120 - 1 X NVME Drive - Samsung 960 - 256 GB used for FreeNAS install (dual boot) - $70 - SATA: LSI 9220-8i IBM M1015 SAS P20 IT Mode For ZFS FreeNAS unRAID 6Gbps SAS HBA US - $45 - Pcie Riser Cable PCI-e PCI Express 8X Extension pci-e 8X Card - $28 - 4 X 4 TB SAS Used Hitachi drives 7200 RPM - clear smart status with crystalinfo app - $200 - 4 X 4 Empty Trays for extra drives - No Unraid license as will not be transferable Total is 1,332 but I can do $1200 plus shipping. No lowballing as this is a brand new setup. I rather keep it than giving it away, sorry I am located in 77002 Houston The system on TOP is for sale As I said I built two. I stressed test the hell out of it just because I can.

The cards are loading fine in the kernel according to your "lsmod" output. --> e1000e. Do you se anything in the GUI? You should have 3 entries in your /boot/config/network-rules.cfg Something like this but I have 4 interfaces so this is just an example: root@NAS-UNRAID:~# cat /boot/config/network-rules.cfg # PCI device 0x8086:0x1f41 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="3c:ec:ef:12:46:74", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x1f41 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="3c:ec:ef:12:46:75", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x8086:0x1f41 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="3c:ec:ef:12:46:76", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x8086:0x1f41 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="3c:ec:ef:12:46:77", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" DELETE both files and reboot: Make a backup just in case as well /boot/config/network.cfg /boot/config/network-rules.cfg

You have other clients on that network getting a proper DHCP address? Your logs show something weird. 99.X network? Can't you just setup a static IP under Setting / Network Settings. Boot in GUI and setup up that way? Jun 23 10:43:34 Tower kernel: r8125: eth0: link up Jun 23 10:43:34 Tower kernel: br0: port 1(eth0) entered blocking state Jun 23 10:43:34 Tower kernel: br0: port 1(eth0) entered forwarding state Jun 23 10:43:34 Tower dhcpcd[2116]: br0: carrier acquired Jun 23 10:43:35 Tower dhcpcd[2116]: br0: soliciting a DHCP lease Jun 23 10:43:36 Tower dhcpcd[2116]: br0: offered 99.1.1.90 from 99.1.1.1 Jun 23 10:43:40 Tower dhcpcd[2116]: br0: probing for an IPv4LL address Jun 23 10:43:45 Tower dhcpcd[2116]: br0: using IPv4LL address 169.254.249.152 Jun 23 10:43:45 Tower dhcpcd[2116]: br0: adding route to 169.254.0.0/16 Jun 23 10:43:45 Tower dhcpcd[2116]: br0: adding default route

Am I doing something wrong? I have gigabit ISP and yet I am pushing just 4 megs up I will be at this for 70 some days Is this common? Any tweaking I can do? Anything I should know? Best practices?

sas2flash.exe -o -f 2118it.bin -b mptsas2.rom if I remember correctly. firmware and bios together

Thanks. Got it

Does the latest beta supports ZFS file system? I heard that somewhere?

Thanks guys. Makes sense.

I have 4 SAS 4TB 7200K RPM drives all showing the same SATA errors. Please help me decipher? I did a pre-clear on all drives last night. Is there a way to clear all these errors? Just trying to figure out what's going on and the next steps. nas-unraid-bkp-diagnostics-20200623-1701.zip

I just finalized building my second Unraid and I am doing a pre-clear on all drives, about 7 of them. The CPU is screaming for sure. Is a bit of a stress test as well. As the pre-clear is running the NVME drive (SAMSUNG_MZVLB256HAHQ-000L7) temperature went off the charts from 38 to a 64 C. Is this normal? I am sure the temperature will go down as the pre-clear on all drives will finish? Did I damage my nvme drive?

You and me both, lol

OUCH. It can get expensive with 2 systems I may just have to go the FreeNAS route I guess as much as I like Unraid. Wish they would give us a break

Hello gents, new Unraid user and love it so far. I already purchased a Pro license and I was wondering if you can offer some kind of discount if I purchase a second Pro license please as I am building a second system more for testing and as a backup Unraid Any coupon, discount will be awesome please. I hope you can help?

You are on Unraid forum and not the Unifi This is where you need to be https://community.ui.com/questions

I hear you brother. But something interesting. Just installed the BETA Version: 6.9.0-beta22 just for the hell of it since I have a second Unraid to play around and it has been SOLID? Same hardware. Something changed in this beta to give me different results. Is doing a parity re-build now and is solid, no errors, nothing. I did order an LSI 2008 just like my other Unraid but meanwhile I am playing with this

Make sure to get the right / latest firmware installed 20X.X.X.X07.X as that was a problem for me and thanks to Johnnie I was able to rectify it. I just to had to do the firmware update myself and if you are not a computer guy it may be a challenge Boot my Supermicro board in DOS was a nightmare root@NAS-UNRAID:~# dmesg |grep SAS [ 27.198857] mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00) [ 27.269950] scsi host7: Fusion MPT SAS Host root@NAS-UNRAID:~#

I am working on my second Unraid box and I do have some limitations. I know I seen many posts advising against the Marvell chipset. Does anyone runs the SuperMicro AOC-SASLP-MV8 card and is it stable and error free in Unraid? Looks like I may have some issue with my Marvell card. I need to use this SuperMicro AOC-SASLP-MV8 card as is the only one that fits my PCI-E 4x slot Would a 8X card such as LSI SAS9200-8i work in a 4X motherboard slot? I know it will physically fit as the back of the 4X slot is open and I am sure the pcie lanes speed will be lower. [ 483.828437] mvsas 0000:02:00.0: mvsas prep failed[-16]! [ 483.828442] mvsas 0000:02:00.0: mvsas exec failed[-16]! [ 483.828444] sas: lldd_execute_task returned: -16 [ 504.340768] sas: Enter sas_scsi_recover_host busy: 22 failed: 22 [ 504.340777] sas: trying to find task 0x00000000b3c713e9 [ 504.340778] sas: sas_scsi_find_task: aborting task 0x00000000b3c713e9 [ 524.810422] drivers/scsi/mvsas/mv_sas.c 1330:TMF task[1] timeout. [ 524.810426] drivers/scsi/mvsas/mv_sas.c 1555:mvs_abort_task:rc= 5 [ 524.810430] sas: sas_scsi_find_task: querying task 0x00000000b3c713e9 [ 545.294757] drivers/scsi/mvsas/mv_sas.c 1330:TMF task[80] timeout. [ 545.294761] drivers/scsi/mvsas/mv_sas.c 1477:mvs_query_task:rc= 5 [ 545.294764] sas: sas_scsi_find_task: task 0x00000000b3c713e9 failed to abort [ 545.294765] sas: task 0x00000000b3c713e9 is not at LU: I_T recover [ 545.294767] sas: I_T nexus reset for dev 5000cca03ba7fe85 [ 547.535918] drivers/scsi/mvsas/mv_sas.c 1434:mvs_I_T_nexus_reset for device[4]:rc= 0 [ 547.535930] sas: task done but aborted [ 547.535933] sas: task done but aborted [ 547.535936] sas: task done but aborted [ 547.535938] sas: task done but aborted [ 547.535941] sas: task done but aborted [ 547.535944] sas: task done but aborted [ 547.535946] sas: task done but aborted [ 547.535949] sas: task done but aborted [ 547.535952] sas: task done but aborted [ 547.535954] sas: task done but aborted [ 547.535957] sas: task done but aborted [ 547.535960] sas: task done but aborted [ 547.535961] sas: task done but aborted [ 547.535963] sas: task done but aborted [ 547.535966] sas: task done but aborted [ 547.535968] sas: task done but aborted [ 547.535970] sas: task done but aborted [ 547.535972] sas: task done but aborted [ 547.535975] sas: task done but aborted [ 547.535977] sas: task done but aborted [ 547.535979] sas: task done but aborted [ 607.576775] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 607.576783] rcu: 1-...0: (0 ticks this GP) idle=e56/1/0x4000000000000000 softirq=59561/59561 fqs=15000 [ 607.576784] rcu: (detected by 2, t=60002 jiffies, g=143457, q=8030) [ 607.576789] Sending NMI from CPU 2 to CPUs 1: [ 607.577792] NMI backtrace for cpu 1 [ 607.577793] CPU: 1 PID: 1352 Comm: scsi_eh_5 Tainted: G O 4.19.107-Unraid #1 [ 607.577794] Hardware name: Supermicro Super Server/A2SDi-4C-HLN4F, BIOS 1.2 11/05/2019 [ 607.577795] RIP: 0010:mvs_slot_complete+0xe/0x4b0 [mvsas] [ 607.577796] Code: ff ff 48 8b 4c 24 08 65 48 33 0c 25 28 00 00 00 74 05 e8 bf 68 e1 e0 48 83 c4 10 c3 89 f0 41 57 49 89 ff 25 ff 0f 00 00 41 56 <41> 89 d6 41 55 41 54 55 53 89 c3 48 6b fb 58 48 83 ec 18 89 44 24 [ 607.577797] RSP: 0018:ffffc90006447d30 EFLAGS: 00000002 [ 607.577798] RAX: 0000000000000001 RBX: 00000000000003a5 RCX: 0000000000000007 [ 607.577799] RDX: 0000000000000000 RSI: 0000000000810001 RDI: ffff889035b40000 [ 607.577799] RBP: ffff889035b40000 R08: 0000000000000003 R09: 0000000000018d00 [ 607.577800] R10: 0000000000000000 R11: 000000000000003c R12: ffff889035c24e00 [ 607.577801] R13: 0000000000000000 R14: 0000000000000000 R15: ffff889035b40000 [ 607.577802] FS: 0000000000000000(0000) GS:ffff88903fa80000(0000) knlGS:0000000000000000 [ 607.577802] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 607.577803] CR2: 0000148a2cc14718 CR3: 0000000001e0a000 CR4: 00000000003406e0 [ 607.577803] Call Trace: [ 607.577804] mvs_int_rx+0x85/0xf1 [mvsas] [ 607.577805] mvs_do_release_task+0x32/0xd1 [mvsas] [ 607.577805] mvs_release_task+0xc4/0xe6 [mvsas] [ 607.577806] mvs_I_T_nexus_reset+0xa2/0xbb [mvsas] [ 607.577806] sas_scsi_recover_host+0x61b/0xaf5 [libsas] [ 607.577807] scsi_error_handler+0x9a/0x37e [ 607.577807] ? scsi_eh_get_sense+0xd7/0xd7 [ 607.577808] kthread+0x10c/0x114 [ 607.577808] ? kthread_park+0x89/0x89 [ 607.577809] ret_from_fork+0x35/0x40 [ 787.554002] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 787.554009] rcu: 1-...0: (0 ticks this GP) idle=e56/1/0x4000000000000000 softirq=59561/59561 fqs=60001 [ 787.554010] rcu: (detected by 0, t=240007 jiffies, g=143457, q=30242) [ 787.554014] Sending NMI from CPU 0 to CPUs 1: [ 787.555018] NMI backtrace for cpu 1 [ 787.555019] CPU: 1 PID: 1352 Comm: scsi_eh_5 Tainted: G O 4.19.107-Unraid #1 [ 787.555019] Hardware name: Supermicro Super Server/A2SDi-4C-HLN4F, BIOS 1.2 11/05/2019 [ 787.555020] RIP: 0010:mvs_slot_complete+0x16/0x4b0 [mvsas] [ 787.555022] Code: 48 33 0c 25 28 00 00 00 74 05 e8 bf 68 e1 e0 48 83 c4 10 c3 89 f0 41 57 49 89 ff 25 ff 0f 00 00 41 56 41 89 d6 41 55 41 54 55 <53> 89 c3 48 6b fb 58 48 83 ec 18 89 44 24 10 83 c8 ff 89 74 24 14 [ 787.555022] RSP: 0018:ffffc90006447d18 EFLAGS: 00000002 [ 787.555023] RAX: 0000000000000002 RBX: 0000000000000247 RCX: 0000000000000007 [ 787.555024] RDX: 0000000000000000 RSI: 0000000000810002 RDI: ffff889035b40000 [ 787.555025] RBP: ffff889035b40000 R08: 0000000000000003 R09: 0000000000018d00 [ 787.555025] R10: 0000000000000000 R11: 000000000000003c R12: ffff889035c24e00 [ 787.555026] R13: 0000000000000000 R14: 0000000000000000 R15: ffff889035b40000 [ 787.555027] FS: 0000000000000000(0000) GS:ffff88903fa80000(0000) knlGS:0000000000000000 [ 787.555028] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 787.555028] CR2: 0000148a2cc14718 CR3: 0000000001e0a000 CR4: 00000000003406e0 [ 787.555029] Call Trace: [ 787.555029] mvs_int_rx+0x85/0xf1 [mvsas] [ 787.555030] mvs_do_release_task+0x32/0xd1 [mvsas] [ 787.555030] mvs_release_task+0xc4/0xe6 [mvsas] [ 787.555031] mvs_I_T_nexus_reset+0xa2/0xbb [mvsas] [ 787.555031] sas_scsi_recover_host+0x61b/0xaf5 [libsas] [ 787.555032] scsi_error_handler+0x9a/0x37e [ 787.555032] ? scsi_eh_get_sense+0xd7/0xd7 [ 787.555033] kthread+0x10c/0x114 [ 787.555033] ? kthread_park+0x89/0x89 [ 787.555034] ret_from_fork+0x35/0x40 [ 967.557621] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 967.557629] rcu: 1-...0: (0 ticks this GP) idle=e56/1/0x4000000000000000 softirq=59561/59561 fqs=105002 [ 967.557630] rcu: (detected by 0, t=420012 jiffies, g=143457, q=53631) [ 967.557634] Sending NMI from CPU 0 to CPUs 1: [ 967.558637] NMI backtrace for cpu 1 [ 967.558638] CPU: 1 PID: 1352 Comm: scsi_eh_5 Tainted: G O 4.19.107-Unraid #1 [ 967.558639] Hardware name: Supermicro Super Server/A2SDi-4C-HLN4F, BIOS 1.2 11/05/2019 [ 967.558640] RIP: 0010:mvs_int_rx+0x89/0xf1 [mvsas] [ 967.558641] Code: 81 e3 ff 03 00 00 8d 43 01 8b 34 82 41 89 f7 41 81 e7 00 00 01 00 74 12 31 d2 48 89 ef 89 74 24 04 e8 cf f8 ff ff 8b 74 24 04 <0f> ba e6 13 72 2d 0f ba e6 11 73 11 45 85 ff 75 ba 31 d2 48 89 ef [ 967.558642] RSP: 0018:ffffc90006447d48 EFLAGS: 00000092 [ 967.558643] RAX: 00000000ffffffff RBX: 0000000000000236 RCX: 0000000000000007 [ 967.558644] RDX: ffff889035b40210 RSI: 0000000000810006 RDI: 0000000000000210 [ 967.558644] RBP: ffff889035b40000 R08: 0000000000000003 R09: 0000000000018d00 [ 967.558645] R10: 0000000000000000 R11: 000000000000003c R12: ffff889035c24e00 [ 967.558646] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000010000 [ 967.558647] FS: 0000000000000000(0000) GS:ffff88903fa80000(0000) knlGS:0000000000000000 [ 967.558647] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 967.558648] CR2: 0000148a2cc14718 CR3: 0000000001e0a000 CR4: 00000000003406e0 [ 967.558648] Call Trace: [ 967.558649] mvs_do_release_task+0x32/0xd1 [mvsas] [ 967.558649] mvs_release_task+0xc4/0xe6 [mvsas] [ 967.558650] mvs_I_T_nexus_reset+0xa2/0xbb [mvsas] [ 967.558650] sas_scsi_recover_host+0x61b/0xaf5 [libsas] [ 967.558651] scsi_error_handler+0x9a/0x37e [ 967.558651] ? scsi_eh_get_sense+0xd7/0xd7 [ 967.558652] kthread+0x10c/0x114 [ 967.558652] ? kthread_park+0x89/0x89 [ 967.558653] ret_from_fork+0x35/0x40 [ 1147.529495] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 1147.529502] rcu: 1-...0: (0 ticks this GP) idle=e56/1/0x4000000000000000 softirq=59561/59561 fqs=150000 [ 1147.529503] rcu: (detected by 3, t=600017 jiffies, g=143457, q=76303) [ 1147.529507] Sending NMI from CPU 3 to CPUs 1: [ 1147.530510] NMI backtrace for cpu 1 [ 1147.530511] CPU: 1 PID: 1352 Comm: scsi_eh_5 Tainted: G O 4.19.107-Unraid #1 [ 1147.530512] Hardware name: Supermicro Super Server/A2SDi-4C-HLN4F, BIOS 1.2 11/05/2019 [ 1147.530513] RIP: 0010:mvs_slot_complete+0x37/0x4b0 [mvsas] [ 1147.530514] Code: 56 41 89 d6 41 55 41 54 55 53 89 c3 48 6b fb 58 48 83 ec 18 89 44 24 10 83 c8 ff 89 74 24 14 49 8d 14 3f 48 8b aa 08 fd 00 00 <48> 89 54 24 08 48 85 ed 0f 84 5c 04 00 00 48 83 bd e8 00 00 00 00 [ 1147.530515] RSP: 0018:ffffc90006447cf8 EFLAGS: 00000086 [ 1147.530516] RAX: 00000000ffffffff RBX: 0000000000000003 RCX: 0000000000000007 [ 1147.530517] RDX: ffff889035b40108 RSI: 0000000000810003 RDI: 0000000000000108 [ 1147.530518] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000018d00 [ 1147.530518] R10: 0000000000000000 R11: 000000000000003c R12: ffff889035c24e00 [ 1147.530519] R13: 0000000000000000 R14: 0000000000000000 R15: ffff889035b40000 [ 1147.530520] FS: 0000000000000000(0000) GS:ffff88903fa80000(0000) knlGS:0000000000000000 [ 1147.530520] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1147.530521] CR2: 0000148a2cc14718 CR3: 0000000001e0a000 CR4: 00000000003406e0 [ 1147.530522] Call Trace: [ 1147.530522] mvs_int_rx+0x85/0xf1 [mvsas] [ 1147.530523] mvs_do_release_task+0x32/0xd1 [mvsas] [ 1147.530523] mvs_release_task+0xc4/0xe6 [mvsas] [ 1147.530524] mvs_I_T_nexus_reset+0xa2/0xbb [mvsas] [ 1147.530524] sas_scsi_recover_host+0x61b/0xaf5 [libsas] [ 1147.530525] scsi_error_handler+0x9a/0x37e [ 1147.530525] ? scsi_eh_get_sense+0xd7/0xd7 [ 1147.530526] kthread+0x10c/0x114 [ 1147.530526] ? kthread_park+0x89/0x89 [ 1147.530527] ret_from_fork+0x35/0x40 root@NAS-UNRAID-2:~# root@NAS-UNRAID-2:~#

Looks like I may have the same issue with my Marvell card. I need to use this SuperMicro AOC-SASLP-MV8 card as is the only one that fits my PCI-E 4x slot Would a 8X card such as LSI SAS9200-8i work in a 4X motherboard slot? I know it will physically fit as the back of the 4X slot is open and I am sure the pcie lanes speed will be lower. [ 160.099715] mdcmd (40): check correct [ 160.099757] md: recovery thread: recon P ... [ 483.828437] mvsas 0000:02:00.0: mvsas prep failed[-16]! [ 483.828442] mvsas 0000:02:00.0: mvsas exec failed[-16]! [ 483.828444] sas: lldd_execute_task returned: -16 [ 504.340768] sas: Enter sas_scsi_recover_host busy: 22 failed: 22 [ 504.340777] sas: trying to find task 0x00000000b3c713e9 [ 504.340778] sas: sas_scsi_find_task: aborting task 0x00000000b3c713e9 root@NAS-UNRAID-2:~#

I am happy to inform you that I have a STABLE system with all parity done and no drive errors anymore. Is not just about keeping it healthy. THANKS Johnnie for all the help and guidance Sir. The firmware advise did the trick for sure. I redid all my cables as well just in case

Did you try to mount it at the command line? I formatted my USB drive with HFS+ , copy all my data from my Mac and I was able to mount that in unraid in read mode and copy all my data. It worked perfect.

Hey Tamalero there is hope. I had a rocky start as well and with the advise from Johnie and those guys I am on the right path. Just got the license myself few days ago and my system works perfectly. There is a reason they recommend specific hardware, steps and firmware version so our systems can be stable and reliable. I am at point now where I am that close to claim victory There is hope brother

Thank you Sir. I am now the proud owner of 20.00.07.00 firmware as suggested. I just stared the parity for the second drive. Let's see if I still get the errors. root@NAS-UNRAID:~# dmesg |grep SAS [ 27.949443] mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00) [ 27.949562] scsi host7: Fusion MPT SAS Host