drawde

not sure if there's a way to download a SMART self-test but got the following: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 2756 - Looks good to me. Going to run a preclear just for peace of mind before adding back into action (possibly as a 2nd parity for now). Thanks! EDIT: hmm, doesn't seem to want to mount under unassigned devices so i can run a preclear on it.. getting the following: Jul 20 17:31:19 Tower unassigned.devices: Adding disk '/dev/sdt1'... Jul 20 17:31:19 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdt1' '/mnt/disks/ST16000NM001G-2KK103_ZL2ATVRA' Jul 20 17:31:19 Tower kernel: XFS (sdt1): Mounting V5 Filesystem Jul 20 17:31:19 Tower kernel: XFS (sdt1): Log inconsistent (didn't find previous header) Jul 20 17:31:19 Tower kernel: XFS (sdt1): failed to find log head Jul 20 17:31:19 Tower kernel: XFS (sdt1): log mount/recovery failed: error -5 Jul 20 17:31:19 Tower kernel: XFS (sdt1): log mount failed Jul 20 17:31:19 Tower unassigned.devices: Mount of '/dev/sdt1' failed: 'mount: /mnt/disks/ST16000NM001G-2KK103_ZL2ATVRA: can't read superblock on /dev/sdt1. ' i tried xfs_repair -v /dev/sdt1 but it just started spamming .'s. I'll wait until parity is finished rebuilding on my other drive and try again later.

Next time I will remember to capture the diagnostics immediately. However I also attached logs that go back to April, not sure if there is anything useful there, but you can see when the drive actually first started having issues yesterday.

ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 071 064 044 - 12246579 7 Seek_Error_Rate POSR-- 080 060 045 - 92287026 Thanks! Is that raw value the actual number of sectors? Are numbers this big consistent with the drive experiencing some failures and being disabled only once?

man, i really am messing up lol.. the drive in question is ST16000NM001G-2KK103 (sdt), also the only 16tb drive.

LOL sorry, yes i did have a question. Is the hdd likely dying or could it be something else? i was never good at deciphering the smart reports, any feedback or tips would be appreciated. hardware-wise all i've done so far is reseat the drive. but took it out of service already. It's only been a few months. drive is still attached and running an extended SMART currently. if smart comes up good was thinking of running a preclear or two on it.

I messed up and forgot to get diagnostics before rebooting (doh!) and I'm currently rebuilding parity on a new drive. I've attached diagnostics anyways. I do have syslogs dating back to april that hopefully is helpful though. tower-diagnostics-20210719-2046.zip syslog.txt.log

hello all, trying to move some data around and i'm getting the following error: I: 2021/03/15 23:16:14 core.go:710: Command Started: (src: /mnt/disk10) rsync -avPR -X "TV/Show" "/mnt/disk6/" I: 2021/03/15 23:16:15 core.go:767: command:retcode(0):exitcode(0) I: 2021/03/15 23:16:15 core.go:1028: Command Finished I: 2021/03/15 23:16:15 core.go:1041: Current progress: 100.00% done ~ 0s left (10792.87 MB/s) I: 2021/03/15 23:16:15 core.go:972: removing:(rm -rf "/mnt/disk10/TV/Neds Declassified School Survival Guide") W: 2021/03/15 23:16:15 shell.go:51: transferProgress::(rm: cannot remove '/mnt/disk10/TV/Show Guide/banner.jpg': Read-only file system) W: 2021/03/15 23:16:15 shell.go:51: transferProgress::(rm: cannot remove '/mnt/disk10/TV/Show Guide/fanart.jpg': Read-only file system) W: 2021/03/15 23:16:15 shell.go:99: transferProgress:: waitError: exit status 1 W: 2021/03/15 23:16:15 core.go:985: Unable to remove source folder (/mnt/disk10/TV/Show): exit status 1 it appears the moved work, the files exist on the new drive but they are also still on the source drive.

is this hitting million CPU suddenly for anyone else? had to stop it. every time i turn it on, my CPU usage goes through the roof.

i'm having the same issue. thoughts? i've seen this in the past, i think my omvf doesn't work as in other VMs i've also had to use seabios. EDIT: nevermind, seems the instructions has been updated. followed and working now.

CPU temp missing all of a sudden for anyone else?

happy 14 years!

Downloaded coppit's plg from github, edited the fields SimonF mentioned, copied the file to /boot/config/plugins and installed the plg via the webUI and snmp is working again on 6.7 (stable). I didn't install netsnmp prior as mentioned, i figured the plg would install it which it did. Haven't tried rebooting and see if it installs on boot yet though (but i don't see why it wouldn't?) If anything i can just install the new plg manually again.

There is also the SNMP plugin where you can send temp info to a nms like observium or librenms.

had a preclear die 1/3 of the way through. does this indicate any drive issue or just a script hiccup? ############################################################################################################################ # # # unRAID Server Preclear of disk K7HBW54L # # Cycle 3 of 3, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read in progress: (22% Done) # # # # # # # # # # # # # # # # # # # # ** Time elapsed: 1:13:18 | Current speed: 205 MB/s | Average speed: 204 MB/s # # # ############################################################################################################################ # Cycle elapsed time: 1:13:19 | Total elapsed time: 65:15:59 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL CYCLE 1 CYCLE 2 STATUS # # 5-Reallocated_Sector_Ct 0 0 0 - # # 9-Power_On_Hours 0 32 64 Up 64 # # 194-Temperature_Celsius 32 36 37 Up 5 # # 196-Reallocated_Event_Count 0 0 0 - # # 197-Current_Pending_Sector 0 0 0 - # # 198-Offline_Uncorrectable 0 0 0 - # # 199-UDMA_CRC_Error_Count 0 0 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear Finished Successfully!. malloc: jobs.c:1246: assertion botched free: underflow detected; mh_nbytes out of range Aborting.../usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 864: 0+()%(7814037168) : syntax error: operand expected (er ror token is ")%(7814037168) ")

How often are updates pushed for this docker? The new release has metadata support now

anyone else having this issue https://github.com/Radarr/Radarr/issues/2485? is there any way to change to the nightlies using this docker? or should we just wait?

hello all, i've been having issue with my sonarr docker lately. it'll just randomly stop working. the logs don't show too much. the docker still appears to be running in the unraid gui, but i cannot access the webui and also it is not pulling anything. i've tried removing and readding the docker container/image and also rebuilding my docker.img from scratch. one thing i am noticing in the docker logs are multiple "[Trace] Owin: SQLite error (5): database is locked" errors. is my db corrupted? EDIT: readding logs, had to remove API keys. also it seems those sqlite errors are normal based on a quick google search. i'm not sure if this matters, but when the problem first started happening, i went to turn on trace logs, but saw that it was already enabled, for who knows how long. could this cause issues? maybe the logs are filling up and breaking something. there's plenty of room on the docker img and the location where my appdata is, but possibly the logs are saved to memory? docker.log sonarr.txt

anyone else's sonarr crashing on the latest unraid? i'll have to capture the logs next time but wanted to put a feeler out there. maybe it's just me.

Fixed for me as well, looks like the missing python package was added to resolve the issue. can anyone confirm it's fixed? haven't restarted my unraid array in forever but had to do today and sab wouldn't work. only after i added ADVANCED_DISABLEUPDATES did it work.

sudo apt-get install in my usefile.sh didn't work, i might need to run apt-get upgrade or add the repos, but honestly i dont want to break everything else that works perfect just for this. is everything in the docker contained within itself? if i do this, the dependencies should not break anything outside of the plex docker right? i'm almost tempted to run another instance of plex in a vm or on another machine and just share the channel (apparently this is a thing now) so as to not mess up anything, and if i do i can just wipe the vm and start over.

anyone know how to get a channel that requires node.js working? Ionix on github mentioned to someone that you can use advanced_user_script to do this but i'm not sure how to go about it. any ideas?

with the latest plex version it keeps scanning my library over and over using a lot of CPU. anyone else having this issue? the only way to fix it is to restart plex, which only calms it down for a few hours.

is this something to be worried about during a preclear? never seen these in the logs when preclearing a drive. sdg is the drive that i'm currently preclearing, and viewing the status it seems to be still preclearing OK. Dec 2 00:12:50 Tower udevd[3424]: timeout: killing 'ata_id --export /dev/sdg' [3425] Dec 2 00:12:51 Tower udevd[3424]: timeout: killing 'ata_id --export /dev/sdg' [3425] Dec 2 00:12:52 Tower udevd[3424]: timeout: killing 'ata_id --export /dev/sdg' [3425] Dec 2 00:12:53 Tower udevd[3424]: 'ata_id --export /dev/sdg' [3425] terminated by signal 9 (Killed) Dec 2 00:12:53 Tower udevd[3424]: timeout 'scsi_id --export --whitelisted -d /dev/sdg' Dec 2 00:13:35 Tower kernel: sdg: sdg1 EDIT: okay just to add a little more info.. root@Tower:~# cat /var/log/syslog |grep udevd Dec 2 00:12:49 Tower udevd[3424]: timeout 'ata_id --export /dev/sdg' Dec 2 00:12:50 Tower udevd[3424]: timeout: killing 'ata_id --export /dev/sdg' [3425] Dec 2 00:12:51 Tower udevd[3424]: timeout: killing 'ata_id --export /dev/sdg' [3425] Dec 2 00:12:52 Tower udevd[3424]: timeout: killing 'ata_id --export /dev/sdg' [3425] Dec 2 00:12:53 Tower udevd[3424]: 'ata_id --export /dev/sdg' [3425] terminated by signal 9 (Killed) Dec 2 00:12:53 Tower udevd[3424]: timeout 'scsi_id --export --whitelisted -d /dev/sdg' Dec 2 14:06:25 Tower udevd[30612]: timeout 'ata_id --export /dev/sdg' Dec 2 14:06:26 Tower udevd[30612]: timeout: killing 'ata_id --export /dev/sdg' [30613] Dec 2 14:06:27 Tower udevd[30612]: timeout: killing 'ata_id --export /dev/sdg' [30613] Dec 2 14:06:28 Tower udevd[30612]: 'ata_id --export /dev/sdg' [30613] terminated by signal 9 (Killed) Dec 2 14:06:28 Tower udevd[30612]: timeout 'scsi_id --export --whitelisted -d /dev/sdg' Dec 3 03:59:05 Tower udevd[18972]: timeout 'ata_id --export /dev/sdg' Dec 3 03:59:06 Tower udevd[18972]: timeout: killing 'ata_id --export /dev/sdg' [18973] Dec 3 03:59:07 Tower udevd[18972]: 'ata_id --export /dev/sdg' [18973] terminated by signal 9 (Killed) Dec 3 03:59:07 Tower udevd[18972]: timeout 'scsi_id --export --whitelisted -d /dev/sdg' i started the preclear on dec 1 at around 1-2pm, the times of these errors is about dec 2 00:12, 14:06, and dec 3 03:59. i'm thinking this aligns with some part of the preclear process, as i've run 3 cycles, and it's about 11-14 hours apart which based on my estimation, this is about how long it takes for 1 cycle?? and lastly, my preclear report ended up fine, no issues. root@Tower:/boot/preclear_reports# cat preclear_rpt_WD-WCC4M4LCZXJY_2015-12-03 ========================================================================1.15 == invoked as: /boot/config/plugins/preclear.disk/preclear_disk.sh -c 3 /dev/sdg == WDCWD20EFRX-68EUZN0 WD-WCC4M4LCZXJY == Disk /dev/sdg has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 5:36:55 (98 MB/s) == Last Cycle's Zeroing time : 4:37:50 (119 MB/s) == Last Cycle's Post Read Time : 9:15:10 (60 MB/s) == Last Cycle's Total Time : 13:53:59 == == Total Elapsed Time 47:17:09 == == Disk Start Temperature: 26C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 120 121 0 ok 27 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ anyone preclear any drives with the plugin recently and see the same lines in their logs? is this normal? a bug?

might be kinda OT, not related to this plugin but is SNMP only for LAN elements? i tried to install snmp on my vps that i rent but i was unable to connect.

the only thing that's making me upset so far is i can't find any way to get temp sensors for windows working but anyways so far this is pretty cool.