Spaceherpe

My original drive failed. I replaced it with a brand new drive, fresh out of the box. It was doing parity rebuild, but going at only 200kbps. I replaced the cable, and rebooted. Now it shows drive disabled, contents emulated. I have turned off my parity check in scheduler, to prevent the parity being replaced without the missing files from my failed drive. I don't know why the brand new drive isn't working, nor do I know how to have it rebuild the filesystem. I'm really novice at this stuff.

I haven't done anything. It still says emulating. I don't know how to get the disk to be rebuilt?

The new drive is literally out of the box.

My new drive failed. I had to swap out the cable, but when I restarted it, it says drive emulated

Brand new, fresh out of the box. If I stop the parity rebuild, will it pick back up automatically after I change out the cable? How do you recommend shutting down the server to swap the cable so the parity will pick back up?

UGH! Now I'm getting this on a brand new, right out of the box HD!!! Unraid Disk 1 SMART health [5]: 23-12-2018 18:55 Warning [TOWER] - reallocated sector ct is 12 TOSHIBA_HDWQ140_98G9K0JHFAYG (sde)

News to me. Thanks for educating me! I've been running my server for a few years now, but still consider my self a complete novice. It's great when it works, and when it doesn't...all of you here on this forum help and make it great again! Thank you all!!!

Diagnostics posted in Zip.

tower-diagnostics-20181223-1834.zip

I'm thinking it may be a bad SATA cable. I have a replacement, but am wary of interrupting the rebuild. Also, I am running the diagnostic now. Will post shortly.

So i had a drive fail. Removed the old drive, popped in a new drive and the system began rebuilding the new drive without asking me to format the new drive first. The drive rebuild is going unGodly slow, between 500kbps and 4mbps. I'm worried that if I interrupt the rebuild to format the drive on a separate computer then return the drive for the server to rebuild, it will ignore the parity and not rebuild the drive. Suggestions?

I do still have a rather long ip list, but suspect that is due to the number of people I share with at any given time. I can't confirm if this is the case or not, but that is my suspicion. The system is working fine now, and I have installed updates since reinstalling it from the template, and have not had the same play issues again.

Kgregg, So what I ended up doing was deleting the PLEX Docker and reinstalling it from the template I had previously installed PLEX with. Didn't make any changes to the template. Everything works fine now.

I forgot to mention that I have attempted to use the "remove pluggin" function, each time it says it ran successfully, reloads and the Advanved Button icon returns or the white window that pops up is completely blank. I'm a fairly novice user, so if you have any suggestions, please walk me through it. Thank you!

So I have deleted the file but upon reboot, it returns? I used Krusader to locate all instances and when I go to each location, it either doesn't exist or is a blank folder, that again, when deleted, returns. When using Fix Common Problems application, it says: " advanced.buttons.plg Not Compatible with unRaid version 6.5.2-rc1 The author (or moderators of Community Applications) of the plugin template (https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/advanced.buttons.plg) has specified that this plugin is incompatible with your version of unRaid (6.5.2-rc1). You should uninstall the plugin here: Maximum OS Version: 6.4.0 I'm at a complete loss. I've tried to use the ignore warning option, but each time I reboot, it returns.

I have made multiple attempts to remove Advanced Buttons. Each time, the system says the addon doesn't exist, yet still shows in the refreshed Plugins list. Recommendations?

It is also worth noting that I made no changes to plex other than running the docker update.

After updating to Unraid 6.5.0, I updated my dockers and Plex now shows a ton of port mapping addresses. My shows are now being interrupted on playback. Anyone with an idea on what is happening and how to fix it, please let me know... PlexMediaServer up-to-date host 192.168.1.150:1900/udp192.168.1.150:1900 192.168.1.150:3005/tcp192.168.1.150:3005 192.168.1.150:32400/tcp192.168.1.150:32400 192.168.1.150:32410/udp192.168.1.150:32410 192.168.1.150:32412/udp192.168.1.150:32412 192.168.1.150:32413/udp192.168.1.150:32413 192.168.1.150:32414/udp192.168.1.150:32414 192.168.1.150:32469/tcp192.168.1.150:32469 192.168.1.150:8324/tcp192.168.1.150:8324 /transcode/mnt/user/appdata/PlexMediaServer/ /data/mnt/user/appdata/PlexMediaServer/ /ScubaPlex/mnt/user/ScubaPlex/ /config/mnt/user/appdata/PlexMediaServer

Thank you

Additional question. what is the difference between yes, no, prefer for cache?

Done. Thank you

I am 100% sure that this question has already been asked and answered, but with so many threads, finding it has proven difficult... Anyways, here goes... I am running 3.6.4 due to issues with 3.6.5 and the power down/reboot function looping. That being said, my system consists of 3 (4tb storage) drives, 1 (4tb) parity and 1 (256gb ssd) cache drive. the current settings for my shares have system, appdata and domains in the "prefere" position for the cache drive. all other drives are listed in the "no" position. When I send files to the server wirelessly from another computer they are written directly to the storage discs instead of the cache and moved later by the mover. I am unsure what setting I have incorrectly set that is not allowing added files to be sent to the cache drive and moved later? Lastly, the server is primarily used for my Plex data library. I am afraid to list the plex share in any other configuration for fear of messing something up on the server. Any help with this would be greatly appreciated and thank you for all that you do for the community! Array Devices Device Identification Temp. Reads Writes Errors FS Size Used Free View Parity WDC_WD40EFRX-68N32N0_WD-WCC7K0XNARD3 - 4 TB (sdd) 72 F 265,161 265,384 0 Disk 1 WDC_WD40EFRX-68N32N0_WD-WCC7K3KS33U9 - 4 TB (sdc) 88 F 1,149,841 277,801 0 xfs 4 TB 2.98 TB 1.02 TB Disk 2 WDC_WD40EFRX-68N32N0_WD-WCC7K2EFJ56K - 4 TB (sdb) 90 F 944,833 73,378 0 xfs 4 TB 2.43 TB 1.57 TB Disk 3 WDC_WD40EFRX-68N32N0_WD-WCC7K6XATD2R - 4 TB (sde) 84 F 85,488 55 0 xfs 4 TB 2 TB 2 TB Total Array of four devices 83 F 2,445,323 616,618 0 12.0 TB 7.41 TB 4.59 TB Cache Devices Device Identification Temp. Reads Writes Errors FS Size Used Free View Cache SAMSUNG_470_Series_SSD_S0MTNEAB502605 - 256 GB (sdf) 84 F 499,421 2,658,477 0 btrfs 256 GB 16.4 GB 240 GB Boot Device Device Identification Temp. Reads Writes Errors FS Size Used Free View Flash v125w - 4.01 GB (sda) * 342 84 0 vfat 4 GB 176 MB 3.83 GB tower-diagnostics-20180105-2328.zip

My SSD is my Cache drive.

so, I am really a noob when it comes to this. My friend set up the server for me. I just use it for my Plex Library at home and with friends. As far as starting the server, I'm really lost. I was able to reduce the number of drives available down to just one slot more than the number of drives I have. I don't know how to do what you are recommending.

My Docker screen has gone completely blank. Like no buttons no previously downloaded Dockers, just a blank screen. Below is a cut/paste of the log, which shows tons of errors. I attempted to revert from 6.3.5 back to 6.3.4 due to the reboot and stability issues and followed Squid's directions on another post to revert, then my docker page disappeared. Additionally, when I go to download new plugins, any Docker plugins are in red with "Docker Not Enabled" in bold red letters. I run a PLEX Server and have temporarily added a plugin, but I need my dockers back to reestablish my Plex Docker and Krusader. Any help would be greatly appreciated. Dec 28 01:09:55 Tower root: truncate: cannot open '/mnt/disk10/system/docker/docker.img' for writing: No such file or directory Dec 28 01:09:55 Tower root: mount: /mnt/disk10/system/docker/docker.img: failed to setup loop device: No such file or directory Dec 28 01:09:55 Tower root: mount error Dec 28 01:09:55 Tower emhttp: err: shcmd: shcmd (256): exit status: 1 Dec 28 01:09:56 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:09:56 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:09:56 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:09:56 Tower shfs/user: err: shfs_readdir: fstatat: domains (5) Input/output error Dec 28 01:09:56 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:09:56 Tower root: Fix Common Problems Version 2017.12.11a Dec 28 01:09:57 Tower shfs/user: err: shfs_readdir: fstatat: domains (5) Input/output error Dec 28 01:09:57 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:06 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:06 Tower shfs/user: err: shfs_readdir: fstatat: domains (5) Input/output error Dec 28 01:10:06 Tower emhttp: err: get_filesystem_status: scandir: Input/output error Dec 28 01:10:06 Tower emhttp: shcmd (270): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/user0/system/docker/docker.img' /var/lib/docker 20 |& logger Dec 28 01:10:06 Tower root: truncate: cannot open '/mnt/disk10/system/docker/docker.img' for writing: No such file or directory Dec 28 01:10:06 Tower root: mount: /mnt/disk10/system/docker/docker.img: failed to setup loop device: No such file or directory Dec 28 01:10:06 Tower root: mount error Dec 28 01:10:06 Tower emhttp: err: shcmd: shcmd (270): exit status: 1 Dec 28 01:10:06 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:06 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:06 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:06 Tower root: Fix Common Problems Version 2017.12.11a Dec 28 01:10:07 Tower shfs/user: err: shfs_readdir: fstatat: domains (5) Input/output error Dec 28 01:10:07 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:17 Tower shfs/user: err: shfs_readdir: fstatat: domains (5) Input/output error Dec 28 01:10:17 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:30 Tower shfs/user: err: shfs_readdir: fstatat: domains (5) Input/output error Dec 28 01:10:30 Tower emhttp: err: get_filesystem_status: scandir: Input/output error Dec 28 01:10:30 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:30 Tower emhttp: shcmd (284): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/user0/system/docker/docker.img' /var/lib/docker 20 |& logger Dec 28 01:10:30 Tower root: truncate: cannot open '/mnt/disk10/system/docker/docker.img' for writing: No such file or directory Dec 28 01:10:30 Tower root: mount: /mnt/disk10/system/docker/docker.img: failed to setup loop device: No such file or directory Dec 28 01:10:30 Tower root: mount error Dec 28 01:10:30 Tower emhttp: err: shcmd: shcmd (284): exit status: 1 Dec 28 01:10:30 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:30 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440 Dec 28 01:10:30 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 24854528 wanted 2465 found 2440