curtis-r

Not sure about my false drive temps, but in regard to the failed drive I rebooted the array without the drive, then rebooted again with the same old drive. Rebuild. All is good... so far.

I did not realize that, and I bet you are correct that I'd been rebooting w/o stopping the array. Attached is the syslog. I'm hoping someone can help me figure out what's wrong with disk10 aside from 'it's dead'. The problem started after an overheating parity check. syslog_9-6-2014.txt

Thanks, I just adjusted the settings, but what was weird is as you can see in my screenshot, I was getting the temp warning for drives that weren't past that threshold. Any ideas on why disk10 doesn't show temp & has a red bullet, yet I can access the data just fine?

One of the worst replies to a thread ever: stick with it. I had given up a few times over the years on getting WOL working on my unraid, and though I cannot recall what eventually did it, but I eventually figured it out. Obviously BIOS settings and unraid GUI settings were tweeked, but that's all I've got for you. Probably had updated the BIOS along the way also.

After a reboot 2 days ago it automatically started a parity check without my realizing it. I usually put a desk fan on the enclosure when I choose to run a parity check b/c of heat, thus things overheated & locked-up. The next day after a reboot disk10 shows red. And now, in Dynamix gui, it keeps reporting drives overheating even though the drives are cold, and the devices gui shows low temps - see screenshot. I can access disk10's data & the shares just fine through smb. Also, the section to run a parity check is missing. I've also recently experienced other weird things like the unraid occasionally freezing when coming out of sleep. All of this couldn't be memory going bad could it? I haven't run a memtest yet b/c the temp and disk10 issues don't seem like memory-related problems to me. Any help would be greatly appreciated. system_log.txt

Man, am I dense! I completely forgot to add a user to the ftp setting. Now I've removed my custom conf, and though I'm remoting in from my office, ftp not only works, but I can then browse ftp-created folders through Windows!!! Thanks a bunch for the hand-holding.

Removed the conf line in the go file, and then also renamed the conf file, but either way I cannot FTP in at all. Are you saying that without a 'custom' conf file like mine, you are able to connect via FTP? I've been running the latest beta BTW.

I feel this is a stupid question, but where can I find the default conf? I've been using my file for years.

Without the custom conf I couldn't FTP in at all. Still having the same problem. Do you not have a custom conf & can you still FTP in? Here is what I'm now working with. Thanks for your help. Go: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & # ftp adjustment to allow users to see files cp /boot/vsftpd.conf /etc vsftpd.conf: # vsftpd.conf for unRAID # write_enable=YES connect_from_port_20=YES # # No anonymous logins anonymous_enable=NO # # Allow local users to log in. local_enable=YES local_umask=000 local_root=/mnt check_shell=NO # # All file ownership will be 'root' guest_enable=YES guest_username=root anon_upload_enable=YES anon_other_write_enable=YES anon_mkdir_write_enable=YES anon_world_readable_only=NO # # Logging to syslog syslog_enable=YES log_ftp_protocol=NO xferlog_enable=NO # # Misc. dirmessage_enable=NO ls_recurse_enable=YES

# vsftpd.conf for unRAID # write_enable=YES connect_from_port_20=YES # # No anonymous logins anonymous_enable=NO # # Allow local users to log in. local_enable=YES local_umask=077 local_root=/mnt check_shell=NO # # All file ownership will be 'root' guest_enable=YES guest_username=root anon_upload_enable=YES anon_other_write_enable=YES anon_mkdir_write_enable=YES anon_world_readable_only=NO # # Logging to syslog syslog_enable=YES log_ftp_protocol=NO xferlog_enable=NO # # Misc. dirmessage_enable=NO ls_recurse_enable=YES

@dgaschk Sorry for the long delay, but still no go. When Filezilla creates or copies a folder/file, its permissions are rwx for owner only, thus Windows cannot access them. Still the only current solution is Midnight Commander to manually add permissions for group and others. Here is my current go file, with your previous suggestion on the last line: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & # ftp adjustment to allow users to see files cp /boot/vsftpd.conf /etc #run notification app installpkg /boot/packages/unraid_notify.tgz # forum suggested b/c filezilla creating wrong permissions when copying files & folders echo "local_umask=0000" >> /etc/vsftpd.conf

Excuse my ignorance, but after that 'go' entry & reboot, when I try to FTP to my unraid I can no longer connect. I get "500 OOPS: missing value in config file for: umask all 000"

Thanks for the link, but as I stated, CHMOD through FileZilla do not stick/apply. I change them but nothing happens.

May be a bit off topic, but if you create a folder in your unraid with FileZilla, the permissions are 700 and the only way to correct them to 777 is through putty. Permission changes through FileZilla (or Windows Explorer) don't stick. It's been driving me crazy, copying with FileZilla to later find I can't access the folders. Any suggestions?

As for the telnet option, I feel so stupid. I should have known that. But what is the 'system console'? thanks.

Is there a way to get a more detailed # of the amount of free space on a disk when on 5.0 (like was displayed in prior versions)?

My Norco 4020 was also way too loud for my home theater rack, thus pimped mine too: Figured it might be worth $12 for each of the 3 XLF 140mm fans since they claim <16dB. Simply epoxied them together, with a strip of aluminum across the top. Two strips of wood, held in place with screws through the case side, to keep the fan assembly in place. I also built a mini thermostat to control the fans. See the variable resistor sticking through the front of my case. Honestly, there is no sound from these fans on, so the thermostat is simply to save a some watts of power when the system doesn't need the fans.