-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by Perdurabo
-
So that's a? stop array take disk out of array start array stop array put disk back into slot start array - (should start rebuilding automatically) Thanks On a side note any ideas on enabling write cache on a SAS disk, sadly "hdparm -W 1 /dev/sdx" did not work. My other SAS disk (identical model just badged differently) has write cache enabled.
-
Hi, it still shows up as red x, is there some way to clear that and reset the disk. Thank you.
-
Smart report attached. Looks like a duff disk sadly. I have another spare and will try that one instead, see if I can get a replacement. ST4000NM0023_Z1Z69SQK_35000c50062a937eb-20210312-1908.txt
-
SAS disks seem to run hot, they are rated for up to 60 allegedly, sadly where I live cooling is a problem one way or another. the disk may have been manufactured a while ago, but I find it unlikely it was running for more than 5 years before I bought it. Beside the smart tests above reported 3 hours in use on first going into the system and then suddenly added 5 years of usage, seems to me to be a software problem. Those hours look like the old disks hours, not a "new" disk. The SMART testing on SAS disks seems to be weird one way or another as another SAS disk from last year whilst not red x has a single non-medium error and yet is fine. Anyway thanks for the help, I will post the long test results when they come in.
-
diagnostics report as requested tower-diagnostics-20210312-0847.zip
-
Good morning, I am having a small problem with a brand new disk. Disk3 which was in use for more than 5 years finally failed, so I replaced the disk, ran a full pre-clear with no errors and proceeded to add the disk into the array. All went fine until today (one day later) when it reported 2 medium errors and the system marked it with a red x. When I looked at the smart test log I saw this, the time difference between #4 and #5 is a few hours at best, it's almost looks like UNRAID has picked up the previous disks details and used that to red x the disk. SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background long Self test in progress ... 64 NOW - [- - -] # 2 Background long Aborted (by user command) 64 47991 - [- - -] # 3 Background short Completed 64 47990 - [- - -] # 4 Background short Completed 64 47983 - [- - -] # 5 Background short Completed 64 7 - [- - -] # 6 Reserved(7) Completed 48 7 - [- - -] # 7 Background short Completed 64 3 - [- - -] Long (extended) Self-test duration: 32700 seconds [545.0 minutes] and also shows this (excuse the formatting): Errors Corrected by Total Correction Gigabytes Total ECC rereads/errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 2799108152 34 0 2799108186 34 1273381.666 0 write: 0 0 0 0 0 129334.473 0 verify: 21310215 0 0 21310215 0 0.000 0 Any ideas on what to do to clear this up as I can't believe the disk has gone this bad this quickly. I am running a long smart disk test. FYI the old disk was 3TB SATA and this new one is 4TB SAS, both reiserfs. Thanks
-
Thanks for all the advice, any cards that only has power through the pci express, happy to get a quadro if that works? My rig is quite low powered at 300w.
-
No problem, I though that would be the case, thank you. I will buy something newer for transcoding in JellyFin, any recommendations?
-
Hi, I get the following error: Dec 21 09:22:40 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Dec 21 09:22:40 Tower kernel: NVRM: The NVIDIA GeForce 210 GPU installed in this system is Dec 21 09:22:40 Tower kernel: NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please Dec 21 09:22:40 Tower kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Dec 21 09:22:40 Tower kernel: NVRM: information. The 455.45.01 NVIDIA driver will ignore Dec 21 09:22:40 Tower kernel: NVRM: this GPU. Continuing probe... Dec 21 09:22:40 Tower kernel: NVRM: No NVIDIA graphics adapter found! Dec 21 09:22:40 Tower kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Dec 21 09:22:40 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Dec 21 09:22:40 Tower kernel: NVRM: The NVIDIA GeForce 210 GPU installed in this system is Dec 21 09:22:40 Tower kernel: NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please Dec 21 09:22:40 Tower kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Dec 21 09:22:40 Tower kernel: NVRM: information. The 455.45.01 NVIDIA driver will ignore Dec 21 09:22:40 Tower kernel: NVRM: this GPU. Continuing probe... Dec 21 09:22:40 Tower kernel: NVRM: No NVIDIA graphics adapter found! Dec 21 09:22:40 Tower kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 How do I install the legacy driver? and if it's possible is it worth it considering the card in 10 years old Thanks Henry
-
Ran the docker logs command and got this: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. When I installed the latest version the media browser only listed the top folders and inside the folders where all the movies are were blank and there was a 500 undefined error at the top of the page. Mostly MKV files in the system. Once I returned to version 161 the files all appeared again instantly. I checked the permissions: "-rw-rw-rw- 1 nobody users 15574070714 Jul 30 2013" for each file and it looks ok. folder structure: root@Tower:/mnt/user/Movies/Action Any ideas, or do you need anything more to debug the problem. Seems odd that at least 2 people have the problem. Regards Henry
-
Hi, Since version 162 (servio version 1.10) I cannot view the majority of my media files. All mkv files get indexed but then the is a "Unknown sever error (500, undefined) when browsing via the web or a device. MP4 and AVI files are fine and some hevc mkv files. Aside from converting all my files ot mp4 or going back to version 161 I am stuck, any ideas, I have done a full reset on permissions in unraid and still nothing.
-
Good morning, the latest Unraid 6.6.3 made Serviio unusable, playback on either my Samsung or LG tv was so stuttery that it was unwatchable, have reverted to 6.6.1 , just an fyi. Oh and any chance of a 1.10 core update? Thanks.
-
Update went well, but my docker of Serviio media server ran so slowly that video playback was unwatchable so I have reverted back to 6.6.1
-
Hi, I have just run an update and I am getting the same error and no amount of trying to update force or otherwise seems to work, any ideas? Thanks Henry 2017-04-24 16:07:25,463 WARN received SIGTERM indicating exit request Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2017-04-24 16:07:26.573136 [info] Host is running unRAID 2017-04-24 16:07:26.609092 [info] System information Linux Tower 4.9.19-unRAID #1 SMP PREEMPT Thu Mar 30 08:32:28 PDT 2017 x86_64 GNU/Linux 2017-04-24 16:07:26.651102 [info] PUID defined as '99' 2017-04-24 16:07:26.695457 [info] PGID defined as '100' 2017-04-24 16:07:26.760515 [info] UMASK defined as '000' 2017-04-24 16:07:26.799113 [info] Permissions already set for volume mappings 2017-04-24 16:07:27,153 CRIT Set uid to user 0 2017-04-24 16:07:27,154 INFO Included extra file "/etc/supervisor/conf.d/nzbget.conf" during parsing 2017-04-24 16:07:27,157 INFO supervisord started with pid 7 2017-04-24 16:07:28,159 INFO spawned: 'nzbget' with pid 40 2017-04-24 16:07:28,171 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists 2017-04-24 16:07:28,174 DEBG 'nzbget' stderr output: /usr/bin/nzbget: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory 2017-04-24 16:07:28,174 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47081066985880 for <Subprocess at 47081066986384 with name nzbget in state STARTING> (stdout)> 2017-04-24 16:07:28,174 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47081066985160 for <Subprocess at 47081066986384 with name nzbget in state STARTING> (stderr)> 2017-04-24 16:07:28,175 INFO exited: nzbget (exit status 127; not expected) 2017-04-24 16:07:28,175 DEBG received SIGCLD indicating a child quit 2017-04-24 16:07:29,178 INFO spawned: 'nzbget' with pid 43 2017-04-24 16:07:29,190 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists 2017-04-24 16:07:29,192 DEBG 'nzbget' stderr output: /usr/bin/nzbget: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory 2017-04-24 16:07:29,192 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47081066985880 for <Subprocess at 47081066986384 with name nzbget in state STARTING> (stdout)> 2017-04-24 16:07:29,193 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47081080608168 for <Subprocess at 47081066986384 with name nzbget in state STARTING> (stderr)> 2017-04-24 16:07:29,193 INFO exited: nzbget (exit status 127; not expected) 2017-04-24 16:07:29,193 DEBG received SIGCLD indicating a child quit 2017-04-24 16:07:31,196 INFO spawned: 'nzbget' with pid 46 2017-04-24 16:07:31,204 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists 2017-04-24 16:07:31,205 DEBG 'nzbget' stderr output: /usr/bin/nzbget: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory 2017-04-24 16:07:31,206 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47081067029496 for <Subprocess at 47081066986384 with name nzbget in state STARTING> (stdout)> 2017-04-24 16:07:31,206 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47081080608384 for <Subprocess at 47081066986384 with name nzbget in state STARTING> (stderr)> 2017-04-24 16:07:31,206 INFO exited: nzbget (exit status 127; not expected) 2017-04-24 16:07:31,206 DEBG received SIGCLD indicating a child quit 2017-04-24 16:07:34,211 INFO spawned: 'nzbget' with pid 49 2017-04-24 16:07:34,224 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists 2017-04-24 16:07:34,225 DEBG 'nzbget' stderr output: /usr/bin/nzbget: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory 2017-04-24 16:07:34,225 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47081067029496 for <Subprocess at 47081066986384 with name nzbget in state STARTING> (stdout)> 2017-04-24 16:07:34,225 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47081080608168 for <Subprocess at 47081066986384 with name nzbget in state STARTING> (stderr)> 2017-04-24 16:07:34,226 INFO exited: nzbget (exit status 127; not expected) 2017-04-24 16:07:34,226 DEBG received SIGCLD indicating a child quit 2017-04-24 16:07:34,226 INFO gave up: nzbget entered FATAL state, too many start retries too quickly
-
Hi, Great to have this in a docker, any chance you can update to v1.6.1? Thanks Henry