gregoryx

Thank you for clarifying.

I'm having similar issues. I removed SF after getting the freeze a couple revs back; then put it back recently only to have the freezes resume. Can someone tell me how to restart emhttp (or whatever might work) when this freeze occurs - so I don't need to do a full reboot? The system is working in every other way. The old "killall emhttp" and "nohup /user/local/emhttp &" does not work on v5 systems.

Success! Formatted again. Copied over RC10 (not RC11). Did make_bootable.bat. Copied over config. Did NOT copy over plugins (only thing in there was SimpleFeatures - can't recall if I copied it over last time). Came up. Rebuilding parity now. At about 95MB per second. Not sure if it was the RC10 versus RC11 or the nth time of reformatting or if I screwed up and restored SimpleFeatures last time. I'll put it all back together one piece at a time after the rebuild. Thank you for the amazingly prompt help.

Ugh. I was feeling all optimistic - of course! reformat! - but no luck. Same results. Formatted the USB key. Copied over RC11 files. Copied over my config files into the config dir. Did make_bootable.bat. Same result. Hmm... try it without the configs?

RC11 was acting weird in the web gui (slow to no response). I couldn't get it to gracefully shut down, so I forced it from the command line (shutdown) and replaced the bzimage and bzroot from RC10 using a Windows PC then rebooted. Nothing. Sits dead after a "Loading Operating System" prompt (which I assume is from the BIOS). I've done the "make_bootable" a couple of times (on the Windows PC) and same results. Rolled back to saved files from the USB in RC8a. Same thing. Not sure what to do next. HELP?

Download not working for me. Is it working for everyone else?

I'm getting these on the latest "RC8" version. How did you resolve this?

Moved from 4.7 to 5.0-rc8a a couple of weeks ago. Finally got the shares issue worked out (replaced the SMB driver thingy - thanks for the help). Now getting to these annoying emails I get every hour. I'm getting emails that look just like the ones I /USED/ to get on 4.7 when the monthly parity resync would run. I think I may have checked / turned on some hourly notification thing when I first loaded 5.0-rc8a, but then I loaded the SimpleFeatures UI and can't figure out where that "hourly notification" thing went. In case that's not the only issue: resync is NOT running (the drives power down) and I've turned off the notification functions I see in the SimpleFeatures UI. Prolly a really simple thing... help?

Well, I'll be... that seems to have worked! Thank you, thank you, thank you! ;D It doesn't seem to be ripping fast or anything... but it seems to be working. I'll test sync'ing up my backups... that's always a good read/write test. Fingers crossed!

Bump. I've re-run the permissions script. I have the same results. On three different machines (one each of XP, Win7, Win8), if I attempt to attach to a share that the user does NOT have rights to, I am unable to attach (as expected). If the user /should/ have rights, I'm able to see the files. If I attempt to WRITE a file, small files succeed (~100K or so) and everything larger fails. I'm not sure where I should be looking or what I should be trying to change at this point.

Thanks for all the help, guys. I'm still having the same issues. I've wiped the users and rebuilt them. I've changed settings in the shares many times. If I set shares so that I should /not/ be able to access them, then reboot the PCs, it acts accordingly. At least in the Win8 system, I don't have to reboot, just kill the connections with net use /delete. What I'm experiencing is very... odd. When attached as a user who /should/ have rights, I can delete or rename any file. I cannot copy a file to the share from a PC. In Win8 and Win7, it does it's "calculating" thing, maybe says "20% progress", then kicks an error about the server not being available ("There is a problem accessing \\unraid1\temp" in Win7). Of course, it is. Occasionally (haven't found a pattern yet), the file then shows as being present in the share and I can see it from another system at that point and it appears to be full size. It is, of course, corrupt / not valid. I can copy a very small file (< 100KB) and it will work. But anything over those small sizes, it does the "calculating" thing, then fails - either with a small "percent complete" on the indicator or not.

dgaschk, I ran the short smart tests the other day and some had stuff reporting, but nothing fatal. the parity is clean. running the long test on the parity drive now. you thinking I should run the short or long? and is there a way to run them on all drives - similar to the way the bubba interface did in 4.7? I assume loading bubba is not the way to go with 5.0...

The output from that first one was... uh... crazy long. Every FILE shows: -rw-rw---- 1 nobody users Every FOLDER shows: drwxrwx 1 nobody users Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes root@UNRAID1:~# ifconfig eth0 Link encap:Ethernet HWaddr 6c:f0:49:e7:58:c8 inet addr:192.168.253.5 Bcast:192.168.253.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:111614 errors:0 dropped:6 overruns:0 frame:0 TX packets:234748 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:17223863 (16.4 MiB) TX bytes:215225435 (205.2 MiB) Interrupt:48 Base address:0x6000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:9 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:646 (646.0 B) TX bytes:646 (646.0 B)

I grabbed this from the "system log" button in the menu. If there's a better / more thorough way, let me know. After reboot (and wandering off with some honey-dos), I started the array and tried unsuccessfully to copy a file from two different PCs using a "public" share called temp. They both failed to write. The XP error is "Cannot copy filename.ext: The specified network name is no longer available. Reading from both clients works great. Quite fast, in fact. syslog_unraid.txt

Thanks, Helmonder. The client machines are using various user names. I've tried with "public" shares (presumably don't need login authorization?) and with users that authenticate on other shares. I say that is's "mostly" because it seems like sometimes I can drop / write a file, but in the rare case that it succeeds it takes a LONG time to get around to doing so. I do not have my cache drive enabled right now. Not sure if that'd have THIS kind of effect.

Did the upgrade. Checked all the disks. Did the permission fix. Recreated the users. Am able to read from shares; but mostly cannot write to them. Restarted the array. Stop/started the array. Restarted the PCs (XP, Win7, and Win8). Did the smb-extra.conf fix found here. Sometimes, it will allow me to copy a file, but ridiculously slow and/or errors. But I can read fast. I've been searching off and on all day... can't find a fix.

Ran into a similar issue with shares not working. Can you confirm that the issue is needing to rerun the new permissions script? I'm guessing it's going to take 20 hours or something like that. If there's a different issue, I'd rather not wait.

Bumping this last question a bit: I have a CyberPower 2200 with an ethernet interface (RMCARD202), which supports SNMP directly. Any chance of getting it to work via SNMP? This link suggests that APCUPSD supports an SNMP configuration: http://osdir.com/ml/sysutils.apcupsd.user/2006-12/msg00002.html But I'm not sure how I'd get the "DEVICE" information described in that post to work with the UnRAID system. Just in case someone brings it up: the UPS port of the UPS is currently plugged into my QNAP; and the Windows PCs run off the CyberPower network software. If my UnRAID system had a serial port on the 'board, I'd just do that. And if no-one has input for this, I'll find a PCI serial option.

WOO-HOO! That did it! You are AWESOME! Thank you! I stopped the array (eventually) and removed the cache drive. Restarted the array and everything was as it should be: shares were all restored. I'm guessing that means the cache drive is corrupt in some way. Probably need to run a check-disk of some sort, I'm guessing? Is that the reiserfsck command? or is the cache not Reiser? Anyone know? Or i can search the wiki... come to think of it.

Hate to be stupid... but I don't know how that got there or how / where to change it. Hmm... I wonder if that's some left-over from back before there was a "hidden" option for the disk and flash shares. I recall changing stuff to try to make them hidden. Dunno. If it's a change I made, it's been years. Either way, that's on the disks, not on the shares, right? And on NFS, not on SMB? How to get the SMB shares back and working again?

I don't know of doing anything to NFS shares. Maybe that's what went wrong? Any ideas what to do? I could be wrong... but I don't recall ever using the NFS shares. I may have tried to use it to backups with my other NAS at some point; but I don't know what config it might have had at this point.

Thanks, Joe. The moron reference was to myself. I was feeling stupid. Rightfully. And sassy. Not rightfully. So... if that's the virtual file system that's crashed and rebooting doesn't help, what to do? It wasn't clear from the syslog what's up? The "disk" shares work. But the ones I built do not. I re-configured to show the shares (they were hidden) and they're easy to attach to from a Windows system now. I took a chance and created a "videos" share to see if it would map back to the top-level "videos" folder(s). It shows in the /mnt/user folder. And it shows when I look at the \\unraid1\ system from a Windows system, but it's empty. And rebooting doesn't seem to change things. I'm happy to rebuild all the shares if that will work; but it didn't with this first test. Something I can do to change that? Uh... I'm stuck. Any other diagnostics I can do or provide?

Adding one more piece here: the "disk*" shares work, BTW. I can get to "\\unraid1\disk1\" and the like from other computers. And the .cfg files are all in the /boot/config/shares/ folder. ugh.

Sorry. I guess I missed the post on "please list each of these things when asking for help or admit that you're a moron." Obviously, I should provide the syslog and mention which version of unRAID. It does seem obvious now that you mention it. And it is in the "please list these things" post. My bad. I admit I didn't even think about the version because if I was on the beta code I would have provided the version and posted in the appropriate forum; but I sort of assumed everyone would be on 4.7 if they're not on the beta. My bad. I'm on 4.7; is there a sub-version I should know about or be able to see somewhere? I have been solid on 4.7 since release; and the only changes (and only shut-downs) since 4.7 release have been to replace drives. The syslog is attached as well - since the latest boot, I think. Maybe I'm not doing it right. Not sure. I have shut down almost all add-ons; but there are a number that appear to be part of the system even though they show in the UnMENU Pkg Manager screen. Again, I'm clueless here; just doing the best I can. ====== On my original track, I was trying to point toward what is and is not working, since I suspect that the user-shares aren't finding the file(s) that make them load. I know from looking at the disks that all the data is there. The rebuild finished and everything says it checks out fine. But I don't understand diddly about how this stuff works from there. There are a couple of posts that talk about how the shares work and what can typically be done when they don't show; though they seem to be oriented around SAB and/or other services running (which are not). I was thinking it might be something similar. I suspect that the issue was caused by the dirty shutdown; which is why I was thinking someone knowledgeable could point me to whatever file may be corrupt to cause this. Since the syslog is here, perhaps you can also look for why the "find" process is having files open and not letting go of them. I have waited tens of minutes for a shutdown, only to watch (with lsof and fuser) the find process keep moving from one file or directory to another. This is something new; I have not had or seen this issue over the last couple of years - though I suspect it is related to the cache drive and/or mover script. Since these are the only files open, I really didn't expect the dirty shutdown to cause a problem. syslog.txt

I have a feeling there's a simple fix to this. But I can't find it in the 'board. I had a drive bomb out. It's old and probably needs replacing, but the SMART doesn't indicate that it's totally dead yet; I think the heat killed it yesterday. I pulled it out of the array, put it back in the array and started the rebuild. All's well there. Only thing that happened while doing that was some "hangs" trying to power off; I hit the "power off" button at one point when it wouldn't shut down. (I think I found a reliable way to do that since - by using the "Stop Array" button in UnMenu's Array Management.) All seemed well with the rebuild... until I went to check the data... and there are no shares accessible from SMB. Okay... that happens, right? Checked the shares under the main menu screen. Not there. Hmmm... I've done this rebuild stuff before. The data is typically available and all is working (if a little slower). Good news is that all the data shows on the drives (telnet in and look in mnt/disk*). Weird thing is that mnt/user is empty; but mnt/user0 has all the shares in it. Is that normal? Is this where the problem is? How to fix it?