mymy Posted July 4, 2012 Share Posted July 4, 2012 Hello, I had a red ball next to a drive (disk 5) but had no spare drives. As the drive was accessible, I started to copy the files to a free disk (disk eight) on the system. Didn't follow wiki correctly and It created a disk 5 directory on disk 8. Seems like it bombed in the middle and stopped copying. At that time, disk 5 was not accessible by SMB nor the directory "disk 5" on disk 8. So I bought a new drive and started the data rebuild which seemed to work perfectly. However I can still not access disk 5 through SMB with the new drive. In windows diagnostics it says "disk 5" is available but the user account you are logged on with was denied access. All other disks are available through SMB. Any help would be greatly appreciated. Alan Quote Link to comment
Joe L. Posted July 4, 2012 Share Posted July 4, 2012 Hello, I had a red ball next to a drive (disk 5) but had no spare drives. As the drive was accessible, I started to copy the files to a free disk (disk eight) on the system. Didn't follow wiki correctly and It created a disk 5 directory on disk 8. Seems like it bombed in the middle and stopped copying. At that time, disk 5 was not accessible by SMB nor the directory "disk 5" on disk 8. So I bought a new drive and started the data rebuild which seemed to work perfectly. However I can still not access disk 5 through SMB with the new drive. In windows diagnostics it says "disk 5" is available but the user account you are logged on with was denied access. All other disks are available through SMB. Any help would be greatly appreciated. Alan To provide any guidance most of us would need to know which version of unRAID you are running AND see a syslog for analysis. (our psychic skills are not as good as you might think) "bombed in the middle" can be interpreted in many ways... Joe L. Quote Link to comment
mymy Posted July 4, 2012 Author Share Posted July 4, 2012 My bad. Unraid 5.0 beta 11 When I say bombed, the system locked up and forced a reboot so I didn't get a syslog. Attached is the current syslog. Running parity and disk 1 is now showing errors. Wondering if I actually have a Sata add on card problem as opposed to bad disks, though not sure that would cause my inability to access disk 5 as unraid clearly accessed it no problem to re-build the entire disk. Thanks. syslog_0704_mymy.txt Quote Link to comment
mymy Posted July 5, 2012 Author Share Posted July 5, 2012 Solved by running New Permissions from the Utils menu of the Unraid Web GUI. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.