airic499

Bingo, Thanks Squid! Saw the path for the Win.iso and it was right, so assumed..... switched to advanced and fixed the path and it spins right up. A suggestion somewhere in the instructions of better yet in defaults it should end up selecting that. Putting it someplace that won't auto-mount, then hiding that setting under advanced probably isn't the best default. I'll try and dig around and add it to a couple of threads to "be sure and check..."

This one has me stumped. I can install a Windows 10 VM no issues. I get it all configured and it runs fine for a month or two until I need to reboot the overall box. When I do that the VM can no longer see the mnt with the .iso and I get this error, " Cannot access storage file '/mnt/virtio-win-0.1.118-2.iso' (as uid:0, gid:100): No such file or directory " The OS install iso is here: /mnt/user/Win10VM/Windows 10.iso so that matches and the mnt pathway appears correct. The vertio iso is in the same mount directory and shows up fine in the disk devices under the VM config. So I don't think it's a location issue, which pretty much leaves a permissions issue, but I don't really see anyway to configure the permissions and really probably wouldn't know what to set them to if I did? Sure I am making a newbie error somewhere, but just not seeing it. Thanks for any help.

Version 6.2.4 suddenly with same error. Also, if I try to create a new user, they get denied access even though they have permissions for the share. I have 5 Unraid boxes and have run them since V2, so I know my way around here. Never seen this before. Any other ideas? I had tried removing the Windows link and deleting the credentials. No joy, same error here.

Thanks, but I did exactly that. Pulled the drives mounted them on my Mint box. used gparted to remove the partition then even formated to ext3 just to make sure. That is what seems so bizarre, the system seemed to still see them as old disks and somehow fairly successfully rebuilt the array. Another joker is the parity disk is a new disk. I forgot about the preclear switches to do a minimal, I'll try that at least on a couple.

Hey all, the only thing I can find is this topic from 2009; http://lime-technology.com/forum/index.php?topic=4707.msg43096#msg43096 . I had pretty much done exactly this, saved of the .key file, formatted and recreated the USB from scratch. The only exception is I did a delete partition and re-format the disks in another computer, not a pre-clear. The reason for not doing the pre-clear this is an 18 x 3TB backup server and I don't want to wait a month or so to pre-clear that many disks. Plus, these are all reasonably new, well vetted disks, pre-cleared on install and checked routinely. When I re-installed everything, much to my amazement the files were still there. No shares obviously but the files were all there, but owned as Read-only file system. I am assuming I need to re-do a fresh install on the USB again, but is there someway to do a pre-clear that doesn't involve all the write 0's and extensive checking that preclear.sh does? I assumed using gparted to delete the partition and format to a new different FS should have been sufficient? It probably isn't to far beyond me to just edit the preclear script, but I was hoping someone a lot more current or familiar could offer some suggestions. Thanks

Hi, I have tried to do this, but I get a you need permission to perform this action error? Have two boxes both set up same time and as far as I know identically. One I can access the USB one I can't? I assume chmod, but to what? Thanks

Yes, I am thinking there is something just messed up with the drive slot. Unfortunately, it is one of those NORCO 3116 cases, so the power all comes from the same backplane. So I am likely looking at replacing the backplane. F

@dgaschk Yes, I can still get to the data via the share. In fact I plugged the removed "bad" disk into my Linux box and it mounted and passes an extended SMART test. So not worried about the data. In point of fact, this is my backups server, so theoretically there is no good reason not to blow it all away and start over (other than I'm lazy and don't want to copy it all off and back ) I am mostly concerned what is happening with the system overall, and that particular drive slot. I did read one thread that sounded somewhat similar and what seems to have been the "fix" was a new flash drive. Drive is only a bit over a year old, so that doesn't seem likely. I took it out and ran a scandisk, no errors so don't think that is it. So looking for comfort level of getting to root cause of the problem, and then fixing that issue. Again, no expert reading these logs, but it looks to me like the system isn't accepting the "new" drive as having replaced the old drive and then failing with each attempt to restore. To me though if that was the case, then there should be no progress towards rebuilding, but it appears there is progress, just very slow. itimpi's idea of the New command is tempting. I would prefer that it not wipe whatever data is left on existing disks however if someone can let me know for certain there. I do realize that anything from the missing disk that exists only in parity would be lost. But files that exist currently in the existing file structure of the non-problem disks would be preserved correct? Again, thanks for everyone's help!

No replacing red balled disk in existing array. It is the re-build from parity that is taking forever.

Thanks Itimipi, I was looking at that option. It does come with a pretty dire warning though about not to use if failed disk, which is what I have. I should have plenty of room on existing disks, if using that option does in fact, I believe the term is, "trust existing parity" and rebuild from that?

Tried swapping with a second freshly pre-cleared drive and red balled after just a few minutes of rebuild. Checked the original problem drive and it checks out fine on another computer. Starting to think it must be a channel issue. I would like to at this point, just remove that drive slot for the time being. But searching the forum that seems not to be possible? Any suggestions?

Thanks, Yes checked cables and seating first. No problems there. Disk was freshly pre-cleared, so no data to lose, but wouldn't rebuild without format. No idea if that is significant?

Hello all, I see a few topics that are similar, but none quite the same, so pardons if I have missed the solution somewhere. I had a disk red ball on a solid box using version 5.0.2. Spun everything down, replaced the problem drive with a pre-Cleared WD 3TB Green, spun back up everything normal. Started format drive, as normal then the system moved on to the re-build. The problem is the rebuild now shows anticipated completion time 47 days. I have rebooted a couple of times. Checked all the drive connections, so running out of physical things to try. The log is attached. Far from good at reading logs, but I do see error handlers getting repeatedly called. I see a couple of things that catch my attention, but no idea what to do about any of them? Hoping for any help here! Thanks Tower_2_Log.txt

Completing the loop, kudos to itimpi. Reiserfsck did the trick. I was afraid it was going to take about a month to finish, but once it got through the bad sections it wrapped up in about 7 hours. Files are back in share.

Still rapidly increasing in time although blocks are going down. I hope/assume it will rip through things a bit faster at some point? Otherwise it would be a lot faster just to copy to a new share and see if that fixes the bad data.