Kosti Posted December 22, 2021 Share Posted December 22, 2021 (edited) Hey All Problems still persist with my new build - I just follow some tube videos to setup a new unraid My SPECS CPU - Intel 11th Gen Core i5-11400 Motherboard - MSI MAG B560M Mortar Wi-Fi LGA 1200 mATX Motherboard RAM - G.Skill 2x16G F4-3200C16D-32GIS PC4-25600 DDR4 3200 Mhz DISKS 2 X 1TB 970 EVO ; 3 x 12TB Elemental Drives, some 4TB which will be removed soon I started a new pre clear last night on a single drive connected via USB3 and today no records of this being completed or finished or even started? I see the following in the logs below on repeat since 4AM, but I started the pre clear much earlier so I suspect the server rebooted? Dec 23 09:32:13 Medusa kernel: Bluetooth: hci0: Reading Intel version information failed (-22) Dec 23 09:32:13 Medusa kernel: Bluetooth: hci0: Intel Read version failed (-22) Dec 23 09:32:13 Medusa kernel: Bluetooth: hci0: Intel reset sent to retry FW download Dec 23 09:32:13 Medusa kernel: usb 1-2: USB disconnect, device number 114 Dec 23 09:32:13 Medusa kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot 19 ep 4 with no TDs queued? Dec 23 09:32:13 Medusa kernel: xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr Dec 23 09:32:13 Medusa kernel: xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is pending. Dec 23 09:32:13 Medusa kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. Dec 23 09:32:13 Medusa kernel: usb 1-2: new full-speed USB device number 115 using xhci_hcd Dec 23 09:32:14 Medusa kernel: Bluetooth: hci0: Reading Intel version information failed (-22) Dec 23 09:32:14 Medusa kernel: Bluetooth: hci0: Intel Read version failed (-22) Dec 23 09:32:14 Medusa kernel: Bluetooth: hci0: Intel reset sent to retry FW download Dec 23 09:32:14 Medusa kernel: usb 1-2: USB disconnect, device number 115 Not sure how to fix this and not sure if this is causing my system to report these errors? Do I need to add options in my kernel parameters? This is a new fresh build and I first encounter issues due to bad ram, replaced this and now the above Any guidance on what I can do to make sure my system is stable for unraid use? PEACE Kosti Edited December 25, 2021 by Kosti changed heading and added details Quote Link to comment
SimonF Posted December 22, 2021 Share Posted December 22, 2021 6 minutes ago, Kosti said: Any guidance on what I can do to make sure my system is stable for unraid use? Do you use bluetooth? mkdir /boot/config/modprobe.d/ echo -e 'blacklist btusb\nblacklist bluetooth' > /boot/config/modprobe.d/bluetooth.conf and reboot will disable BT drivers 1 Quote Link to comment
Kosti Posted December 24, 2021 Author Share Posted December 24, 2021 Hi @SimonF Thanks for the reply, no I do not use BT at all, this is a new build But more issues and lost the pre clear drive Dec 24 11:06:12 Medusa kernel: Bluetooth: hci0: Reading Intel version information failed (-22) Dec 24 11:06:12 Medusa kernel: Bluetooth: hci0: Intel Read version failed (-22) Dec 24 11:06:12 Medusa kernel: Bluetooth: hci0: Intel reset sent to retry FW download Dec 24 11:06:12 Medusa kernel: usb 1-2: USB disconnect, device number 32 Dec 24 11:06:17 Medusa kernel: xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command. Dec 24 11:06:17 Medusa kernel: xhci_hcd 0000:00:14.0: USBSTS: Dec 24 11:06:17 Medusa kernel: xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead Dec 24 11:06:17 Medusa kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up Dec 24 11:06:17 Medusa kernel: usb 2-2: USB disconnect, device number 2 Dec 24 11:06:17 Medusa kernel: usb 2-2.1: USB disconnect, device number 3 Dec 24 11:06:17 Medusa kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=5s Dec 24 11:06:17 Medusa kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 02 7a 49 e0 00 00 00 08 00 00 00 Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sda, sector 10641596416 op 0x0:(READ) flags 0x80700 phys_seg 220 prio class 0 Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sda, sector 10641598464 op 0x0:(READ) flags 0x80700 phys_seg 199 prio class 0 Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sda, sector 23437705215 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sda, sector 1504556004 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sda, sector 20592783 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sda, sector 10641596416 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Dec 24 11:06:17 Medusa kernel: Buffer I/O error on dev sda, logical block 1330199552, async page read Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sda, sector 3068526668 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 3 Dec 24 11:06:17 Medusa kernel: usb 1-3: USB disconnect, device number 3 Dec 24 11:06:17 Medusa kernel: usb 1-7: USB disconnect, device number 4 Dec 24 11:06:17 Medusa rc.diskinfo[9889]: SIGHUP received, forcing refresh of disks info. Dec 24 11:06:17 Medusa kernel: usb 1-8: USB disconnect, device number 5 Dec 24 11:06:17 Medusa acpid: input device has been disconnected, fd 5 Dec 24 11:06:17 Medusa emhttpd: shcmd (89378): rmmod md-mod Dec 24 11:06:17 Medusa kernel: md: unRAID driver removed Dec 24 11:06:17 Medusa emhttpd: shcmd (89379): modprobe md-mod super=/boot/config/super.dat Dec 24 11:06:17 Medusa kernel: md: unRAID driver 2.9.17 installed Dec 24 11:06:17 Medusa kernel: sd 1:0:0:0: [sdb] tag#0 access beyond end of device Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sdb, sector 590696 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Dec 24 11:06:17 Medusa kernel: sd 1:0:0:0: [sdb] tag#0 access beyond end of device Dec 24 11:06:17 Medusa kernel: blk_update_request: I/O error, dev sdb, sector 590696 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Dec 24 11:06:17 Medusa kernel: read_file: read error 5 Dec 24 11:06:17 Medusa kernel: md: could not read superblock from /boot/config/super.dat Dec 24 11:06:17 Medusa kernel: md: initializing superblock Dec 24 11:06:17 Medusa emhttpd: Unregistered - flash device blacklisted (EBLACKLISTED2) Dec 24 11:06:17 Medusa kernel: usb 1-11: USB disconnect, device number 6 Dec 24 11:06:17 Medusa kernel: usb 1-11.2: USB disconnect, device number 8 Dec 24 11:06:17 Medusa kernel: Buffer I/O error on dev sdb1, logical block 1, lost async page write Dec 24 11:06:17 Medusa kernel: Buffer I/O error on dev sdb1, logical block 536651, lost async page write Dec 24 11:06:17 Medusa kernel: Buffer I/O error on dev sdb1, logical block 551626, lost async page write Dec 24 11:06:17 Medusa kernel: usb 1-14: USB disconnect, device number 7 Dec 24 11:06:17 Medusa emhttpd: Device inventory: Dec 24 11:06:17 Medusa emhttpd: Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M319641V (nvme1n1) 512 1953525168 Dec 24 11:06:17 Medusa emhttpd: ST4000DM000-2AE166_WDH0PS6T (sdd) 512 7814037168 Dec 24 11:06:17 Medusa emhttpd: TOSHIBA_MG04ACA400N_X9PUKDAEFSYC (sdc) 512 7814037168 Dec 24 11:06:17 Medusa emhttpd: Samsung_SSD_970_EVO_Plus_1TB_S6P7NG0R727537X (nvme0n1) 512 1953525168 Dec 24 11:06:17 Medusa emhttpd: Error: (sdb) not present Dec 24 11:06:17 Medusa kernel: mdcmd (1): import 0 Dec 24 11:06:17 Medusa kernel: mdcmd (2): import 1 Dec 24 11:06:17 Medusa kernel: mdcmd (3): import 2 Dec 24 11:06:17 Medusa kernel: mdcmd (4): import 3 Dec 24 11:06:17 Medusa kernel: mdcmd (5): import 4 Dec 24 11:06:17 Medusa kernel: mdcmd (6): import 5 Dec 24 11:06:17 Medusa kernel: mdcmd (7): import 6 Dec 24 11:06:17 Medusa kernel: mdcmd (8): import 7 Dec 24 11:06:17 Medusa kernel: mdcmd (9): import 8 Dec 24 11:06:17 Medusa kernel: mdcmd (10): import 9 Dec 24 11:06:17 Medusa kernel: mdcmd (11): import 10 Dec 24 11:06:17 Medusa kernel: mdcmd (12): import 11 Dec 24 11:06:17 Medusa kernel: mdcmd (13): import 12 Dec 24 11:06:17 Medusa kernel: mdcmd (14): import 13 Dec 24 11:06:17 Medusa kernel: mdcmd (15): import 14 Dec 24 11:06:17 Medusa kernel: mdcmd (16): import 15 Dec 24 11:06:17 Medusa kernel: mdcmd (17): import 16 Dec 24 11:06:17 Medusa kernel: mdcmd (18): import 17 Dec 24 11:06:17 Medusa kernel: mdcmd (19): import 18 Dec 24 11:06:17 Medusa kernel: mdcmd (20): import 19 Dec 24 11:06:17 Medusa kernel: mdcmd (21): import 20 Dec 24 11:06:17 Medusa kernel: mdcmd (22): import 21 Dec 24 11:06:17 Medusa kernel: mdcmd (23): import 22 Dec 24 11:06:17 Medusa kernel: mdcmd (24): import 23 Dec 24 11:06:17 Medusa kernel: mdcmd (25): import 24 Dec 24 11:06:17 Medusa kernel: mdcmd (26): import 25 Dec 24 11:06:17 Medusa kernel: mdcmd (27): import 26 Dec 24 11:06:17 Medusa kernel: mdcmd (28): import 27 Dec 24 11:06:17 Medusa kernel: mdcmd (29): import 28 Dec 24 11:06:17 Medusa kernel: mdcmd (30): import 29 Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29352) failed Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29353) failed Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29354) failed Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29355) failed Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29356) failed Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29357) failed Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29358) failed Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29359) failed Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29360) failed Dec 24 11:06:20 Medusa kernel: FAT-fs (sdb1): Directory bread(block 29361) failed Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd - read 5448497364992 of 12000105070592 (6551607705600). Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: elapsed time - 7:54:07 Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd command failed, exit code [1]. Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2588975+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2588974+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5429472002048 bytes (5.4 TB, 4.9 TiB) copied, 28329.1 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2589991+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2589990+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5431602708480 bytes (5.4 TB, 4.9 TiB) copied, 28341.4 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2590957+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2590956+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5433628557312 bytes (5.4 TB, 4.9 TiB) copied, 28353.6 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2591951+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2591950+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5435713126400 bytes (5.4 TB, 4.9 TiB) copied, 28366 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2592951+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2592950+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5437810278400 bytes (5.4 TB, 4.9 TiB) copied, 28378.3 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2593987+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2593986+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5439982927872 bytes (5.4 TB, 4.9 TiB) copied, 28390.5 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2595041+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2595040+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5442193326080 bytes (5.4 TB, 4.9 TiB) copied, 28402.9 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2596064+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2596063+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5444338712576 bytes (5.4 TB, 5.0 TiB) copied, 28415.3 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2597060+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2597059+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5446427475968 bytes (5.4 TB, 5.0 TiB) copied, 28427.6 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: dd: error reading '/dev/sda': Input/output error Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2598045+0 records in Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 2598045+0 records out Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: dd output: 5448495267840 bytes (5.4 TB, 5.0 TiB) copied, 28445 s, 192 MB/s Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: Post-Read: post-read verification failed! Dec 24 11:06:29 Medusa preclear_disk_3551483156325046[20546]: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 1780: /boot/config/plugins/preclear.disk/4312537425768.sreport: No such file or directory Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: Error: Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: Reallocated_Sector_Ct 0 - Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: Power_On_Hours 38 - Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: Temperature_Celsius 33 - Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: Reallocated_Event_Count 0 - Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: Current_Pending_Sector 0 - Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: Offline_Uncorrectable 0 - Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: S.M.A.R.T.: UDMA_CRC_Error_Count 0 - Dec 24 11:06:30 Medusa preclear_disk_3551483156325046[20546]: error encountered, exiting... Something is going on and I do not think unraid likes this motherboard? Any ideas where to start ? Quote Link to comment
Squid Posted December 24, 2021 Share Posted December 24, 2021 Try a different USB port, ideally USB2 for the boot flash. If problems continue, then try the Flash Remount plugin Right now the only recourse is a reboot (and a parity check will ensue, but it'll be safe to cancel) 1 Quote Link to comment
Kosti Posted December 25, 2021 Author Share Posted December 25, 2021 (edited) Thanks Mr @Squid I do find this so strange while using a HP Gen8 fully loaded never had one issue, moved to latest GEN hardware and nothing but issues Same USB Flash drive, prob only seen s a few reboots at best, as for using a USB2 I will try and find one and run a unregistered version before I try and tie my licence to another flash stick I I'm using an onboard USB2 port connector which is USB2 as shown in the attachment using a USB3 Flash that was used flawlessly in the HP like I mentioned bugger all use? I've never seen so much hardware issues with virtually brand new hardware, just think the unraid OS isn't compatible with what I have put together? Very frustrating trying to get this to play nice, but will now try and find a USB2 Flash drive for use on the onboard USB2 instead of the current one I have my license on PEACE Kosti BTW - Merry XMAS folks! EDIT - is there a way to test the USB flash drive in unraid? Edited December 25, 2021 by Kosti Quote Link to comment
Kosti Posted December 25, 2021 Author Share Posted December 25, 2021 On 12/23/2021 at 9:56 AM, SimonF said: Do you use bluetooth? mkdir /boot/config/modprobe.d/ echo -e 'blacklist btusb\nblacklist bluetooth' > /boot/config/modprobe.d/bluetooth.conf and reboot will disable BT drivers I have added in this to the USB boot and will try and run pre clear again for the 3rd time and see what happens. Logs look good at the moment no more BT errors or USB issues yet? Dec 25 19:01:08 Medusa nmbd[9746]: ***** Dec 25 19:01:10 Medusa webGUI: Successful login user root from 192.168.1.134 Dec 25 19:06:11 Medusa ntpd[1964]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Not sure about the clock issues, but will see how my Google fu goes to fix it PEACE Kosti Quote Link to comment
SimonF Posted December 25, 2021 Share Posted December 25, 2021 1 hour ago, Kosti said: Dec 25 19:06:11 Medusa ntpd[1964]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized I always get this after boot, nothing to worry about. 1 Quote Link to comment
Kosti Posted December 26, 2021 Author Share Posted December 26, 2021 update So far by adding this mkdir /boot/config/modprobe.d/ echo -e 'blacklist btusb\nblacklist bluetooth' > /boot/config/modprobe.d/bluetooth.conf and reboot will disable BT drivers also changing onboard USB header adapter like this one Error log looks clean and pre-clear has continued operating without dropping out, phew, maybe this is the winning combination.. Thanks again for the support Simon&Squid fingers crossed I can start the array once pre clear is done Quote Link to comment
Kosti Posted December 27, 2021 Author Share Posted December 27, 2021 Update - Preclear shows as completed successfully I think Dec 27 09:26:12 Medusa preclear_disk_3551483156325046[20654]: Post-Read: progress - 90% verified @ 119 MB/s Dec 27 12:33:38 Medusa preclear_disk_3551483156325046[20654]: Post-Read: dd - read 12000105070592 of 12000105070592 (0). Dec 27 12:33:38 Medusa preclear_disk_3551483156325046[20654]: Post-Read: elapsed time - 21:16:26 Dec 27 12:33:38 Medusa preclear_disk_3551483156325046[20654]: Post-Read: dd exit code - 0 Dec 27 12:33:38 Medusa preclear_disk_3551483156325046[20654]: Post-Read: post-read verification completed! Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: Cycle 1 Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: Reallocated_Sector_Ct 0 0 - Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: Power_On_Hours 84 125 Up 41 Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: Temperature_Celsius 38 38 - Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: Reallocated_Event_Count 0 0 - Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: Current_Pending_Sector 0 0 - Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: Offline_Uncorrectable 0 0 - Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 - Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: S.M.A.R.T.: SMART overall-health self-assessment test result: PASSED Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: Cycle: elapsed time: 41:08:31 Dec 27 12:33:39 Medusa preclear_disk_3551483156325046[20654]: Preclear: total elapsed time: 41:08:32 BUT the below logs worries me a fair bit as to why is this popping up? Can anyone pls tell me why this is occurring and if this is normal? Dec 27 05:35:57 Medusa kernel: usb 1-14: USB disconnect, device number 10 Dec 27 05:35:57 Medusa kernel: usb 1-14: new full-speed USB device number 11 using xhci_hcd Dec 27 05:35:57 Medusa kernel: input: MSI MYSTIC LIGHT as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/0003:1462:7D17.0006/input/input9 Dec 27 05:35:57 Medusa kernel: hid-generic 0003:1462:7D17.0006: input,hiddev96,hidraw2: USB HID v1.10 Device [MSI MYSTIC LIGHT ] on usb-0000:00:14.0-14/input0 Any idea chaps?? I really want to start using this new unraid build but fear its not stable enough? PEACE Kosti Quote Link to comment
SimonF Posted December 27, 2021 Share Posted December 27, 2021 Looks like rgb contro!ler is resetting are you using it? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.