Kosti

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

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

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?

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 ?

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

Hey, So new unraid box, all new, and ran in to issues with pre-clear, after some trouble shooting isolated the issue to possible ram, as ran a few memtest and one of the 16GB pairs failed the test Now server is running 32GB instead of 64GB while I RMA the suspect 32GB Kit, since the pre-clear failed, when I try to run again it details a previous PRCLR, should I resume it or start fresh clear and skip pre read? Thanks preclear_disk_3551483156325046_21811.txt

Should I resume the pre clear or start a new clear and skip pre and post read?

My update..I removed 32Gb of ram from the total of 64GB and ran a MEMtest of 4 passes, 1st 32GB kit PASS no issues. Removed this 32GB Kit and swapped them for the other new 32GB kit and restarted MEMtest, this has failed!!! Can't believe brand new RAM is running errors! I will set up UNRAID with 32GB and try the PRE-Clear again

Hey, thanks for the reply gents, But I am a little confused with these responses, so if you have time to re-address ? @JorgeB[1] Is the method I used to pre-clear the cause of the failure because I do not have the array started and these are all unassigned disks and nothing is mapped yet as parity etc?? Should I use the above plugin you shown, is this different from what I used and followed guides from ibracorl to install top 20 apps, Does the one I installed the pre clear plugin in terms of the behaviour and tasks that different? @Squid[2]FYI I'm using a USB2 port and I have a USB onboard connector which is USB2 as shown in the attachement [thanks for the tip] so we're going to lean towards the USB flash drive for having an issue? So its in a USB2 using a USB3 Flash now the issue here or something else within my hardware? Should I use something like HIRENS CD and run MEM tests and stress test anything else considering everything is brand new? PEACE Kosti

OK a bit of an update, seems something went horribly wrong, now the 2nd 12TB has also failed the pre-clear? But now I also got a fatal error from the flash drive I can try another USB stick although this one is a USB 3 type, never had any issues in the HP while it was under test before moving to this new hardware, Very strange! Thoughts? preclear.disk.txt

Hey All Been a while, I retired my HP GEN8 and with the sale of that machine I purchased and updated to a whole new system which I just booted it up last night for the first time, using a fresh install of unraid on the same USB so I could tie my licence to it easy. My SPECS CPU - Intel 11th Gen Core i5-11400 2.60GHz LGA1200 Desktop Processor - Retail Box comes with HSF Motherboard - MSI MAG B560M Mortar Wi-Fi LGA 1200 mATX Motherboard RAM - G.Skill 64G [(2x16G) X 2 ] F4-3200C16D-32GIS PC4-25600 DDR4 3200 Mhz CASE - Fractal Design Node 804 DISKS 2 X 1TB 970 EVO ; 3 x 12TB Elemental Drives, some 4TB which will be removed soon Since the 12TB came from Amazon and from overseas, I ran it through a pre clear, I just ran the 2 x 12TB in their USB enclosures and once has just failed? See attached file I am not sure if its my new PC or the actual drive? I only ran it preclear with clear and post check only and started both 12TB drives a few seconds after each other Have I got a bad 12TB or I should not run these together and run them one at a time Let me know what you guys think? PEACE Kosti preclear_disk_3551483156325046_21811.txt

Not smiling here! I hope someone who takes this up, offers assistance for those 1% people who are on a budget and want to use unraid but are crippled by its installer as I bought 2 new USB from Sandisk - Ultra fit 32GB to use for unraid to trial and I can't even do that because this installer doesn't recognise it? How can I even test unraid when the installer is whacked and I have to try and use a manual method where I can't even grab a beta version to test? Sux Balls as spent money on USB sticks in preparation to use and purchase unraid and when asked here for help I'm told buy another USB stick. Given my currency is shit compared to the USD, this is not a cheap purchase for me wanting the pro version comes in just under $200..

Anyone got some clues for my preclear issue and USB creator tool using a USB with no key and moving files via a painful manual creation of the USB? As for the Server time, I will just ignore it and leave it unsynchronized seems to be a bug in unraid taking too long to find a time My issues with PRECLEAR, and one of the reasons I rebuilt the HP Gen 8 was during my first preclear of a enclosed USB3 12TB, the server mysteriously rebooted about 95% into the preclear, I tried to reboot the server as I was able to log into via ILO and used the soft start but as soon as I did the PSU popped, yes large bang sound! hence why I moved it to another case with a larger PSU and didn't want to wait 3mths and pay for another 1RU PSU which I bought to replace the original 180W with same brand 400W. One other strange occurrence was preclear was no longer on the server after I rebuilt it, same USB stick and same everything except didn't put any drives back in and just before the server shut down I noticed one of the CPU cores was maxing out which I though was strange.

Thanks mate, your a champ for taking the time to chime in, really appreciate it I created another bunch of questions in the general section HERE, thinking this area wasn't for such questions, shame as its had 85 views and not much of a way of clues as to why I had experienced a catastrophic failure during preclear.. Don't know what your name is dude can't work out the emoji LOL

As my current USB and the unraid OS is well over 30days, does this cause any problems if the trial license has expired or that I never aquired a trial licence? Meaning is this somehow crippling my system up? The plan was to test some features but life got in the way and with COVID I managed to test this on a ESXI prior to moving this as a stand alone, now I want to move this to another USB which there lies the next problem in that I just purchased 2 sandisc ultrafit usb 3.1 flash drive but the UBS creator doesn't recognize it ? I've used another similar USB3.0 stick (current) one just fine, and yes I've read that USB2 is preferred etc but what is the creator looking for? Given I purchased these 2 usb sticks to be identical for the purpose to be used for unRaid and both are not being detected by the creator, this is something I would've expected back in 2014 when I first looked unraid not in 2020 when I come back to check in? Is the manual install the only way to install unraid on these USB units and would I be able to transfer from current details from the old one to the new USBs given the tool doesn't work?

Hey All Most may have seen my new re-build in UCD HERE and my return to these parts in over 5 years+ So I am wanting to ask a few questions in one thread since I am starting from scratch. First up is my Unraid logs show kernel reports TIME_ERROR: 0x41: Clock Unsynchronized so is it something not agreeing with unraid? or just that it requires time to "sync"? Jun 10 15:57:52 Medusa root: Starting Nginx server daemon... Jun 10 16:03:00 Medusa ntpd[1625]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized root@Medusa:~# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 212m 64 0 0.000 0.000 0.000 *85.199.214.98 .GPS. 1 u 13 64 377 293.491 1.450 0.819 -ntp4.rbx-fr.hos 131.176.107.13 2 u 413 1024 377 302.521 -8.232 8.099 +ns.iitp.ru 89.109.251.21 2 u 446 1024 377 329.865 -1.206 2.052 +103.214.220.220 202.6.131.118 2 u 396 1024 377 12.893 -0.864 1.884 root@Medusa:~# Should I be concerned, as this is only one entry time sync error log now? Next issue I had was with PRECLEAR, The whole reason I rebuilt the HP Gen 8 was during my first preclear of a enclosed 12TB, the server mysteriously rebooted about 95% into the preclear, I tried to reboot the server as I was able to log into via ILO and used the soft start but as soon as I did the PSU popped, yes large bang sound! hence why I moved it to another case with a larger PSU and didn't want to wait 3mths and pay for another 1RU PSU which I bought to replace the original 180W with same brand 400W. One other strange occurrence was preclear was no longer on the server after I rebuilt it, same USB and same everything and just before the server shut down I noticed one of the CPU cores was maxing out which I though was strange. So my USB 12TB HDD got to about 95% before the catastrophic failure so now when I try to preclear again it asks to resume, but this resume doesn't work. Do I have to start the preclear again and if so how can I do this by just writing zero's so that unraid will accept it and find a valid signature? Onto my other issue is that I've been using a USB and the OS which is well over 30days, does this cause any problems if the trial license has expired or that I never aquired a trial licence. Meaning is this somehow crippling my system up? The plan was to test some features but life got in the way and with COVID I managed to test this on a ESXI prior to moving this as a stand alone, now I want to move this to another USB which there lies the next problem in that I just purchased 2 sandisc ultrafit usb 3.1 flash drive but the UBS creator doesn't recognize it ? I've used another similar USB3.0 stick (current) one just fine, and yes I've read USB2 is preferred etc but what is the creator looking for? Given I purchased these 2 usb sticks to be identical for the purpose to be used for unraid and both are not being detected by the creator, this is something I would've expected back in 2014 when I look unraid not in 2020? Is the manual install the only way to install unraid on these USB units and would I be able to transfer from current one to the new USBs? PEACE Kosti

Thanks JB, will do, although I have no preclear logs since the server rebooted and then PSU blew up?

Why does preclear offer to resume but them fails? My initial preclear got to 95% then something happened and killed my PSU?

Hi Sorry to hijack but I'm sort of doing the same trying to preclear drives WD easystore in their case before I open them up and install in my current new build HERE My 12TB got to 95% and then I lost power to the server for an unknown reason, (its on UPS) when I tried to turn it back on it blew the Delta 400W PSU hence why i removed it all and built it back into another case Preclear states there is a unfinished preclear session on the 12TB, but when I try to resume it, it fails! I do not want to redue the whole process and was hoping to continue but seems that is not possible. so I just want to be able to write all zeros and get the signature so unraid will be happy with the drive, but as I am not running docker and just using the GUI preclear, so its not clear which option PEACE Kosti

Anyone got idea's on how to solve my time sync error log?

OK added this to my go file and no more errors seen, hope this isn't really required..? Now the next issue is NTP, seems I am not getting the right sync or at least that's what the logs are telling me Jun 9 19:32:36 Medusa ntpd[1622]: ntpd [email protected] Fri Aug 2 18:40:41 UTC 2019 (1): Starting Jun 9 19:32:36 Medusa ntpd[1622]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Jun 9 19:32:36 Medusa ntpd[1624]: proto: precision = 0.045 usec (-24) Jun 9 19:32:36 Medusa ntpd[1624]: basedate set to 2019-07-21 Jun 9 19:32:36 Medusa ntpd[1624]: gps base set to 2019-07-21 (week 2063) Jun 9 19:32:36 Medusa ntpd[1624]: Listen normally on 0 lo 127.0.0.1:123 Jun 9 19:32:36 Medusa ntpd[1624]: Listen normally on 1 lo [::1]:123 Jun 9 19:32:36 Medusa ntpd[1624]: Listening on routing socket on fd #18 for interface updates Jun 9 19:32:36 Medusa ntpd[1624]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jun 9 19:32:36 Medusa ntpd[1624]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized I had a look at the date settings in unRaid and made some changes to use oceania.pool.ntp.org for NTP time but this made it worse? Even setting 0.pool.ntp.org 1, 2 respectively didn't seems to make any improvements Jun 9 20:06:48 Medusa ntpd[17600]: ntpd exiting on signal 1 (Hangup) Jun 9 20:06:48 Medusa ntpd[17600]: 127.127.1.0 local addr 127.0.0.1 -> <null> Jun 9 20:06:48 Medusa ntpd[17600]: 162.159.200.1 local addr 192.168.1.122 -> <null> Jun 9 20:06:48 Medusa root: Stopping NTP daemon... Jun 9 20:06:49 Medusa ntpd[18559]: ntpd [email protected] Fri Aug 2 18:40:41 UTC 2019 (1): Starting Jun 9 20:06:49 Medusa ntpd[18559]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Jun 9 20:06:49 Medusa root: Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp Jun 9 20:06:49 Medusa ntpd[18561]: proto: precision = 0.050 usec (-24) Jun 9 20:06:49 Medusa ntpd[18561]: basedate set to 2019-07-21 Jun 9 20:06:49 Medusa ntpd[18561]: gps base set to 2019-07-21 (week 2063) Jun 9 20:06:49 Medusa ntpd[18561]: Listen normally on 0 lo 127.0.0.1:123 Jun 9 20:06:49 Medusa ntpd[18561]: Listen normally on 1 br0 192.168.1.122:123 Jun 9 20:06:49 Medusa ntpd[18561]: Listen normally on 2 lo [::1]:123 Jun 9 20:06:49 Medusa ntpd[18561]: Listening on routing socket on fd #19 for interface updates Jun 9 20:06:49 Medusa ntpd[18561]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Jun 9 20:06:49 Medusa ntpd[18561]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized I've tried using several different NTP servers but get the same message in the system log every time I apply the new settings. I check the output from the console root@Medusa:~# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 37m 64 0 0.000 0.000 0.000 *time.cloudflare 10.26.8.4 3 u 37 64 377 9.078 0.673 2.823 -tick.chi1.ntfo. 206.55.64.77 3 u 31 64 377 201.290 -1.028 0.359 +ntp3.ds.network 162.159.200.1 4 u 35 64 377 57.536 -0.631 2.780 +ec2-13-55-50-68 203.206.205.83 3 u 28 64 377 9.605 0.734 1.597 root@Medusa:~#

Here are the pictures of the case transplant, not sure if the above link worked so added for viewing https://imgur.com/a/Wmsx0Ty

Thanks I'm sure I read that thread, as I am also running the latest BIOS, so the other option which I missed was to add in the line to the /boot/config/go file rmmod acpi_power_meter Will try this and see if this suppresses the spamming of the log file Will let you know how it goes PEACE Kosti

So looking at the logs I see the following filling up Jun 8 16:28:53 Medusa kernel: ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20180810/exfield-390) Jun 8 16:28:53 Medusa kernel: ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20180810/psparse-514) Jun 8 16:28:53 Medusa kernel: ACPI Error: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20180810/power_meter-338) Checking what is going on seems to point to a few pages in particular this one HERE I'm using the latest bios and all updates on the HP motherboard? sudo dmidecode -s bios-release-date 04/04/2019 HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 Believe the version of unraid is 6.8.3 Is there anything I can do to stop these filling up the logs? PEACE Kosti

G'Day Folks, WOW its been 5-6 years since I last looked at unRaid as my first attempt was way before features such as Kernel-based Virtual Machine and Dockers existed, Dang! Look how much you've grown "unRAID"!! Due to my own OCD or should I say my UCD again, I am reviving a HP Gen8 with a few modification, my last build was back in 2014 for MAIOS HERE. This HP ProLiant MicroServer Gen8 originally had the following upgrades inside the HP case, until the PSU went POP during a preclearing of a WD 12TB HDD via USB, while this is still a mystery why the PSU blew up, I wasn't going to shell out more for another PSU so decided to butcher up the GEN8 and move it to another case I had lying around CPU <> Xeon E3-1265L V2 with a modified Noctua NH-9i HSF RAM <> 16GB ECC RAM Real RAID <> HP Smart Array P420 flashed to IT mode with 2GB FBWC and BBU installed in PCI 1 CASE Mod added <> Addonics AESN5DA35-A Snap-In Disk Array PRO (holds 5 drives) Moved / swapped the SATA 1 cabling with the ODD making this to allows to boot off SSD due to BIOS limitations and HP not allowing to boot a HDD of the ODD, anyways this was done prior and now not required for use of unRAID). No longer required since moving to a more flexible case and cabling. PSU Delta PSU 400W PSU Corsair 650W Originally was using ESXI and ran unRaid along side a few other VM's like Xpenology and FreeNas. But honestly due to one dude "SpaceInvaderOne" & through his awesome tutorials on how good unRaid has become that I want to take a further look and rebuild my crippled NAS with the current hardware and try out unRAID again. My primary use is to be centralized storage for my household of 6 users, including Plex Media Server storage. I am not planning on doing much with the dockers yet, will have camera capture / surveillance, share folders across 6 users and backups of Apple devices. Possibly build a pfsens in a VM to replace the raspi running pie-hole. I'd planned to use a 250GB SSD for a cache drive, but thinking to replace this with 2 x 480GB SSD drives as RAID0 due to seeing 2 CRC errors for the single 250GB SSD, not sure if this is due to cabling or just the Samsung 840 is just getting old so may as well dump it for the 2 x Intel S3500 480G units. Eventually I want to use all 12TB drives which will last a while given I've just picked up 2 of them from Amazon recently, this is to allow me to sort and store all my folders and data to one of them before moving files to the NAS, Yep I've datahorded and spread across multiple drives - backups to duplication that I need to consolidate! List of HDD's that need consolidating 3 x 3TB WD Green; 1 x 3TB Seagate : These are already out free of data and ready to sell off to fund additional larger HDD's Still to sort and be wipe 6 x 4TB Seagate (4 of them are new, only powered up a few times if that, no data written to them or precleared yet so potentially will be used to add to unraid with one of the 12TB as the parity drive)? sell off unused drives to fund additional larger HDD 1 x 4TB WD; 1 x 5TB Toshiba; 1 x 8TB Seagate, once all data is moved to unRAID sell off to fund additional larger HDD Due to some limitations of the HP GEN8 board such as SATA ports, BIOS etc, I'm thinking for my build plan to including additional back up options. The loose plan is to use the 8TB as a parity drive and use 3 X 4TB for unRAID. Then take this data and back this up to another single drive not part of unraid and perform some sort of rsync or similar to keep it updated and backed up, eventually replacing the 8TB with a 12TB or larger I'm wanting to use the B120i onboard controller on the HP to do this as its a crap controller where by the first 2 slots are at SATAII 6G and the others are SATA1 3G. so hence I want to use the HP P420 Smart Array and use this for unRAID giving me 6 total drives towards unRAID and 2 drives Something like this B120i --> 2 x SATAII connect 2 x 12GB Mirror for backing up UNRAID B120i --> 2 X SATA I connect drives for slow storage or simply not used them? ODD SATA port, either use for backup purposes add to the above as a new pool or not use at all? HP Smart Array P420 --> Port 1 connect 4 drives, 1 x 8TB - 3 x 4TB HP Smart Array P420 --> Port 2 connect 2 X 480G SSD Cache, leaves 2 SATA ports for expansion creating hop spare or preclearing Feel free to advise best options with current hardware. For those keen to see what transplanted looked like PIX are HERE PEACE Kosti