Cessquill

Thanks. Yay, the cache drive spins down on its default setting now. Little things please me.

Just to clarify the release notes (http://lime-technology.com/wiki/index.php?title=UnRAID_Server_Version_5.0-beta_Release_Notes)... Should the last Upgrade heading read "5.0-rc9 through 5.0-rc15a"? (it currently reads "5.0-rc9 through 5.0-rc1")

Can confirm that a cache drive without its default settings changed does not spin down (mentioned in RC15 thread). No plugins, not using the cache for anything else. Settings: Spin down delay: Use default Share type: SMB Export: Yes (hidden) Security: Public All disk settings left at default

the flag file unraidsafemode not yet in 15a, but you'll be able to do that in the next version. Thank you. So conceivably in the future the browser might be able to create the file on the user's behalf (I know it's little, but it's one less thing to remember).

Wonderful, thank you. Might it be an option in the future to be able to reboot into safe mode from the browser? Would be handy for those of us that use headless systems, but absolutely no rush, since I appreciate that this will be a bit more involved.

Thanks - I'm 64-bit capable according to this. Might be a useful command for those of us that aren't quite as savvy.

Thank you Joe L for the 64 bit test line, I'll run it shortly. Well, thank you again since you've helped me out a couple of times. And to echo other sentiments on this thread, thank you Tom. From some of the interactions I read on here, it sometimes seems like the tail is trying to wag the dog. Don't be pushed into implementing something you haven't considered. And have a good weekend.

Thanks WeeboTech, much appreciated

I'm running 2GB RAM on my box so I'm thinking of skipping this RC and going from 13-15. I know it's an easy change to get 14 working, but judging from the other post in Announcements, a new RC might be out fairly soon. Quick question though - if I'm running absolutely stock unRAID, 10 data drives + parity and cache (all WD Greens, mixture of 1 & 2 TB) storing DVD backups, do I need more than 2GB of RAM? It seemed OK when I first built my 3 drive system, but it dawned on me when Tom didn't consider <4GB systems for this RC that maybe the base configuration has gone up. Would I benefit? I've had a couple of crashes in the past where the system's just dropped off the network and I've had to hold the power button in (normally after writing lots of data). Could they be insufficient memory related? (obviously don't expect an answer based on so little information, just throwing ideas).

To be fair, I run unRAID completely stock. I was sold on the basis that it's a relatively affordable way to get a large, mainly read-only, NAS drive solution with a failure mechanism built in. I put together a a fairly meager system (motherboard with 8x SATA ports and onboard Gig LAN port, low power processor, 2Gb RAM, PSU), and I've been filling it with WD Green Power drives since. The only changes I've made are to update to a more beefy power supply and add a Supermicro 8 port SATA card. The system works virtually flawlessly; it's not the fastest out there, but things like parity check speeds aren't really a concern if I'm running overnight. I have no idea whether it'll run 64-bit though. It might, I guess. I've been keeping up with releases to take advantage of any driver updates and speed improvements (and the fact that I might run >2TB drives in the future). The FTP option has come in quite handy recently too, but it ultimately still does what I need it to, and its requirement hasn't changed. I don't really need add-ins, since I have a Windows Home Server running that handles all network apps. Would I rip out my mobo, RAM and CPU if I needed to in order to get a 64-bit file server? Don't know really, but my hand might be forced if - say - new drives were released that only the 64-bit version supported.

Just thought I'd try a restart after some of the comments on here. I'd successfully updated from 12a to 13 and run a parity check, but not transferred any data. I stopped the array and hit reboot and everything went down OK. It didn't come back up again though. No web interface, no ping on its IP address. It's a headless unit, so I couldn't see a screen. I waited for 30 minutes, then tapped the power button. It appeared to shut down gracefully, then I powered up again. This time it came back up fine. It didn't automatically start a parity check, so I assume the system thinks all is well. I captured a system log from the web interface after this clean boot, but I assume it won't contain anything useful, since - well - it's of a clean boot. Hopefully this is just a glitch, but I thought I'd post in case anybody else is having reboot issues. I only really encountered problems with 12a when I was copying a lot of data all at once, or if I'd put a lot on the cache drive. I suspect that's an out of memory issue, but the machine would just disappear off the network. My box is a couple of years old now, and I really need to get together the spec and put it in my signature. syslog.txt.txt

Ahh, thank you

I'm running 12a, and I noticed last week how much harder it is now to remove a drive from the array (I had an empty drive so figured I'd re-purpose it as a cache). I don't know whether the wiki has been updated since - I can't find the guide I used - but it's worth noting that you need to take a note of all your disc assignments (especially the parity drive), since you'll need to assign them all again (and hope that you've not turned a data drive into a parity by mistake). Anyway, can I just confirm that there is no option to password protect the web interface? If so, it seems a bit of a security vulnerability; you can now get to all files through the browser. I might have misunderstood some of the share settings though.

Justin, As you may or may not know, you don't need a monitor always attached to your unraid box to access the "console" there is an application called putty that will do that for you. Using the telnet protocol you can have console access at any time with out a monitor attached. Make sure you set the "translation option" within Putty to UTF-8. google "putty" to find and download it. --Sideband Samurai Use it a great deal, and it comes in very handy (kind of wish it didn't, but hey-ho). However, a safe reboot option from the web-gui wouldn't go amiss also.

Personally, after initial install I don't ever want to touch the flash drive, and would rather not telnet onto the box. In an ideal world, everything would be locked down and controlled through the interface.

Statement still stands though, I think. Plugins are not part of the core package and hence should not be running when problems are reported on an RC thread. Sure, they're important, but they should always be removed on upgrade; otherwise it's just wasting the precious time of people on here that are kind enough to help others out. And my own stupidity needs the advice of those people EDIT: made post less aggressive.

Thanks Trurl, I'll give that a go over the weekend. Seems an odd thing to have to do, but I'll try.

Hi - Upgraded from 4.7 to to 5.0rc11 and I've had a few problems with the server on my network that were not present previously. I ran through all of the upgrade steps in the release notes without issue. I'm running Windows 7, and SMB is set to Workgroup. - Sometimes, when browsing, unRaid1 (the name of my server) doesn't appear in the available machines on the network. If I go there directly (\\unraid1), it shows up fine - When backing up a movie to the server via file copy, I get a lot of "The network name is no longer available" messages in windows (error message not verbatim, I'll check when I'm next at home and update). If I click "Try Again" a couple of times, it resumes. I can't work out whether this is time based, but I suspect it might be happening for every file - Occasionally, I use DVD Shrink or Clone DVD to verify that a movie has backed up OK by opening the network location to verify all files are present and correct. Now when I do this, I get a file not found error for "video_ts.ifo". Looking on the drive, the file is there, so I'm wondering why the software suddenly thinks it's not Attached is the syslog. Are there any other details I need to provide? Any assistance grateful. syslog.txt

I was thinking the same thing, but I'm currently assuming that the web GUI forms will be locked down once the back end functionality is sorted (potentially in a later version). There's a few areas here where the interface could guide the user better, but I'm guessing they'll fall into place once the system's parameters have settled. My job involves building web interfaces for applications. It's in the publishing industry, so not identical, but I started sketching out a demo web front end with Jquery and its UI components. Whilst it doesn't change the functionality of the system at all, it makes a huge difference to the appearance (in my opinion, obviously).

Sorry, yes. I meant I followed the upgrade instructions fully as per the release noyes and all upgraded fine. Subsequent posts explained that my username must be lower case. Thank you.

User names must be lower case. (You were using a leading capital letter) Ahh, thank you

Hi - I've just upgraded from 4.7 to rc-11 and all's looking good. Followed the upgrade instructions and it all went smoothly. Having trouble adding users though. Root is the only user listed. When I try to add a new one I get a very brief message (something about restart SMB?), and it looks like it's done. However, no new user on the list. In my old configuration, I didn't use the Users section at all - I just fancied having a look at the FTP part. I upgraded by stopping my array and updating the files to the flash share over the network. If I click the log button afterwards, I get this... /usr/bin/tail -f /var/log/syslog Feb 3 15:01:10 unRAID1 emhttp: shcmd (73): smbpasswd -L -s -a Simon <<< "*****"$' '"*****" Feb 3 15:01:10 unRAID1 emhttp: _shcmd: shcmd (73): exit status: 1 Feb 3 15:01:10 unRAID1 emhttp: shcmd (74): cp /etc/passwd /etc/shadow /etc/samba/private/smbpasswd /boot/config Feb 3 15:01:10 unRAID1 emhttp: shcmd (75): :>/etc/samba/smb-shares.conf Feb 3 15:01:10 unRAID1 emhttp: Restart SMB... Feb 3 15:01:10 unRAID1 emhttp: shcmd (76): killall -HUP smbd Feb 3 15:01:10 unRAID1 emhttp: shcmd (77): ps axc | grep -q rpc.mountd Feb 3 15:01:10 unRAID1 emhttp: _shcmd: shcmd (77): exit status: 1 Feb 3 15:01:10 unRAID1 emhttp: shcmd (78): /usr/local/sbin/emhttp_event svcs_restarted Feb 3 15:01:10 unRAID1 emhttp_event: svcs_restarted Is that any use, or do I need to provide more? EDIT: re-pasted log entry - missed off a bit originally EDIT: pasted correct log entry - D'OH!

Yes, I've changed cables, ports, power *shouldn't* be a problem and had it running on a Win box fine. Have tried adding it three or four times now with various combinations, initialising configs between to rebuild cache. Taken a couple of weeks. However, I was drawn to this post when sunnyville mentioned "error (factory-erased)" when clicking on the red-ball drive. Something I've not seen before.

I've got exactly the same problem on a 2TB drive (I think). Did preclear solve it? Haven't done anything like this before, so some help would be appreciated. EDIT: Other things I've tried/notes... - smartctl - resulted in "Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)" - Took it out, put it into a Windows 7 machine, formatted, worked fine (as far as I tested it) - Have tried it a couple of times in my unRAID system, but it's always coming back with a red ball problem - Western Digital 2tb EARS drive. I've replaced my parity and drive one with equivalent drives, no problem - Here, I'm adding a new drive to the array rather than replacing, and it's being plugged into an 8-port SATA card (SuperMicro AOC-SAT2-MV8)

Yeah, good point. Thanks. I was thinking just an old machine that's used in the shed or somewhere. The machine's been on for 24 hours now, and I've been throwing stuff at it. Constantly parity checking whilst copying files to it and recreating the meta-data for the movies on there. Hasn't missed a step or thrown an error (touch wood). The old setup would never have coped with anything like this, throwing up "network location no longer available" type messages as it blipped in and out. Golden rule: you can re-use drives and other components, but don't cut corners on the power supply.