Joe L. Posted January 14, 2012 Share Posted January 14, 2012 just upgraded from 4.7 to 5.0 beta 14 everything ok but when i want to explore (windows 7) the share i get an error? "location is not accesible. Location can be harddrive on this pc or network. Check disk or connection to network and try again. If you still cant find it, information might be moved or deleted" how do i make this work again? run the fix permissions utility on the Utils tab, AND then reboot the windows machine. Quote Link to comment
skank Posted January 14, 2012 Share Posted January 14, 2012 just upgraded from 4.7 to 5.0 beta 14 everything ok but when i want to explore (windows 7) the share i get an error? "location is not accesible. Location can be harddrive on this pc or network. Check disk or connection to network and try again. If you still cant find it, information might be moved or deleted" how do i make this work again? this is quite urgent Quote Link to comment
skank Posted January 14, 2012 Share Posted January 14, 2012 just upgraded from 4.7 to 5.0 beta 14 everything ok but when i want to explore (windows 7) the share i get an error? "location is not accesible. Location can be harddrive on this pc or network. Check disk or connection to network and try again. If you still cant find it, information might be moved or deleted" how do i make this work again? run the fix permissions utility on the Utils tab, AND then reboot the windows machine. oh reboot windows machine? i ran the fix permissions, and reboot the server, but not the windows machine, ill try that Quote Link to comment
skank Posted January 14, 2012 Share Posted January 14, 2012 just upgraded from 4.7 to 5.0 beta 14 everything ok but when i want to explore (windows 7) the share i get an error? "location is not accesible. Location can be harddrive on this pc or network. Check disk or connection to network and try again. If you still cant find it, information might be moved or deleted" how do i make this work again? run the fix permissions utility on the Utils tab, AND then reboot the windows machine. Worked, thx ! stupid of me... not to reboot windows too Quote Link to comment
crankbearing Posted January 14, 2012 Share Posted January 14, 2012 Hey all, I am getting these ata errors. I know you all talked about it with b12 and I just noticed it in b14 here as well. My saslp is at firmware .21. From google it looks like a kernel bug but nothing really concrete. there are a couple acpi minor issue as well that i am googling with no luck. Jan 14 04:37:52 MEDIASERVER kernel: ata9: sas eh calling libata port error handler (Errors) and a little further down. Jan 14 04:37:52 MEDIASERVER kernel: ata9: sas eh calling libata port error handler (Errors) Jan 14 04:37:52 MEDIASERVER kernel: ata10: sas eh calling libata port error handler (Errors) acpi Jan 14 04:37:52 MEDIASERVER kernel: ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20110623/tbfadt-560) (Minor Issues) Jan 14 04:37:52 MEDIASERVER kernel: ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359) (Errors) just wanting to be sure. Thanks, Dave Quote Link to comment
dimaestro Posted January 15, 2012 Share Posted January 15, 2012 How many of y'all are running AOC-SASLP-MV8? I had issues with prior beta builds, and it has made me slightly twingy about using betas, but I have got the itch to upgrade, and need a newer build to support large drives. (especially after some data corruption - luckily it was on backup items - tough to keep everything backed up tho) So, any AOC-SASLP-MV8 users? What has been your experience with Beta14? Quote Link to comment
Phil C. Posted January 15, 2012 Share Posted January 15, 2012 I'm running AOC-SASLP-MV8 on B14...Only problem I've had is spin down. Doesn't work properly - as in some do, some don't, and it is only somewhat predictable. As far as the data getting pushed out, etc, no problems at all. Quote Link to comment
dimaestro Posted January 15, 2012 Share Posted January 15, 2012 I'm running AOC-SASLP-MV8 on B14...Only problem I've had is spin down. Doesn't work properly - as in some do, some don't, and it is only somewhat predictable. As far as the data getting pushed out, etc, no problems at all. Thanks Phil. In prior builds I had many BLK_EH errors, which caused quite a bit of grief. At least, I think a Thank You is in order. You may have caused me to spend another chunk of money I shouldn't. Quote Link to comment
MikeL Posted January 15, 2012 Share Posted January 15, 2012 I've had my server running since November 29th non stop, and I am using 2 AOC-SASLP-MV8 cards. So far everything is purring along very nicely. How many of y'all are running AOC-SASLP-MV8? I had issues with prior beta builds, and it has made me slightly twingy about using betas, but I have got the itch to upgrade, and need a newer build to support large drives. (especially after some data corruption - luckily it was on backup items - tough to keep everything backed up tho) So, any AOC-SASLP-MV8 users? What has been your experience with Beta14? Quote Link to comment
mrcrlee Posted January 15, 2012 Share Posted January 15, 2012 I'm also running with two AOC-SASLP-MV8 cards on b14 and have been fine for 2.5 weeks. Prior to running b14, I was running b12 and had the BLK_EH errors. I think I have noticed a little bit of issue with spindown, if that issue is where the log reports it has spundown a disk but the disk is not spundown. But I'm wiling to put up with that with no BLK_EH errors. If I go in and figure out which devices are open, and close those opens, the disk will spindown as expected after the spindown timer expires for that given resource. Quote Link to comment
jimmydrac Posted January 15, 2012 Share Posted January 15, 2012 But I'm wiling to put up with that with no BLK_EH errors. If I go in and figure out which devices are open, and close those opens, the disk will spindown as expected after the spindown timer expires for that given resource. How do figure out which devices are open? I am new to unRAID and have a AOC-SASLP-MV8 arriving tomorrow. I would like to use this beta with it so I could have 3TB support. Thanks Jim B Quote Link to comment
mrcrlee Posted January 15, 2012 Share Posted January 15, 2012 How do figure out which devices are open? I am new to unRAID and have a AOC-SASLP-MV8 arriving tomorrow. I would like to use this beta with it so I could have 3TB support. I use the command 'lsof', grepping for /mnt: lsof | grep /mnt It will list shares, drives that are open. Good luck and welcome aboard! Quote Link to comment
gbdesai Posted January 16, 2012 Share Posted January 16, 2012 No joy. It wasn't running and when I restarted it I got this: Jan 10 19:51:59 freenas emhttp: unRAID System Management Utility version 5.0-beta14 Jan 10 19:51:59 freenas emhttp: Copyright (C) 2005-2011, Lime Technology, LLC Jan 10 19:51:59 freenas emhttp: Pro key detected, GUID: 0781-556B-3109-3213ECBXXXX Jan 10 19:51:59 freenas kernel: mdcmd (35): spindown 2 Jan 10 19:52:00 freenas kernel: mdcmd (36): spindown 3 Jan 10 19:52:01 freenas emhttp: rdevName.22 not found Jan 10 19:52:01 freenas emhttp: diskFsStatus.1 not found Jan 10 19:52:01 freenas kernel: emhttp[17085]: segfault at 0 ip b754a760 sp bf9442b0 error 4 in libc-2.11.1.so[b74d1000+15c000] This seems to be some great mystery of the universe. Seems like a dozen of us suddenly started having this problem, but no answers exist. rdevName.22 not found, but I don't know what that means and why it didn't happen for months and suddenly it starts happening. I've disabled everything extra and still have the problem. No one has ideas on how to fix this? Quote Link to comment
peter_sm Posted January 16, 2012 Share Posted January 16, 2012 I have some seg fault error as well, I uninstalled Transmission, and now I don't see these error anymore Quote Link to comment
dgaschk Posted January 16, 2012 Share Posted January 16, 2012 No joy. It wasn't running and when I restarted it I got this: Jan 10 19:51:59 freenas emhttp: unRAID System Management Utility version 5.0-beta14 Jan 10 19:51:59 freenas emhttp: Copyright (C) 2005-2011, Lime Technology, LLC Jan 10 19:51:59 freenas emhttp: Pro key detected, GUID: 0781-556B-3109-3213ECBXXXX Jan 10 19:51:59 freenas kernel: mdcmd (35): spindown 2 Jan 10 19:52:00 freenas kernel: mdcmd (36): spindown 3 Jan 10 19:52:01 freenas emhttp: rdevName.22 not found Jan 10 19:52:01 freenas emhttp: diskFsStatus.1 not found Jan 10 19:52:01 freenas kernel: emhttp[17085]: segfault at 0 ip b754a760 sp bf9442b0 error 4 in libc-2.11.1.so[b74d1000+15c000] This seems to be some great mystery of the universe. Seems like a dozen of us suddenly started having this problem, but no answers exist. rdevName.22 not found, but I don't know what that means and why it didn't happen for months and suddenly it starts happening. I've disabled everything extra and still have the problem. No one has ideas on how to fix this? Test with a clean install. Quote Link to comment
crankbearing Posted January 16, 2012 Share Posted January 16, 2012 Jan 14 04:37:52 MEDIASERVER kernel: ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359) (Errors) Dave I mentioned this error a few threads back, I have found a patch for it and I am wondering if there is an easy way to patch it or is that something Tom has to do. here is the patch that I could find. http://thread.gmane.org/gmane.linux.acpi.devel/51405/focus=51407 rgds, Dave Quote Link to comment
gbdesai Posted January 17, 2012 Share Posted January 17, 2012 No joy. It wasn't running and when I restarted it I got this: Jan 10 19:51:59 freenas emhttp: unRAID System Management Utility version 5.0-beta14 Jan 10 19:51:59 freenas emhttp: Copyright (C) 2005-2011, Lime Technology, LLC Jan 10 19:51:59 freenas emhttp: Pro key detected, GUID: 0781-556B-3109-3213ECBXXXX Jan 10 19:51:59 freenas kernel: mdcmd (35): spindown 2 Jan 10 19:52:00 freenas kernel: mdcmd (36): spindown 3 Jan 10 19:52:01 freenas emhttp: rdevName.22 not found Jan 10 19:52:01 freenas emhttp: diskFsStatus.1 not found Jan 10 19:52:01 freenas kernel: emhttp[17085]: segfault at 0 ip b754a760 sp bf9442b0 error 4 in libc-2.11.1.so[b74d1000+15c000] This seems to be some great mystery of the universe. Seems like a dozen of us suddenly started having this problem, but no answers exist. rdevName.22 not found, but I don't know what that means and why it didn't happen for months and suddenly it starts happening. I've disabled everything extra and still have the problem. No one has ideas on how to fix this? Test with a clean install. Short of purchasing a new license to put on a new USB flash drive, what files can I delete (after making a copy of course) to bring me back to a stock install? I disabled all plugins, auto installs, scripts, etc. already. Quote Link to comment
pantner Posted January 18, 2012 Share Posted January 18, 2012 Short of purchasing a new license to put on a new USB flash drive, what files can I delete (after making a copy of course) to bring me back to a stock install? I disabled all plugins, auto installs, scripts, etc. already. why not just delete the entire USB drive (ie, format) after making a backup and treat it as a fresh install? Quote Link to comment
MikeL Posted January 19, 2012 Share Posted January 19, 2012 Why not just go to flash/config there you will find the pro key, save the key in a safe place then the flash drive can be formatted everything reinstalled, place a copy of the pro key back in the new config folder, and all is good. Short of purchasing a new license to put on a new USB flash drive, what files can I delete (after making a copy of course) to bring me back to a stock install? I disabled all plugins, auto installs, scripts, etc. already. why not just delete the entire USB drive (ie, format) after making a backup and treat it as a fresh install? Quote Link to comment
gbdesai Posted January 19, 2012 Share Posted January 19, 2012 Got it, thanks guys will save my key, reformat, and install again. Quote Link to comment
Interstellar Posted January 19, 2012 Share Posted January 19, 2012 Still getting driver errors: Jan 19 20:00:53 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:01:30 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:01:44 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:01:44 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:02:30 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:03:09 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:03:30 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:04:01 Tower in.telnetd[720]: connect from 192.168.1.5 (192.168.1.5) (Routine) Jan 19 20:04:02 Tower login[721]: invalid password for 'jamescullingham' on '/dev/pts/0' from 'Mac-Pro' (Logins) Jan 19 20:04:05 Tower login[721]: ROOT LOGIN on '/dev/pts/0' from 'Mac-Pro' (Logins) Jan 19 20:04:30 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:05:30 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:06:31 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:06:51 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:07:28 Tower last message repeated 2 times Jan 19 20:07:31 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:07:47 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:08:31 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:08:44 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:09:12 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:09:31 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:10:32 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:11:01 Tower kernel: mdcmd (35): spindown 3 (Routine) Jan 19 20:11:01 Tower kernel: mdcmd (36): spindown 4 (Routine) Jan 19 20:11:32 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:11:50 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:12:29 Tower last message repeated 2 times Jan 19 20:12:32 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:12:51 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:13:32 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:13:41 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:14:32 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:15:32 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:15:58 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:16:32 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:17:32 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:18:33 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:19:15 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:19:27 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:19:33 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:19:51 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:20:16 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:20:33 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:21:28 Tower kernel: r8169 0000:02:00.0: eth0: link up (Network) Jan 19 20:21:34 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter Jan 19 20:22:34 Tower logger: Thu Jan 19 17:43:07 GMT 2012 - Hard Drives active, resetting counter As per previously attached syslog. This isn't right. See: http://mailman.archlinux.org/pipermail/arch-dev-public/2011-June/020672.html And I refer you to b9 and the attempt to fix it in b10. Tom, will b15 fix this again? Cheers Quote Link to comment
crankbearing Posted January 20, 2012 Share Posted January 20, 2012 More bugs that I can see. my board supports 7 Sata 6GB I have 5 3TB WD set to AHCI at 6GB speed unraid boots fine and runs fine but as soon as I try and copy anything over to the server it riddles the sys log with errors to the point I replaced the PSU with a corsair TX650 12V single rail 53 amp supply. 3 sets of the NEW 6GB sata cables including replacing the Asus supplied cables. Tehn finally this mornig I had the board replaced installed it set it up and tried to make a copy at 6GB and no dice errors errors and more errors. 3 pages of them IE - "unrecov data, recov data, eh reset, 0x6 frozen, handshk, "finally eh reset them to sata3 speeds instead of sata 6. I just went into the bios and set the whole controller to sata 3 to stop the errors. I have been all over google looking for some kind of inkling of this being kernel related with no luck. I am going to roll back to 12a and test as well. my only question is I have 5 3TB wd on the motherboards sata ports (A75 amd hudson d-3) and then 2 wd ears 2tb on one saslp would this cause an issue with the over all speeds. The errors when I see them currently are on ata 1 and ata2 parity and disk1 hence the drives that are active as I copying. (3:27pm) just looked at my syslog after copying 15Gb with the bios set to Sata 3 and not a single error. (3:30pm) another 5.05Gb copied with no errors at 3GB rgds, Dave Quote Link to comment
elkay14 Posted January 21, 2012 Share Posted January 21, 2012 That is interesting. However, you'll see little or no difference in copy times between 3Gbps and 6Gbps. Quote Link to comment
dgaschk Posted January 21, 2012 Share Posted January 21, 2012 That is interesting. However, you'll see little or no difference in copy times between 3Gbps and 6Gbps. There should be no difference. The rotating magnetic media is the bottleneck, for which SATA I(1.5GBps) is sufficient. Faster SATA speeds are useful with port extenders where multiple HDD share a single SATA port. Quote Link to comment
crankbearing Posted January 21, 2012 Share Posted January 21, 2012 great, i agre but if it does not make a difference why I am getting the errors. Is the system trying to copy to the drives faster then they can keep up or are the cables useless or is the sata controller the problem. I am parity syncing or checking at 110 to 120MB/s to 70-80MB/s when at the final stages and copying (teracopy) win7 or xp from one server to another at 30-40MB/s AND through 2-1Gb switches currently. I just hate ERRORS in my syslog (minor) or other - Dave 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.