-
-
Issues getting QSV working and intel.gpu.top installed
Thanks for the post. This was exactly my problem. I had added nomodeset to syslinux.cfg when trying to get my iKVM console to stop blinking. After I removed it my Sparkle Intel Arc A310 started working in Unraid.
-
Unassigned Devices Preclear - a utility to preclear disks before adding them to the array
Hi guys, first of all thanks the amazing plugin DLandon. I found something strange while pre-clearing my SAS drives. I have never been able to use the resume option after reboot and today tried to figure out why. Although I can resume my pre-clear and resume it from the web interface (see attached screenshots), it never gives me the option to resume after a reboot. Reading up on this forum post I checked /var/log/preclear.log, which states that the pre-clear has been paused. root@Unraid:/var/log/preclear# tail -f preclear.log Feb 10 10:12:07 Preclear script invoked as: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh --notify 4 --frequency 4 --cycles 1 --skip-preread --skip-postread --no-prompt /dev/sds Feb 10 10:12:08 preclear_disk_PBGK10SX_26298: Preclear Disk Version: 1.0.29 Feb 10 10:12:08 preclear_disk_PBGK10SX_26298: Disk size: 4000787030016 Feb 10 10:12:08 preclear_disk_PBGK10SX_26298: Disk blocks: 7814037168 Feb 10 10:12:08 preclear_disk_PBGK10SX_26298: Blocks (512 bytes): 7814037168 Feb 10 10:12:08 preclear_disk_PBGK10SX_26298: Block size: 512 Feb 10 10:12:08 preclear_disk_PBGK10SX_26298: Start sector: 0 Feb 10 10:12:10 preclear_disk_PBGK10SX_26298: Zeroing: zeroing the disk started 1 of 5 retries... Feb 10 10:12:10 preclear_disk_PBGK10SX_26298: Zeroing: emptying the MBR. Feb 10 11:45:09 preclear_disk_PBGK10SX_26298: Zeroing: progress - 25% zeroed @ 172 MB/s Feb 10 11:45:54 Preclear paused on all devices Feb 10 11:45:55 preclear_disk_PBGK10SX_26298: Pause requested Feb 10 11:45:56 preclear_disk_PBGK10SX_26298: Paused Feb 10 11:46:55 Preclear resumed on sds Feb 10 11:46:56 preclear_disk_PBGK10SX_26298: Resumed Feb 10 11:49:11 Preclear paused on all devices Feb 10 11:49:11 preclear_disk_PBGK10SX_26298: Pause requested Feb 10 11:49:11 preclear_disk_PBGK10SX_26298: Paused Looking at the /boot/preclear_reports directory I can see a resume file has been made. root@Unraid:/boot/preclear_reports# ls -lat total 56 -rw------- 1 root root 599 Feb 10 11:49 5000cca03b1ef89c.resume Content of that file looks good. root@Unraid:/boot/preclear_reports# cat 5000cca03b1ef89c.resume # parsed arguments format_html='' no_prompt='y' read_stress='y' write_size='' notify_channel='4' skip_postread='y' notify_freq='4' skip_preread='y' write_disk_mbr='' cycles='1' read_blocks='' erase_preclear='n' verify_zeroed='' read_size='' verify_disk_mbr='' short_test='' erase_disk='n' # current operation current_op='zero' current_pos='1040277569536' current_timer='5752' current_cycle='1' # previous operations preread_average='' preread_speed='' write_average='' write_speed='' postread_average='' postread_speed='' # current elapsed time main_elapsed_time='5762' cycle_elapsed_time='5761' Progress also shows that the pre-clear is paused. #################################################################################################### # Unraid Server Preclear of disk 5000cca03b1ef89c # # Cycle 1 of 1, partition start on sector 64. # # # # Step 1 of 3 - Zeroing in progress: (26% Done) PAUSED # # # # # # # # # # # # ** PAUSED # # # #################################################################################################### # Cycle elapsed time: 1:36:02 | Total elapsed time: 1:36:03 # #################################################################################################### When I tried another drive (in this case a SATA drive), resuming did work after reboot. But I noticed that for this drive, the name in the log file and the name of the resume file where the same. Which was not the case with the SAS drive as shown above. root@Unraid:/boot/preclear_reports# tail -f /var/log/preclear/preclear.log Feb 10 12:08:06 Preclear script invoked as: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh --notify 4 --frequency 4 --cycles 1 --skip-preread --skip-postread --no-prompt /dev/sdc Feb 10 12:08:07 preclear_disk_Z1D22906_22098: Preclear Disk Version: 1.0.29 Feb 10 12:08:07 preclear_disk_Z1D22906_22098: Disk size: 1000204886016 Feb 10 12:08:07 preclear_disk_Z1D22906_22098: Disk blocks: 244190646 Feb 10 12:08:07 preclear_disk_Z1D22906_22098: Blocks (512 bytes): 1953525168 Feb 10 12:08:07 preclear_disk_Z1D22906_22098: Block size: 4096 Feb 10 12:08:07 preclear_disk_Z1D22906_22098: Start sector: 0 Feb 10 12:08:12 preclear_disk_Z1D22906_22098: Zeroing: zeroing the disk started 1 of 5 retries... Feb 10 12:08:12 preclear_disk_Z1D22906_22098: Zeroing: emptying the MBR. Feb 10 12:27:14 preclear_disk_Z1D22906_22098: Zeroing: progress - 25% zeroed @ 193 MB/s Feb 10 12:27:43 Preclear paused on all devices Feb 10 12:27:44 preclear_disk_Z1D22906_22098: Pause requested Feb 10 12:27:45 preclear_disk_Z1D22906_22098: Paused root@Unraid:/boot/preclear_reports# ls -lat total 64 drwx------ 2 root root 8192 Feb 10 12:27 ./ -rw------- 1 root root 598 Feb 10 12:27 Z1D22906.resume After renaming the resume file to the name used in the logfile of the SAS drive. Resuming after reboot also works for the SAS drive. cp 5000cca03b1ef89c.resume PBGK10SX.resume
MvHeezik
Members
-
Joined
-
Last visited