qwaven

ok great thanks for confirming. Will give it a go. Cheers!

Hi there, Wondering what I should be doing? I have an unraid array with 1 parity drive. Seems there are two drives that are unstable/broken. So I am unable to bring my array up. I don't particularly care about the data on those specific drives. I found a guide from unraid https://wiki.unraid.net/Shrink_array#The_.22Remove_Drives_Then_Rebuild_Parity.22_Method about shrinking the array. So I'd be fine with just removing the drives from the array in order to get the remaining drives back online. I can restore the data from the missing drives another time. What I am wondering is it tells me to remove the drives from being a member of any share. Yet I cannot modify this, since I cannot bring my array up. Is there a way around this? Can I skip this step? "Make sure that the drive or drives you are removing have been removed from any inclusions or exclusions for all shares, including in the global share settings. Shares should be changed from the default of "All" to "Include". This include list should contain only the drives that will be retained." ... ... Or maybe there is a better path I should take? Thoughts?

I had just restored the same data not sure it should have changed during this process, however it was strange that 2 were fine and 1 was not. Anyway will keep in mind if there is a next time. Cheers!

Hi all, Thanks for all the help here. I've done the format and transferred everything back. Weird part (they are docker containers) was that after I copied and started up docker. 2 of 3 containers were running. I ran the updater to pull the new content and then after all my containers were removed again! I'm not understanding what happened here. I re copied over my backup of the docker.img file. My container data was still on drive. And again 2 of 3 containers were running again. The 3rd container possibly has some compatibility issue / more investigation needed but that is out of scope for this thread. I've removed the settings conflicting (still need to check it later) and now all 3 containers are running even after going through an update. No idea what happened the first time around or why it was all removed. Anyway seems like all is working well now. Thanks again! Cheers!

I copied it to another drive as specified to do earlier. I used rsync.

ok I am back at last, upgraded again, and as expected the drive 1 is in the same error state. Just wanted to confirm steps I should be taking. Do I just click the format button at the bottom beside the disk? Anything special I should be doing? After format I copy the data back similar to how I backed up or? Cheers!

so are we thinking there is a drive issue? IE will I be replacing this drive? and if so would it make more sense to do this now before attempting the upgrade again? Cheers!

ok so the downgrade seems to have worked. Is there anything special I should do to backup disk1? or do I just cp -R the appdata and system to another drive?

ok so after stopping and starting the array I do not see anything changed. Attached new diag. Curious though. Can the drive be formatted or replaced and the data restored? Or am I missing something with this. Cheers diagnostics-20210601-1121.zip

Checking the history it looks like there is something that starts monthly. As I am not even sure where to set this it seems like a default setting. Seems I should just cancel it then. Cheers.

It is something it has run on its own. I have not shutdown. Is it perhaps something as a result of the upgrade?

Would it be better to cancel the parity or should I continue to wait? Cheers!

Hi JorgeB, Thanks for the reply. First I got command not found but realized its actually btrfs check .... (should it be useful for anyone else in the future) no - Anyway did this... # btrfs check --clear-space-cache v1 /dev/md1 Opening filesystem to check... Checking filesystem on /dev/md1 UUID: 08428632-0cca-4d98-b643-3bf1dd2f7a34 Free space cache cleared # btrfs check --clear-space-cache v2 /dev/md1 Opening filesystem to check... Checking filesystem on /dev/md1 UUID: 08428632-0cca-4d98-b643-3bf1dd2f7a34 no free space cache v2 to clear After doing this I noticed a message pop up saying its doing a parity check. Not sure if I should cancel this to restart the array or if I should wait? It looks like it was already running for 9 hours and has about 10 hours to complete. The drive in question still shows the same error. Will leave it running unless told otherwise. Cheers!

Ah yes fair point. Attached. Cheers. diagnostics-20210531-1701.zip

Hi Squid thanks a lot for the reply. I am used to another system, was expecting the packages to be updated when the system was updated. Updating the unassigned devices seems to have solved that error. However I am still having the main issue with getting my system working again. My disk 1 is still being listed as "Unmountable: not mounted" which I am believing is why I cannot see any of my docker images. I also cannot locate my app data folder which I am guessing that it would have been on there... I am not clear why its not mountable or what I should be doing about this in order to restore my data. If I switch the drive will my parity drive rebuild? Hoping for some direction. Cheers!

Hi all, Wondering if anyone can help me figure this out. I've run the unraid updater to the latest stable 6.9.2. After the reboot I've noticed my docker now has no containers (had 3) and when I try and browse my appdata share it is showing up empty but the unraid gui says it contains data. I see two things on the main page that seem possible issues but I do not really want to touch anything in case I make things worse. 1. There is a disk that is now listed as unmountable. However my array seems ok? To be clear I am not 100% sure if this was even part of my array before. It looks like it would be some sort of SSD drive which if I had used it, it would only have been some sort of cache type drive. 2. The unnasigned devices plugin I had before is now showing this: Fatal error: Uncaught Error: Call to undefined function _() in /usr/local/emhttp/plugins/dynamix/include/Helpers.php:35 Stack trace: #0 /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php(308): my_scale(120.034123776, NULL) #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 35 DEVICEIDENTIFICATION It was working perfectly fine before the upgrade. Thoughts anyone? Cheers!

Thanks for the quick reply. I tried changing my shares to RO/Slave but this does not appear to have changed anything. Added a new file. It was picked up immediately on my older Plex and nothing happens on the new Plex. If I initiate a manual scan, the new Plex will scan all the media again and then the new file shows up. Cheers

Hi there, I've got docker running a Plex instance. It plays things fine on my local network and generally seems to run fine. I have encountered an issue which I did not encounter on a previous docker Plex install (not unraid based) My issue is that I can't get the media library to update itself. I've got the usual options in Plex set to check for changes to the media library paths etc. I currently have my media paths mapped using unassigned devices / smb share from another file server. The docker image will map to these share paths using access mode RO/Shared. For some reason when new media is put on the share (locally on the other file server) you will see this referenced fine on the share itself. But nothing will update accordingly inside Plex. If I do a manual media scan it will locate the new additions. Wondering if anyone might have any thoughts on how I can resolve this? Would there be some option I've set/not set for the docker container? Is it because I am mapped to a shared drive instead of a local path? Cheers!

Hi trurl, Thanks for the reply. I had not realized the previous apps referenced that. I checked mine and it looks like it should be doable. Thanks for the info, will give that a good next time. Cheers!

Hi there, Thanks for the replies. I've attempted to do the above by moving everything to cache. However I encountered a lot of issues trying to format the "raid" drives. As nothing here was terribly critical I ended up clicking the "new config" option to reset my array config. I rebuilt my array using some other drives from the array and they seem to be working properly in a non-raid1 way. I was able to mount the previous cache drive using unassigned devices and copy my cached data back. However my docker settings were gone. So my question now, is there a way for me to export my entire docker config and image running? It appears that even with caching set to prefer this would not have retained everything needed for docker. I've been re thinking things again and I will likely need to do a new array again so ideally it would be nice if I can retain my docker settings. Thoughts?

Thanks for the reply. Would there be a way I can do this without starting over? Cheers!

Hi johnnie.black, Thanks for the reply. I do have a cache drive but it is a single drive and I have not really done much for it other than create the cache designation. Attaching the diagnostic files. Cheers! diagnostics-20200613-1024.zip

Hi there, So I've recently setup unraid (minimal configs) and I was looking at my drive info. I am now wondering if my 4 drives are actually working as 1 array? I am looking under the drive, under the balance status section. On the first two drives I see something like this: Data, RAID1: total=42.00GiB, used=22.09GiB System, RAID1: total=32.00MiB, used=16.00KiB Metadata, RAID1: total=1.00GiB, used=20.09MiB GlobalReserve, single: total=16.00MiB, used=0.00B What puzzles me is the RAID1 descriptions? I have also noticed that these two drives (Drive 1 and Drive 2) appear to always been Green/online together. Now that could be just by luck but it seems notable given the RAID1 description. I do not recall ever seeing "raid" like options when I set this up. The next two, Drive 3 and Drive 4 are listed: Data, single: total=8.00MiB, used=256.00KiB System, DUP: total=8.00MiB, used=16.00KiB Metadata, DUP: total=1.00GiB, used=112.00KiB GlobalReserve, single: total=16.00MiB, used=0.00B To be clear all 4 drives are supposed to be acting as 1 single array with 1 parity drive (not mentioned above) Hoping someone can help explain what I am seeing here and confirm what I have should be just a simple 4 drive + parity array. I do not desire any sort of RAID 1 mirror if that is in fact what has happened? ...if it is, is there a way to fix this to not be a raid1? edit: attached a screen shot of the two drives. The data usage seems to support the raid1 idea as they look pretty identical. Hoping for some help. Cheers!

Hi there, I'm fairly new with using unraid and cannot seem to get this working no matter what settings I try. I am simply trying to mount a remote share which happens to be on another NAS. I've read many posts about using Unassigned Devices to do this. For the most part is seems like it 'should' work. What I am doing: 1. Going to MAIN and going down to the unassigned devices section, selecting the Add remote SMB/NFS share button. 2. Menu comes up, asks me to choose between linux (I assume this means NFS?) or Windows (SMB) ; I've tried them both but believe the option should be SMB 3. It asks me for the server or to search. If I search it will find my other NAS but for some reason cannot load the shares. If I enter the IP this seems to work better. So I enter the IP Here. 4. It asks for a username, I enter one 5. It asks for a password, I enter one 6. It asks for domain if applicable, its not, I don't enter anything 7. Next it asks for the share or I can search for it. This works fine. Searching and it finds my share which I select. 8. At this point I click done and I am brought back to the MAIN page. 9. I can now see my settings I entered above. Its Green which seems to imply it should be working? ...its not. Notes: The source looks accurate The mount point is there, by default it has my NAS IP_ShareName (for the most part I have left this as-is but sometimes I have attempted to change it) Now the mount button directly beside the above map point is orange/available to click. Clicking this will change it to "mounting...." and then come back to the orange button again ready to click again? Still says mount. There are no details like size etc filled out. Clicking on log is useless, there is literally nothing in it to assist with troubleshooting I am not 100% clear where the mount should be happening but based on what I have found it looks like it should reside under /mnt/disks ? This is an empty directory I tried creating a directory in there with the same name as my mount point. it was removed after hitting the mount button. I have tried two users through the above process. 1 that I have used quite often from a desktop machine and a freshly made user. Both work flawlessly on the desktop machine. I'm at a loss here as to what is the issue or where I can go to try and obtain more details. Anyone have any thoughts that can help me? Thanks a bunch!

I have now enabled this but unfortunately it does not appear to do a ton. Got a little increase but nothing drastic. Except now all the drives are on except just the one required. Will leave it for now and see if it gets better. Anyway thanks for your help.