moose

Thank you @Random.Name I will check this out.

Does anyone know if a plugin exists (or docker container exists) that can measure the kilowatt-hours (kWh) that a unRAID server consumes? This would be helpful to measure average cost to operate over various periods (hour, day, week, month, year, custom). In unRAID "Settings/UPS Settings" I see a LOADPCT variable that is dynamically being measured and updated ~ every few seconds. I think if this was recorded with respect to time and calibrated with my known UPS capacity, kilowatt-hours could be calculated for user defined time intervals. Users could input their cost per kWh and have a good estimate of what it costs them to operate their unRAID server. I think you can buy a third party device for this but why not make it free for all in unRAID? If I knew how to develop this I would try. Anyone know if something already exists or how someone could create this?

Thank you JorgeB. I ran extended tests on disk 13 again and it started failing, disk 5 also started throwing read errors and was disabled. Disk 5 also failed extended tests. I ended up replacing both disk 5 and 13. The data rebuild completed on the new 5 and 13 disks. I am up and running with no issues! Thank you for the help!!

Will do. Thank you JorgeB and trurl for your help! Very appreciated! I ran another extended SMART test on disk 13 and it failed, so I ended up replacing both disk 5 and 13. The data rebuild on both disks completed successfully. The problem is fixed and I'm up and running again! Thank you!!

The extended test on disk 5 failed. Attached are new diagnostics with the array started. artoo-detoo-diagnostics-20220915-2230.zip

Yes, all was done with the system on. I enabled Smart attributes 1 and 200 or 1 for all WD disks (some WD did not have SMART attribute 200). I was able to do a clean shut down through the GUI. I rebooted and disk 5 is disabled (disk 13 is emulated and ready for data rebuild). I ran a short self test on disk 5 and it passed, now am running an extended test on disk 5. Attached are new diagnostics. I will wait for the extended test to complete and advice before proceeding. Array is not started. artoo-detoo-diagnostics-20220915-2103.zip Edit: The extended test failed for disk 5. The SMART report is attached. artoo-detoo-smart-20220915-2133.zip

I was rebuilding a disabled disk (#13) and into the disk rebuild process I noticed another data disk (#5) with read errors. I paused the rebuild operation and then ensured the breakout cable was seated into the disk 5 cage and I also pulled disk 5 from the cage and re-seated it. Now when I attempt to resume the disk rebuild or cancel the disk rebuild, nothing occurs, the rebuild operation remains paused. I've attached diagnostics and a screenshot of the GUI interface. Any recommendations? artoo-detoo-diagnostics-20220914-2109.zip

Sorry for the delay in responding. Attached are diagnostics. I did not start the array, just booted and generated diagnostics. (Disk 13 is disabled. Disk 3 was also having issues and I thought it was also disabled when I shut down the server but now disk 3 shows as ok.) artoo-detoo-diagnostics-20220912-2030.zip

I didn't know Unraid won't disable more disks that there are parity drives. This would have kept me from panicking and shutting it down. @JorgeB I didn't save diagnostics before I shut down the server. If Unraid won't disable more disks than there are parity drives, I can boot the server and produce diagnostics. The server state should be ~ the same as it was when the 2 data disks were disabled due to read errors, correct?

I have an array with 2 parity disks and 16 data disks. I had 1 data disk have read errors and become disabled. I performed short/long tests on the disk and it was fine so I rebuilt the data disk, moved the server to a new location due to home remodel. Everything was fine for several days then I had 2 different data disks have read errors and get disabled. I shut server down thinking cabling may be the issue and I was afraid a 3rd data disk may have read errors and get disabled. Server is still shut down. I though I would recheck all cabling before restarting and risking a 3rd data disk disable before I can rebuild the 2 data disks that are currently disabled. I have a LSI controller (flashed to IT mode) and SAS breakout cables. My question is what happens if with 2 parity disks, more than 2 data disks get disabled due to read errors (which might be cabling)? Since the seemingly only way to correct a disabled disk is to rebuild it, 2 parity disks and 3 or more disabled data disks seems like a data loss?

Thank you for the clarification jonathanm!

FWIW, I have the same scenario as strike. Using the binhex preclear docker, I successfully precleared a 4TB and 8TB drive. I stopped the array, assigned the new drives and started the array. Both drives are "clearing" and should be complete in ~ 24 hours. I would have thought unRAID would have known the drives were already precleared. Anyway it's just going to take a bit longer for the second "clearing" cycle to complete, no big deal for now. Merry Christmas to all! edit: Another oddity on the second clearing topic. A few days earlier, I precleared 2 new 10TB drives using the binhex preclear docker, preclear worked fine. The 2 10TB drives were then assigned as parity replacements (1 10 TB at a time for a dual parity configuration). I didn't have any issue with unRAID clearing these drives for a second time, meaning unRAID did not clear these 2 10TB drives a second time when I added them as new parity drives and rebuilt/re-synced array parity. I'm also on 6.8 stable.

Thanks all!

Would you mind providing a link to that bug report? Honestly I tried to find it on my own but could not...

Thanks j0nnymoe for enlightening me!

Is anyone running v5.10 or is the general recommendation to go to v5.9 max? I'm running v5.9.29 and haven't had any issues so far...

@JonMikeIV I also upgraded from 6.6.7 to 6.7.0 but had no hanging issue. I'm not sure if this makes a difference but I always do this before starting the unRAID OS upgrade and have never had it hang: Stop VMs and Dockers Stop Array, confirming it stops sucessfully Then upgrade OS Then reboot I know this doesn't really help your current situation but just wondered if it might explain the hanging.

Updated from 6.6.7, no issues. Thank you for the excellent work!

Hi spants, I have a question with respect to the comment/detail from yippy3000, does this mean that after some time of running the docker (as it now exists) that the docker (pihole dns server) becomes unusable/unresponsive? I ask because I installed the pihole docker and it seemed to work great for about a day or so then all LAN devices were unable to DNS resolve. My remedy was to remove pihole. I really like the function/benefit/concept of pihole and would like to reinstall/have it work as a docker. In other words is there any issue with this docker or are people successfully using it for a ~ indefinite period? (guessing the docker is fine and it was perhaps some config tweak/change I made in that first day or so)

Thanks trurl! Update: After removing and reinstalling, I was delighted to see that all my previous custom plex settings were maintained. All I had to do was uninstall the existing plex docker (also selected the remove image option), then install a new plex docker from the Apps tab and remap my previous share and transcode paths. All previous user detail and custom settings were maintained with the new plex install, awesome! Easy fix!

I renamed my plex container name from "plex" to "Plex" in the container configuration, now the configuration (conf file) is missing. I can't go back and rename the container from "Plex" to "plex", cannot perform any updates. I searched hte /mnt/cache/appdata/plex folder and its empty (no conf file). Is there anyway to get the conf file back or do I need to remove and reinstall plex? Or can I just reinstall without deleting plex and will it recreate a conf file and preserve the existing settings?

The original preclear_disk.sh has to be patched in order to work with unRAID 6.2 Just to be clear....by "patched" do we mean the following: Patched = download the original preclear script by Joe L (here) and place that preclear script in "/boot/config/plugins/preclear.disk/"? Here is the info on the patch for Joe L's original preclear script http://lime-technology.com/forum/index.php?topic=13054.msg464653#msg464653. According to gfjardim, his script is 6.2 compatible out of the box. No patch required. https://lime-technology.com/forum/index.php?topic=39985.msg504465#msg504465. Thank you. I tried several times but had trouble with gfjardim's script on v6.2.1. I installed, uninstalled, re-installed, etc, many times but had issues with my syslog filling up, webGUI becoming unresponsive and the zeroing (write cycle) was ~ 5MB/s. Then I had tried to run Joe L's original preclear script in v6.2 via telnet and couldn't the preclear script to run, but.... with the "sed..." command modification Joe L. lists at the 1st link you provided, it works via telnet, although the pre-read cycle does seem slow... It seems preclear isn't playing well with v6.2 for me... FYI - here is the syslog detail from the preclear operation....this keeps repeating over and over while preclear runs filling up the syslog. I ended up canceling the preclear I had running in telnet. Oct 13 22:41:08 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 7b 4b 04 d8 00 00 01 00 00 00 Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(11) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(114688) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(16384), sc->result(0x00000000) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:08 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:09 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 2f 00 00 00 01 00 00 00 Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(9) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(131072) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(0), sc->result(0x00000000) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:09 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:10 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 32 00 00 00 01 00 00 00 Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(9) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(130560) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(512), sc->result(0x00000000) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:10 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:11 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 42 00 00 00 01 00 00 00 Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(11) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(130560) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(512), sc->result(0x00000000) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:11 Artoo-Detoo kernel: sd 1:0:11:0: [sdm] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 43 00 00 00 01 00 00 00 Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: sas_address(0x4433221105000000), phy(5) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: enclosure_logical_id(0x500605b002b71570),slot(6) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: handle(0x0014), ioc_status(success)(0x0000), smid(11) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: request_len(131072), underflow(131072), resid(130560) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: tag(65535), transfer_count(512), sc->result(0x00000000) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: scsi_status(check condition)(0x02), scsi_state(autosense valid )(0x01) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: [sense_key,asc,ascq]: [0x06,0x29,0x00], count(18) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312) Oct 13 22:41:11 Artoo-Detoo kernel: mpt2sas_cm0: log_info(0x31120312): originator(PL), code(0x12), sub_code(0x0312)

The original preclear_disk.sh has to be patched in order to work with unRAID 6.2 Just to be clear....by "patched" do we mean the following: Patched = download the original preclear script by Joe L (here) and place that preclear script in "/boot/config/plugins/preclear.disk/"?

I'm getting this error when trying to update this plugin for v6.1.8.

Worked. Although in my case, the plugin was actually there and on checking for updates, there was one. I updated (somewhat tentatively) but everything went smoothly. Current version is 2015.08.01c. This command worked for me too and I had the same results as Frank1940. Thanks bonienl! All is fixed now and I'm on 2015.08.01c