Kujo

I'll look into this in the new year once I get my shares cleaned up. Been using Unraid for 8 years, never had any issues before. I didn't realize XFS was recommended.

Update: Good news, third time running rebuild tree was the charm. Drive is back up. Disk check showing no errors now. Next step is to sort through the lost+found folder.

I guess another worst case scenario option would be to try to use a linux data recovery app to try to pull data off the drive?

--rebuild-tree on disk 1 was successful, but disk 4 is not so much. 2 attempts now. Worth running again? Any other options? If I was to replace the drive, could I rebuild via parity and not loose anything? mymediasvr-diagnostics-20191216-1817.zip

i didn't file system check on disk 1. I'm doing that now. I'll report back. I'll do the same for disk 4 again.

I replaced the parity drive with a new 4TB drive as well as disk 1 with a new 4 TB drive as the original disk 1 was having smart disk failures. I followed the steps on the Wiki to replace the parity drive, this completed in about 12.5 errors. I then replaced the disk 1 with the other new 4TB drive. This took just over 10 hours. When I attempted to bring the array back up, disk 4 is now unmountable. This was a surprise as there was never an issue with this disk. I put the array in maintenance mode, and ran a disk check in the gui for disk 4. There were errors and it recommended to run reiserfsck rebuild tree. I did but no change. Not sure how to get of this mess. I've attached the logs and screen shots. Running Unraid 6.6.7. Any help would be appreciated. mymediasvr-diagnostics-20191215-1633.zip

I can confirm that this is still an issue with 6.7.2.

I had the same issue as well. LibreElec 9.02. Also had to downgrade. Wondering if it has anything to due with this change. smb: disable samba auto-register with avahi for now

SMB broken with OpenELEC 9.02 after upgrading to 6.7. No issues connecting to the Unraid SMB shares on other devices. (i.e Windows, Android). Downgrading back to 6.6.7 workaround for now.

This happened to be yesterday. I should have made a backup before updating. I'll do this going forward. Wasn't too big a deal for me to start from scratch again. See my post above for how I solved it. You can try PhAzE's suggestion above as well.

I just figured out a workaround. I edited the "Sonarr.cfg" file, and manually updated the config path.

Running unRAID 5, since latest Sonarr plugin update, can't get to run on cache apps drive. I'm trying to point the config folder to /mnt/cache/apps/Sonarr/config, which has been working fine all this time. After applying the changes, install error occurs. Here is the log: 2016-04-22 13:58:34 [iNFO] *** Apply - Enable Initiated *** 2016-04-22 13:58:34 [iNFO] Stopping Sonarr... 2016-04-22 13:58:34 [iNFO] Stop OK: Not installed 2016-04-22 13:58:35 [iNFO] Updating settings 2016-04-22 13:58:35 [iNFO] Installing Sonarr... 2016-04-22 13:58:36 [iNFO] Updating dependencies 2016-04-22 13:58:36 [iNFO] Dependency install file has correct MD5 2016-04-22 13:58:36 [iNFO] Using /mnt/cache/.PhAzE-Common for dependency directory 2016-04-22 13:58:37 [iNFO] Dependencies updated successfully 2016-04-22 13:58:37 [iNFO] Updating Mono 2016-04-22 13:58:37 [iNFO] Mono install file has correct MD5 2016-04-22 13:58:37 [iNFO] Mono updated successfully 2016-04-22 13:58:37 [iNFO] Updating export file 2016-04-22 13:58:37 [iNFO] Updating shorcut file 2016-04-22 13:58:41 [WARNING] Unable to get latest version from online - Checking USB for any install file 2016-04-22 13:58:41 [ERROR] Install failed: Install file missing I tried uninstalling Sonarr, rebooting, starting from scratch, no dice. Only works if I leave config dir defaults (i.e. RAM installation).

I'm trying to setup sabnzbd to access ipv6 newsservers. I get the following error when trying to connect: My router has been configured for ipv6, and I can connect fine on my Windows box. I've scoured the net, and this forum, but I haven't been able to find anything specific to my issue as of yet. Is there anything special I need to do to configure unraid for ipv6 support?

no need to worry. Yours is not a drive that uses 4k sectors internally. Even then, the only difference is small performance difference if you accessed lots of small files (small being under 1Meg in size in quick succession under lab tests.) For media playing, you would probably not notice any difference since the files are usually MUCH larger than the block size on the disk. If you set the default alignment in the unRAID settings to 4k-aligned then they already are partitioned so the first sector is aligned at a 4k boundary. If you did not yet assign the disks to the array, you can change the partitioning by use of the "-C 64" option of the preclear_disk.sh script. Otherwise, you'll need to un-assign the disks from the array to do anything. (just be aware, clearing the disks will erase any current contents) Joe L. Thanks Joe. The disk are still preclearing (about 25% done). Since there's really no performance hit, I'll probably just leave them as is. Just to clarify, your saying after the preclear jobs have finished, and before signing them to the array, I could run "-C 64" option of the preclear_disk.sh script". Does this command take a significant amount of time to run?

Hi, I've just setup an unraid server for the first time, and I began preclearing 3 Hitachi Deskstar 5K3000 2TB drives. I was following user configuration tutorial, and I unfortunately missed the point about using -A option with version 4.7. I just used "./preclear_disk.sh /dev/sdX". Am I screwed in anyway? Is it necessary to re-preclear the drives with this option? Thanks.