Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

joelones

Members
  • Joined

  • Last visited

Everything posted by joelones

  1. I do not seem to have the addonupdate in my guisettings. Should I add it? Are you kidding me? Makes no difference, still won't work... If it were that simple, we'd have fixed it, the issue is intermittent, so some people think they have fixed it, but it makes no difference.... Makes plently difference, hasn't seg faulted once since I've made the change. But as I mentioned, I did copy over the Addons20.db from my 16.1 Mac OS X install and then made the change in guisettings. http://forum.kodi.tv/showthread.php?tid=212061&page=24
  2. Maybe I'm missing something, but it seems you are inputting "kodi" as a username in sonarr, correct? First off, the default user/pass in the advancedsettings.xml is xbmc: <webserverpassword>xbmc</webserverpassword> <webserverusername>xbmc</webserverusername> Secondly, concerning the seg faults, I got the docker to stop crashing by copying Addons20.db from my 16.1 Mac OS X box (perhaps you can get it from another build) and set the below to 2 in guisettings.xml to prevent addon updates: <addonupdates>2</addonupdates> It's worth a try before exploring other alternatives. However, I do like the VM option as well.
  3. I'm also using the S3 sleep plugin, prior to 6.2 it was working well. Upgraded my AMD FX based server and now notice sleeping the server is fine, no issues, but on wake (WOL) the GUI becomes inaccessible. Not sure if this is related to the plugin or not, any thoughts? I do have network access once awake but see nothing in the log.
  4. You could try my workaround in the meantime, it's been solid for me. https://lime-technology.com/forum/index.php?topic=42439.msg494193#msg494193
  5. So the segmentation fault bug with the addons file is fixed ?
  6. Forgive me for posting this in the preclear thread. Woke up this morning with a nice email saying that my parity drive reallocated sector ct went to 50. Fast forward to this afternoon and a couple more emails later, it's now up to 56. Suffice it to say, a new drive is on the way, but the way things are headed, the drive will probably fail before then. I disabled monthly parity check for Sept. tonight. Firstly, I never had to deal with a bad parity, so any guidance would be appreciated. Worst case scenario, drive dies, I'm assuming unRAID can manage without a parity? Second, because it's a parity, I'm assuming any data is unreadable when I RMA it back to Toshiba? No need to zero data prior? Event: unRAID Parity disk SMART health [5] Subject: Warning [Tower] - reallocated sector ct is 55 Description: TOSHIBA_DT01ACA300_XXX(sdj) Importance: warning 1 Raw read error rate 0x000b 098 098 016 Pre-fail Always Never 4 2 Throughput performance 0x0005 139 139 054 Pre-fail Offline Never 73 3 Spin up time 0x0007 133 133 024 Pre-fail Always Never 431 (average 430) 4 Start stop count 0x0012 099 099 000 Old age Always Never 4251 5 Reallocated sector count 0x0033 100 100 005 Pre-fail Always Never 56 7 Seek error rate 0x000b 100 100 067 Pre-fail Always Never 0 8 Seek time performance 0x0005 124 124 020 Pre-fail Offline Never 33 9 Power on hours 0x0012 098 098 000 Old age Always Never 17775 (2y, 9d, 15h) 10 Spin retry count 0x0013 100 100 060 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 000 Old age Always Never 27 192 Power-off retract count 0x0032 097 097 000 Old age Always Never 4263 193 Load cycle count 0x0012 097 097 000 Old age Always Never 4263 194 Temperature celsius 0x0002 181 181 000 Old age Always Never 33 (min/max 19/48) 196 Reallocated event count 0x0032 100 100 000 Old age Always Never 60 197 Current pending sector 0x0022 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0008 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x000a 200 200 000 Old age Always Never 0
  7. I added mirrors.kodi.tv to the hosts file and reinstalled the docker, appears to still be crashing on my end ./run: line 2: 299 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless Oh it seems to still be grabbing addons.xml.gz from different mirrors. 09:14:27 T:47314506884864 DEBUG: CurlFile::Open(0x2b0844601460) http://mirrors.kodi.tv/addons/jarvis/addons.xml.gz 09:14:28 T:47314506884864 DEBUG: CCurlFile::Open - effective URL: <http://ftp.halifax.rwth-aachen.de/xbmc/addons/jarvis/addons.xml.gz> 09:14:29 T:47314506884864 DEBUG: CRepository 'http://mirrors.kodi.tv/addons/jarvis/addons.xml.gz' is gzip. decompressing EDIT: I got it to finally stop crashing by copying Addons20.db from my 16.1 Mac OS X box. Not pretty, but for now it'll do. EDIT 2: Guess I was wrong, was up for a couple of hours and it appears to still want to download addons.xml.gz EDIT 3: I set the below to 2 in guisettings.xml to prevent addon updates, better now <addonupdates>2</addonupdates>
  8. thanks for the update sparklyballs, hopefully this widespread an issue gets remedied quickly. is this bug being tracked, can't seem to find reference to this particular segfault?
  9. Just to clarify you mean for me to try to delete the docker.img or leaping out of the nearest window? Well I can rule out the docker.img stuff here.... If you need me to try, I can. However, since you mentioned that you were able reproduce the error, I have not tried. I have quite a few dockers to recreate, if you can quickly rule the docker.img that'll be swell.
  10. Just to clarify you mean for me to try to delete the docker.img or leap out of the nearest window as a possible solution? lol, will report back.
  11. Glad it not isolated to me, I was going to leap out of the nearest window...
  12. running docker logs container gives me segmentation faults...which is probably what's causing the restarts, as to why...btw running unraid in esxi, not like that should matter *** Running /etc/my_init.d/999_advanced_script.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 285 ./run: line 2: 296 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 321 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 344 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 366 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 388 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 410 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 432 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 454 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 476 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 498 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 520 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 542 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 564 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless *** Shutting down runit daemon (PID 285)... *** Killing all processes... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/05_set_the_time.sh... *** Running /etc/my_init.d/10_add_user_abc.sh... *** Running /etc/my_init.d/20_apt_update.sh... Getting list of mirrors...done. Testing latency to mirror(s) [13/13] 100% Getting list of launchpad URLs...done. Looking up 3 status(es) [3/3] 100% ubuntu.mirror.iweb.ca (current) is the currently used mirror. Skipping file generation *** Running /etc/my_init.d/30_set_the_config.sh... *** Running /etc/my_init.d/40_update.sh... --2016-08-25 14:59:09-- https://files.linuxserver.io/kodi/LATEST16 Resolving files.linuxserver.io (files.linuxserver.io)... 104.18.61.43, 104.18.60.43 Connecting to files.linuxserver.io (files.linuxserver.io)|104.18.61.43|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 36 Saving to: ‘/tmp/LATEST’ 0K 100% 10.5M=0s 2016-08-25 14:59:10 (10.5 MB/s) - ‘/tmp/LATEST’ saved [36/36] *** Running /etc/my_init.d/999_advanced_script.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 80 ./run: line 2: 92 Killed /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 95 Killed /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless ./run: line 2: 97 Killed /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless I also put my advancesettings.xml file in userdata, not sure if it's related. Now it's topping my cpu. What on earth is happening :'( I also nuked another container which I assume was also using the same base image(s). will try again with default advancesettings.xml EDIT: still getting ./run: line 2: 296 Segmentation fault /sbin/setuser abc /usr/local/lib/kodi/kodi.bin --headless syslog Aug 25 15:25:23 tower kernel: JobWorker[4812]: segfault at 4c0 ip 00000000009c0cc7 sp 00002af96bc50730 error 4 in kodi.bin[400000+1da6000] I'm going wipe the docker.img at this point, I guess my user templates will stay intact... kodi.old.log.zip
  13. Clean install, nuked everything. Default advancesettings.xml, Still restarts. ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- finding fastest mirror 1. ubuntu.mirror.iweb.ca Latency: 8.51 ms Org: iWeb Technologies Inc. Status: Up to date Speed: 4 Gbps 2. mirror.cedille.club Latency: 19.00 ms Org: Club CEDILLE Status: Up to date Speed: 100 Mbps 3. archive.ubuntu.mirror.rafal.ca Latency: 20.22 ms Org: Rafa? Rzeczkowski Status: Up to date Speed: 1 Gbps New config file saved to /defaults/sources.list We are now refreshing packages from apt repositories, this *may* take a while Get:1 http://ppa.launchpad.net trusty InRelease [15.5 kB] Get:2 http://ppa.launchpad.net trusty InRelease [15.4 kB] Get:3 http://ppa.launchpad.net trusty/main amd64 Packages [2,941 B] Get:4 http://ppa.launchpad.net trusty/main amd64 Packages [29.5 kB] ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- finding fastest mirror 1. ubuntu.mirror.iweb.ca Latency: 8.51 ms Org: iWeb Technologies Inc. Status: Up to date Speed: 4 Gbps 2. mirror.cedille.club Latency: 19.00 ms Org: Club CEDILLE Status: Up to date Speed: 100 Mbps 3. archive.ubuntu.mirror.rafal.ca Latency: 20.22 ms Org: Rafa? Rzeczkowski Status: Up to date Speed: 1 Gbps New config file saved to /defaults/sources.list We are now refreshing packages from apt repositories, this *may* take a while Get:1 http://ppa.launchpad.net trusty InRelease [15.5 kB] Get:2 http://ppa.launchpad.net trusty InRelease [15.4 kB] Get:3 http://ppa.launchpad.net trusty/main amd64 Packages [2,941 B] Get:4 http://ppa.launchpad.net trusty/main amd64 Packages [29.5 kB] Ign http://ubuntu.mirror.iweb.ca trusty InRelease Get:5 http://ubuntu.mirror.iweb.ca trusty-updates InRelease [65.9 kB] Get:6 http://ubuntu.mirror.iweb.ca trusty-security InRelease [65.9 kB] Get:7 http://ubuntu.mirror.iweb.ca trusty Release.gpg [933 B] Get:8 http://ubuntu.mirror.iweb.ca trusty-updates/main Sources [470 kB] Get:9 http://ubuntu.mirror.iweb.ca trusty-updates/restricted Sources [5,217 B] Get:10 http://ubuntu.mirror.iweb.ca trusty-updates/universe Sources [201 kB] Get:11 http://ubuntu.mirror.iweb.ca trusty-updates/multiverse Sources [5,946 B] Get:12 http://ubuntu.mirror.iweb.ca trusty-updates/main amd64 Packages [1,097 kB] Get:13 http://ubuntu.mirror.iweb.ca trusty-updates/restricted amd64 Packages [23.5 kB] Get:14 http://ubuntu.mirror.iweb.ca trusty-updates/universe amd64 Packages [474 kB] Get:15 http://ubuntu.mirror.iweb.ca trusty-updates/multiverse amd64 Packages [14.3 kB] Get:16 http://ubuntu.mirror.iweb.ca trusty-security/main Sources [150 kB] Get:17 http://ubuntu.mirror.iweb.ca trusty-security/restricted Sources [3,920 B] Get:18 http://ubuntu.mirror.iweb.ca trusty-security/universe Sources [44.1 kB] Get:19 http://ubuntu.mirror.iweb.ca trusty-security/multiverse Sources [2,550 B] Get:20 http://ubuntu.mirror.iweb.ca trusty-security/main amd64 Packages [638 kB] Get:21 http://ubuntu.mirror.iweb.ca trusty-security/restricted amd64 Packages [20.2 kB] Get:22 http://ubuntu.mirror.iweb.ca trusty-security/universe amd64 Packages [170 kB] Get:23 http://ubuntu.mirror.iweb.ca trusty-security/multiverse amd64 Packages [4,850 B] Get:24 http://ubuntu.mirror.iweb.ca trusty Release [58.5 kB] Get:25 http://ubuntu.mirror.iweb.ca trusty/main Sources [1,335 kB] Get:26 http://ubuntu.mirror.iweb.ca trusty/restricted Sources [5,335 B] Get:27 http://ubuntu.mirror.iweb.ca trusty/universe Sources [7,926 kB] Get:28 http://ubuntu.mirror.iweb.ca trusty/multiverse Sources [211 kB] Get:29 http://ubuntu.mirror.iweb.ca trusty/main amd64 Packages [1,743 kB] Get:30 http://ubuntu.mirror.iweb.ca trusty/restricted amd64 Packages [16.0 kB] Get:31 http://ubuntu.mirror.iweb.ca trusty/universe amd64 Packages [7,589 kB] Get:32 http://ubuntu.mirror.iweb.ca trusty/multiverse amd64 Packages [169 kB] Fetched 22.6 MB in 17s (1,311 kB/s) Reading package lists... (Reading database ... 27276 files and directories currently installed.) Preparing to unpack .../python2.7-dev_2.7.12-1~trusty1_amd64.deb ... Unpacking python2.7-dev (2.7.12-1~trusty1) over (2.7.11-0+trusty1) ... Preparing to unpack .../libpython2.7-dev_2.7.12-1~trusty1_amd64.deb ... Unpacking libpython2.7-dev:amd64 (2.7.12-1~trusty1) over (2.7.11-0+trusty1) ... Preparing to unpack .../python2.7_2.7.12-1~trusty1_amd64.deb ... Unpacking python2.7 (2.7.12-1~trusty1) over (2.7.11-0+trusty1) ... Preparing to unpack .../python2.7-minimal_2.7.12-1~trusty1_amd64.deb ... Unpacking python2.7-minimal (2.7.12-1~trusty1) over (2.7.11-0+trusty1) ... Preparing to unpack .../libpython2.7-minimal_2.7.12-1~trusty1_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.12-1~trusty1) over (2.7.11-0+trusty1) ... Preparing to unpack .../libpython2.7_2.7.12-1~trusty1_amd64.deb ... Unpacking libpython2.7:amd64 (2.7.12-1~trusty1) over (2.7.11-0+trusty1) ... Preparing to unpack .../libpython2.7-stdlib_2.7.12-1~trusty1_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.12-1~trusty1) over (2.7.11-0+trusty1) ... Preparing to unpack .../wget_1.15-1ubuntu1.14.04.2_amd64.deb ... Unpacking wget (1.15-1ubuntu1.14.04.2) over (1.15-1ubuntu1.14.04.1) ... Preparing to unpack .../python-pip_1.5.4-1ubuntu4_all.deb ... Unpacking python-pip (1.5.4-1ubuntu4) over (1.5.4-1ubuntu3) ... Preparing to unpack .../python-pip-whl_1.5.4-1ubuntu4_all.deb ... Unpacking python-pip-whl (1.5.4-1ubuntu4) over (1.5.4-1ubuntu3) ... Processing triggers for mime-support (3.54ubuntu1.1) ... Setting up libpython2.7-minimal:amd64 (2.7.12-1~trusty1) ... Setting up python2.7-minimal (2.7.12-1~trusty1) ... Setting up libpython2.7-stdlib:amd64 (2.7.12-1~trusty1) ... Setting up python2.7 (2.7.12-1~trusty1) ... Setting up libpython2.7:amd64 (2.7.12-1~trusty1) ... Setting up libpython2.7-dev:amd64 (2.7.12-1~trusty1) ... Setting up python2.7-dev (2.7.12-1~trusty1) ... Setting up wget (1.15-1ubuntu1.14.04.2) ... Setting up python-pip-whl (1.5.4-1ubuntu4) ... Setting up python-pip (1.5.4-1ubuntu4) ... Processing triggers for libc-bin (2.19-0ubuntu6.7) ... No Update Required Aug 25 14:53:16 de6ce92bb863 syslog-ng[292]: syslog-ng starting up; version='3.5.3' root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="kodi-headless" --net="bridge" -e PUID="99" -e PGID="100" -e VERSION="16" -e TZ="America/New_York" -p 8080:8080/tcp -p 9777:9777/udp -v "/mnt/cache/appdata/docker/kodi-headless":"/config/.kodi":rw linuxserver/kodi-headless kodi.old.log.zip
  14. Started from an empty appdata, I also tried a new mariadb container as well, with empty databases. The log stops at the following for some reason and then the server restarts... CRepository 'http://mirrors.kodi.tv/addons/jarvis/addons.xml.gz' is gzip. decompressing
  15. Thanks for the help, I'm going bonkers here. Up until today I was using sparklyballs docker on ver 14 with no issues. How do I get at the run command from within the interface or shell? Is this what you want to see? I also removed my advancesettings.xml and it still continues to restart itself with the default supplied xml. I see the kodi.log continuously recreate itself with the same data... I increased the log level and attached a log. The stuff in the log file keeps on repeating once it rotates the log over to kodi.old.log kodi.old.log.zip
  16. addons.xml.gz seem to download all right. 2016-08-25 14:01:09 (939 KB/s) - ‘addons.xml.gz’ saved [550529/550529] the headless server refuses to start, docker remains up, telnet 8080 refuses, i see this in docker log Checksum Failed, falling back to original version , try again by restarting the container kodi.log does not show any errors, i then notice kodi.bin topping my cpu, so i know it's bugging somewhere.... anyway to increase the log level in advancesettings?
  17. Having a real hard time here. I noticed the docker keeps on restarting on its own. Mariadb is fine, dbs were empty and I noticed that the docker created the schemas for both videos/music. Added the VERSION = 16 variable was the only change I made to the docker plus the /config/.kodi path. The server keeps on restarting but the docker remains up, can't telnet into 8080 and I noticed the kodi.log keeps on updating with the same info. Tried to delete container and image and restarted and same. Thoughts please. Noticed this now: 12:49:28 T:47541202773760 ERROR: CCurlFile::FillBuffer - Failed: Timeout was reached(28) 12:49:28 T:47541202773760 ERROR: CRepository: Failed to parse addons.xml. Malformated. 12:49:28 T:47541202773760 ERROR: CRepositoryUpdateJob[repository.xbmc.org] failed to read or parse directory 'http://mirrors.kodi.tv/addons/jarvis/addons.xml.gz' 12:50:51 T:47540441307392 NOTICE: Samba is idle. Closing the remaining connections I guessed it timeout on some download or something... Also seeing this: Fetched 22.5 MB in 25s (877 kB/s) Reading package lists... Checksum Failed, falling back to original version , try again by restarting the container Aug 25 13:29:20 0c30efe98b04 syslog-ng[78]: syslog-ng starting up; version='3.5.3' I am going out through a VPN and it could be the the VPN's ip is blacklisted or something preventing me to access the internet during docker start. kodi.old.log.zip
  18. There's a bug with your plugin zeron. When I updated and while still on kernel 4.1.18 it didn't install right. Here's the offending line: elif [ "4.4.15" == "4.1.18" ]; then
  19. I see. Well, the updates apps button didn't work for me as well.
  20. Thanks but's I figure it's a known PIA IP address, which is probably banned for good reason....I guess I'll manually scp the file over to /tmp when I need to use CA, of course I know it won't survive reboots.
  21. Well that confirms it. wget http://tools.linuxserver.io/unraid-docker-templates.json --2016-02-29 15:38:31-- http://tools.linuxserver.io/unraid-docker-templates.json Resolving tools.linuxserver.io (tools.linuxserver.io)... 104.18.60.43, 104.18.61.43 Connecting to tools.linuxserver.io (tools.linuxserver.io)|104.18.60.43|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2016-02-29 15:38:31 ERROR 403: Forbidden. Guess I'll just manually scp the templates.json file in as a workaround. Thanks
  22. What do you mean? Are all the categories empty? Right all categories are empty. Every click brings zero results. Search brings nothing up as well. Don't know what to make of it. Could be my IP (going through a VPN) being blacklisted from wherever CA gets its feed. Only thing I could think of. Where does CA get its data from?
  23. Thoughts on why I am unable to bring up any apps at all, no matter what I select? Probably missing something here. It was working... Version:2016.02.20 Last Change To Appfeed: February 28 2016 12:50 Running 6.1.8
  24. Thanks. I precleared the drive three times and see the pending sectors gone. =========================================================================== ** Changed attributes in files: /tmp/smart_start_sdq /tmp/smart_finish_sdq ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 111 110 6 ok 37282784 Spin_Up_Time = 98 94 0 ok 0 Seek_Error_Rate = 47 46 30 near_thresh 2040135090721 Power_On_Hours = 72 73 0 ok 24538 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Reported_Uncorrect = 96 99 0 ok 4 High_Fly_Writes = 98 99 0 ok 2 Airflow_Temperature_Cel = 63 76 45 near_thresh 37 Load_Cycle_Count = 14 14 0 near_thresh 173170 Temperature_Celsius = 37 24 0 ok 37 No SMART attributes are FAILING_NOW 16 sectors were pending re-allocation before the start of the preclear. 16 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, a change of -16 in the number of sectors pending re-allocation. 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. What worries is that I see this (attached smart report as well: 187 Reported_Uncorrect 0x0032 096 096 000 Old_age Always - 4 sdg.txt
  25. Just got a warning with my parity drive. Warning [TOWER] - current pending sector is 16 I've also never encountered a " Offline_Uncorrectable " smart error as of yet. Thoughts on the next course of action (will firstly swap in a new parity drive) sdj_smart.txt

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.