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.

Thanks, itimpi. I put the array into Maintenance Mode. Telnetted in and typed reiserfsck /dev/md10 where is 10 is the replaced red balled drive. Got an reiserfsck message and it said type Yes to continue. I got the following returned after various steps. Looking up this flag now for syntax to run. finished 3 found corruptions can be fixed only when running with --rebuild-tree ...update, running with --rebuild-tree. Running hopefully things will get better shows 30,000 seconds (some 500 hours) remaining and rapidly increasing not decreasing.

Thanks, yes I have it. As noted, the problem disk is removed from the box. It red balled and I replaced. I can stick it on the separate box and run reiserfsck check, if I need to salvage the files. But, this is my backup server so not worried too much about losing files, just don't want to re-coy 12 TB if I don't have too. So far though, all the files appear to be fine, just not mounted into the share. So the question is how do I get them back into the share? Alternatives are, add them to a new share, and remove them from the original so I can delete, or just blow away the old share? Second thought, looking at MC to see if I can copy to a new share that I have created. But the question is I see disks and can drill down to folders using MC, but not shares. I assume I need to navigate someplace other than mnt? Suggestions if that is a good or bad idea and if good where to copy files to. Thanks all.

Using 5.0 ver 16c. Had a disk red ball. No problem, always have a pre-cleared disk ready to go. Spun the array down, replaced disk, spin up, blue ball , re build array, re-do parity check no errors, no problems. Go to access files from share and the share is empty. Mandatory panic attack, start checking individual disks, and everything is there and fine. Check other shares, all fine, just this one. Ok several searches here have suggested re-setting the ownership, so did that. Nothing. Other threads parity re-check. Again nothing. Cold restart, well several times in the process, but hey one more time, nothing. Ok, maybe I can just re-copy some of the files into the share see if that helps, nope won't let me. No real specific error just nothing. Try to add a folder to the share and I get this error: Could not find this item This is no longer located in <%3 Null:OpText>. Verify the item's location and try again. Ok at least an error message, but no ideas what to do. Probably wasn't the wisest thing to do, but tried to delete the share but it wouldn't let me. No error, but acted like when you try to delete a non-empty share (which I presume is exactly what it is). The share shows some or all of files in cache. Checked cache drive as others have indicated and nothing there. Can I turn off cache on this share and re-boot? No real need for cache as this is strictly a backup directory. I can go earlier, but here is the pertinent part of the log in the .txt file. The share in question is the movie iso backup one that is throwing the permission errors shown below. Sep 15 09:24:23 Tower2 emhttp: shcmd (94): /usr/local/sbin/emhttp_event disks_mounted Sep 15 09:24:23 Tower2 emhttp_event: disks_mounted Sep 15 09:24:23 Tower2 emhttp: shcmd (95): :>/etc/samba/smb-shares.conf Sep 15 09:24:23 Tower2 emhttp: shcmd (96): cp /etc/exports- /etc/exports Sep 15 09:24:23 Tower2 emhttp: shcmd (97): cp /etc/netatalk/AppleVolumes.default- /etc/netatalk/AppleVolumes.default Sep 15 09:24:23 Tower2 emhttp: Restart SMB... Sep 15 09:24:23 Tower2 emhttp: shcmd (98): killall -HUP smbd Sep 15 09:24:23 Tower2 emhttp: shcmd (99): ps axc | grep -q rpc.mountd Sep 15 09:24:23 Tower2 emhttp: Restart NFS... Sep 15 09:24:23 Tower2 emhttp: shcmd (100): exportfs -ra |& logger Sep 15 09:24:23 Tower2 emhttp: Restart AFP... Sep 15 09:24:23 Tower2 emhttp: shcmd (101): killall -HUP afpd Sep 15 09:24:23 Tower2 emhttp: shcmd (102): /usr/local/sbin/emhttp_event svcs_restarted Sep 15 09:24:23 Tower2 emhttp_event: svcs_restarted Sep 15 09:25:34 Tower2 afpd[1814]: dsi_tcp_open: invalid header Sep 15 09:26:03 Tower2 shfs/user: shfs_readdir: fstatat: Drama (13) Permission denied Sep 15 09:26:03 Tower2 shfs/user: shfs_readdir: readdir_r: /mnt/disk10/Movie ISO Backup (13) Permission denied Sep 15 09:26:03 Tower2 shfs/user: shfs_readdir: fstatat: Drama (13) Permission denied Sep 15 09:26:03 Tower2 shfs/user: shfs_readdir: readdir_r: /mnt/disk10/Movie ISO Backup (13) Permission denied Sep 15 09:26:03 Tower2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 3 Sep 15 09:26:03 Tower2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 359209748. Fsck? Sep 15 09:26:03 Tower2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [15288 15289 0x0 SD] Sep 15 09:26:03 Tower2 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 3 Sep 15 09:26:03 Tower2 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 359209748. Fsck? Sep 15 09:26:03 Tower2 kernel: REISERFS error (device md10): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [15288 15289 0x0 SD] Sep 15 09:30:35 Tower2 afpd[1862]: dsi_tcp_open: invalid header Sep 15 09:35:35 Tower2 afpd[1863]: dsi_tcp_open: invalid header Tower2_Log.txt

Any thoughts on this card? Fujitsu D56622-307 SAS Looks like decent card for SAS on systems with an abundance of PCI slots and limited PCIe, but Google has not been my friend finding much info. Looks like it defaults to JBOD so that shouldn't be an issue and the real question is will one of the default drivers work, or what are the chances of finding an add in. Obviously, anyone with experience good or bad would be a great help!

Obviously a super minor thing, but I have noticed that with 3 different 15a installs the scree doesn't blank/sleep. All SuperMicro on board video.

@OGI, not at all dumb. One of the first things I tried. Finally got a new set of backplanes, still the green ones, but everything fired right up just fine now. Next problem is drives run awfully hot. Repopulating the RAID with backup files and most are over 42 and a couple at 47. Think I saw some suggested fan replacements. Have to be quieter, even if not cooler.

Thanks, but I've tried two high end Corsair 750W PS's and a solid generic 650, all 3 of which work fine in other builds. Pretty sure it isn't the PS. WIth all the backplane warnings here, I am pretty sure it is the backplane, I just wanted to make sure I wasn't missing something as there is no manual with the Norco and for instance I didn't know that you only needed to power one connector per backplane.

I just wanted to check if I was missing something on the power supply with a Norco 4224. Using the same high end Corsair PS from my old box, (and a decent generic just to try something else). If I everything fires up until I plug any of the molex plugs into the backplanes. Only 1 plug per backplane, in fact I have tried just one plug to backplane 1, then 1 plug to backplane 2 etc. Anything plugged into the backplanes prevents the computer from powering up. Get a momentary fan spin then off. Sounds like it is bad backplanes as noted previously, but I was hoping someone could point out any obvious errors I might be making. Thanks!

Thanks all, Probably would have easily figured it out. But always nice to get some feedback before learning the hard way on a process that can take more than a day. Someone ought to mention it, but one thing I do appreciate about this forum is that (for the most part ;-), no one shoots Noobs for every question.

Yeah, I steer away from these. Around here we talk about the Seagate COD (click of death). Last year during the drive crunch we were in a situation we had to have something and that was all that was available locally. Violated our own rules and got it. COD right out of the box, and totally gone before burn in finished. Sooner or later I assume they will get this fixed. If they survive the initial few months the seem to work well, but out of the box they seem to have an at best 50:50 shot of surviving.