Skipdog

Hi JorgeB, Yes IPMI works great. I went ahead and updated BIOS to 2.0 which i think reset BIOS completely. I went in and played with the legacy USB support settings. Legacy USB was already enabled and when I disable it -- it won't boot UNRAID USB. Not a huge deal- it seems like the X11SDV-4C-TLN2F has issues with USB lower power devices like keyboards/mice and UNRAID. Oh, and yes I did try back of motherboard USB, and i plugged in front USB cable and tried those. They all do the same thing. I appreciate your help! Skip

Ah- just figured the slow boot issue was indeed tied to the network interfaces being port up but down. Bootup times are now restored and good! This does leave the USB issue which isn't critical at all. I do see that UNRAID is seeing the low speed keyboard connected. Skip edit: Bus 001 Device 003 Port 1-2 ID 04f2:1125 Chicony Electronics Co., Ltd Asus Keyboard

UNRAID Version: 6.12.6 Hi there. I upgraded my Supermicro CS836 X9 based system to a Supermicro MBD-X11SDV-4C-TLN2F-O Xeon D-2123IT. A few problems i'm troubleshooting: 1) UNRAID boot stalls at "Triggering udev events: /sbin/udevadm trigger --action=change" for a long period of time. If I wait long enough it seems to boot and operate OK. I tried a new clean UNRAID USB and it boots up immediately and doesn't get stuck at this point. Do I need to do something in UNRAID to rediscover the new hardware/drivers? I also notice that when it finally does bootup IPv4 Address says "not set" but the webgui does work with the static IP that is assigned. 2) The USB port on the back of the MBD-X11SDV used for keyboard doesn't seem to work once UNRAID is booting/booted. Could this be related to the hardware change and #1? Seems maybe driver related? I dont think i want to rebuild the licensed USB key but open to suggestions to fix. Thanks, Skip

UNRAID V. 6.12.6 Supermicro X9DRH with E5-2670 and about 12 drives in array with a cache disk. Installed new container HOOBS and couldn't get homekit to connect to network set in bridge mode. Changed it to custom bridge and immediately fixed the homekit connection issue. However overnight system locked up hard. System locks up if turned on for a period of time. Disabling the custom bridge did seem to allow the system to run normally. Docker setting is Maclan so I will try ipvlan but i'm hesitant to do this being all my other functions are completely normal. Attaching diag. Skip diagnostics-20231203-1416.zip

UNRAID Ver: 6.9.1 PreClear ver: 2021.01.03 Server type: Supermicro CS836, LSI SAS2308 controller Noticed in the fix notes for 2020:12-22 Fix: script failing during drive zeroing I've purchased several brand new external WD 8TB drives. Each of the drives runs through pre-reads just fine. Then toward the very end of zeroing it reports a failure. I've tried different slots and the behavior is the same. I've pulled the drive out of the server and put it back into the original enclosure to run pre-clear on another system. Should I generate a full diag next time or attach the pre-clear log. I am wondering if i'm hitting the bug behavior or just a hardware type issue causing the pre-clear bug. Skip edit: attached diag- but syslog looks like it is missing data tower-diagnostics-20210316-1218.zip

System is a Supermicro X9DRH with Dual E5-2670v2. Ram=256gig. The server has been super stable with 6.8 with uptimes reaching 150+ days. I could not leave well enough alone and upgraded to 6.9 RC2. I upgraded in part to get the new graphics plugin working with my Quadro card. I've enabled syslog now and i'm dumping them to disk. Is there any other diagnostics I can turn on to catch another potential crash? Parity check auto-ran and found roughly 8000 errors which is expected since it shutdown dirty. I see no errors on the drives currently. Thanks, Skip

Walter- Epic fail on my part! Thank you! I had thought it installed all of the tools by default! Skip

Apologies i did search for a solution! I've installed and reinstalled the nerd pack but when I attempt to execute iperf3 it doesn't seem to find it. Looked in various directories. What rookie mistake am I making? Skip

Hi there. I am trying to use Krusader to copy between local UNRAID volume and an SMB network connection. The SMB connects fine. When I go to copy files/directories I get the error "The file or folder smb://[email protected]/backup/folder/subfolder/.@_thumb does not exist. Any ideas what it is unhappy about? Skip

talked to a friend who has the same drives in an enterprise QNAP. He started to have the same problem at the same time. We are wondering if something in the Linux kernel/driver set was updated that is causing issues with the Seagate Constellation series. Also checking firmware to see if that has any impact.

Yes i moved the Seagates to another supermicro that effectively uses the onboard SATA. they are producing the errors in the text I pasted. The drives aren't throwing bad sectors - but maybe they are mechanical problems in nature.

I should also add i've got 7x WDC_WD80EMAZ that have given me zero problems since they were installed. On the spare supermicro, they were indeed going into the onboard SATA. There are no HBAs installed in that server. The primary supermicro is using SAS 9207-8i type card.

Still struggling with this as just the Seagate 8TB EXOS drives continue to have problems. I have another supermicro and i'm seeing these Seagate drives also produce problems in that. Completely different chassis, HBA, cables. My system failed to rebuild parity on one of the drives just now, and then after a reboot, the drive that did rebuild correctly decided to drop out. I didn't reboot this time and captured diags. Here is snippet of the logs from the drive when it happened: Aug 12 10:43:12 Tower kernel: sd 7:0:7:0: [sdk] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Aug 12 10:43:12 Tower kernel: sd 7:0:7:0: [sdk] 4096-byte physical blocks Aug 12 10:43:12 Tower kernel: sd 7:0:7:0: [sdk] Write Protect is off Aug 12 10:43:12 Tower kernel: sd 7:0:7:0: [sdk] Mode Sense: 7f 00 10 08 Aug 12 10:43:12 Tower kernel: sd 7:0:7:0: [sdk] Write cache: enabled, read cache: enabled, supports DPO and FUA Aug 12 10:43:12 Tower kernel: sdk: sdk1 Aug 12 10:43:12 Tower kernel: sd 7:0:7:0: [sdk] Attached SCSI disk Aug 12 10:43:12 Tower kernel: BTRFS: device fsid e2a97d07-5b8c-4f40-9733-01c1060204f8 devid 1 transid 387385 /dev/sdk1 Aug 12 10:43:38 Tower emhttpd: ST8000NM0055-1RM112_ZA105CRR (sdk) 512 15628053168 Aug 12 10:43:38 Tower kernel: mdcmd (1): import 0 sdk 64 7814026532 0 ST8000NM0055-1RM112_ZA105CRR Aug 12 10:43:38 Tower kernel: md: import disk0: (sdk) ST8000NM0055-1RM112_ZA105CRR size: 7814026532 Aug 12 10:43:41 Tower emhttpd: shcmd (25): /usr/local/sbin/set_ncq sdk 1 Aug 12 10:43:41 Tower root: set_ncq: setting sdk queue_depth to 1 Aug 12 10:43:41 Tower emhttpd: shcmd (26): echo 128 > /sys/block/sdk/queue/nr_requests Aug 12 10:46:54 Tower kernel: sd 7:0:7:0: [sdk] tag#7 CDB: opcode=0x8a 8a 00 00 00 00 00 01 51 c2 c0 00 00 00 40 00 00 Aug 12 10:46:57 Tower kernel: sd 7:0:7:0: [sdk] Synchronizing SCSI cache Aug 12 10:46:58 Tower kernel: sd 7:0:7:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Aug 12 10:46:58 Tower kernel: sd 7:0:7:0: [sdk] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 01 51 c2 c0 00 00 00 40 00 00 Aug 12 10:46:58 Tower kernel: print_req_error: I/O error, dev sdk, sector 22135488 Aug 12 10:46:58 Tower kernel: sd 7:0:7:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Aug 12 10:46:58 Tower kernel: sd 7:0:7:0: [sdk] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 70 27 f9 48 00 00 00 08 00 00 Aug 12 10:46:58 Tower kernel: print_req_error: I/O error, dev sdk, sector 1881667912 Aug 12 10:46:58 Tower kernel: sd 7:0:7:0: [sdk] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Skip tower-diagnostics-20190812-1452.zip

OK so pre-clear on two drives failed during different times. One looks like during read. The other i'm not sure about. It looks like I/O errors. Drives are in sleds in supermicro. Diags uploaded. Skip tower-diagnostics-20190801-1256.zip

OK, so I think yes I made some mistakes on this one. When something like this happens should I generate diag, and then power down completely? Post reboot see what is coming up? When this happened I did notice that disks were spun down. I've got two disks pre-clearing right now. Thanks for the pointer to UD.