January 28, 20188 yr If I browse the folders using MV, I can open the folders and files. If I try accessing the folders from windows, I get: "windows cannot access \\tower\disk8\unraid\tv series\xyz folder you do not have permission to access \\tower\disk8\unraid\tv series\xyz folder Contact your network administrator to request access" This message only affects some of the folders I moved, not all of them. Any suggestions appreciated. Unraid version 6.4.0. Edited January 28, 20188 yr by gnollo
January 28, 20188 yr You might want to try running the New Permissions tool in case you ended up changing them when you ran the ‘mv’ command.
January 28, 20188 yr 12 minutes ago, itimpi said: You might want to try running the New Permissions tool in case you ended up changing them when you ran the ‘mv’ command. Would recommend the docker safe new perms though!
January 28, 20188 yr Author 25 minutes ago, itimpi said: You might want to try running the New Permissions tool in case you ended up changing them when you ran the ‘mv’ command. Running now, on all disks and all shares
January 28, 20188 yr Just now, gnollo said: Running now, on all disks and all shares Please tell me that's the docker safe version you're using?
January 28, 20188 yr Author 17 minutes ago, CHBMB said: Please tell me that's the docker safe version you're using? erm no I saw your reply after. Why?
January 28, 20188 yr 3 minutes ago, gnollo said: erm no I saw your reply after. Why? Because the tool you've run will change the permissions on all your docker appdata and can cause absolute mayhem. Nothing you can do about it now. Just check your docker containers still work ok when new perms has finished and if not you'll probably have to restore from a backup.
January 28, 20188 yr Author I should be OK then. I run nothing from the docker, use unraid purely as storage for an Emby server installed on a separate Windows machine
January 28, 20188 yr Just now, gnollo said: I should be OK then. I run nothing from the docker, use unraid purely as storage for an Emby server installed on a separate Windows machine Should be fine then. That's a relief @itimpi Dodged that bullet
January 28, 20188 yr Author mmh didn't realise that by closing the window the process would stop. I need to start it again, can I just select the newly installed drive which has issues (disk8) or do I have to select all drives again?
January 28, 20188 yr I'd just do it on the bit you think has issues, it may not even fix things, but worth a shot.
January 29, 20188 yr Author Well, I don't know if this is connected, but I was rearranging files by moving them from a drive at 95% usage to disk7, which now had space left as I moved some tv series off it to my new drive (drive 8), but I woke up this morning to find drive 7 disabled due to read errors (1536). Any suggestions short of rebuilding the drive after checking connections?
January 29, 20188 yr Wait for @johnnie.black who is the de-facto expert on all things drive failure related before doing anything would be my advice, and post some diagnostics.
January 29, 20188 yr 3 minutes ago, gnollo said: Ok thanks. I'll attache the log file. Make sure you go to Tools - Diagnostics and post the complete diagnostics zip. It includes the syslog and more importantly for your case, includes SMART for all disks.
January 29, 20188 yr Author tower-diagnostics-20180129-1332.zip Here it is Edited January 29, 20188 yr by gnollo
January 29, 20188 yr Disk dropped offline, it could be the disk, a bad cable or the SAS2LP which has known issues with unRAID v6, but since it dropped offline there's no SMART report, so reboot, grab and post new diags.
January 29, 20188 yr Author Rebooted, new diagnostics run and attached tower-diagnostics-20180129-2105.zip
January 29, 20188 yr Disk looks mostly fine, though I would prefer a zero read_raw_error value, recommend running an extended SMART test and if it passes rebuild to the same disk, or a new spare one if you want to play it safer in case there's another failure during the rebuild.
January 29, 20188 yr Author How about I create a new configuration, and assume all drives are good, then check parity (not recalculate). if it passes then I don't need to recreate the drive? http://lime-technology.com/wiki/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily Edited January 29, 20188 yr by gnollo
January 29, 20188 yr If like you described you were moving files when the disk got disabled parity is no longer valid.
January 29, 20188 yr Author gotcha, running an extended smart test result. If it passes I will then - stop the array, - unassign that disk - start the array - stop again, reassign the disk and start array to begin rebuild Is that correct?
January 29, 20188 yr 5 minutes ago, gnollo said: Is that correct? Yes, the emulated disk is mounting but still a good idea to check that contents look correct before rebuilding on top of the old disk.
January 30, 20188 yr Author SMART Extended self test still running after 6 hours, now at 90%, does it normally take that long? The disk is a Western Digita Red WDC WD40EFRX-68WT0N0
Archived
This topic is now archived and is closed to further replies.