lovingHDTV

I did rebuild with the same drive and it is working fine. I guess I was just confused because unRaid disabled a perfectly fine drive, but on that same IDE channel there was a failed drive (the cache drive). dave

OK after digging around a little more I figured some of this out. It may not be as bad as I thought. The drive that failed, bad bearings was the cache drive. So it looks like the cache drive is gone, along with my crashplan setup. Figures that I copy from the normal install point to the cache drive two days before the drive crashes. I have the original install, hopefully that goes fine. So could the failed cache drive cause the other drive on the same ide channel to be disabled? Do I just need to go through and re-enable the disk3 to get it all up and running? thanks, dave

I've replaced failed drives before, but this is a first for me. I was traveling, of course, when I got the emails saying drive 3 was disabled. My wife reported a very loud noise coming from the server. I have a spare drive waiting for these things, so when I got home I logged onto the gui, noted the serial number for the disabled drive. I could hear it grinding away in the server so I know it's good and dead. I pull what I think is the dead one, but the serial numbers don't match so I keep looking until I find drive 3 with matching serial numbers. I swap the drive, and boot up. The servers is still grinding badly so I shut it down and the truly failed drive is swapped instead. So now I have disk3 which unraid flagged as disabled still in slot 3, and I have now swapped the drive with obvious bad bearings out (slot 2). I start up unRaid it started without issue, and the array started up. Now when I look at the array status, it still shows drive 3 as disabled, and the drive in slot 2 is listed as unassigned. In the GUI the parity, and disks1-6 all show populated. Does that mean disk7 is the disk that failed? I looked for my backup copy of unraid, but yes, I moved it to the tower drive so I can't get it. It will now reside on my wuala account after I get past this screw up. So I'm confused as to what happened. It looks like the disk in slot2 died, unRaid flagged the disk in slot3 and disabled it. Does that mean I had two drive failures and I'm screwed? The two drives in question, slot2 and slot3 are on the same IDE channel. I"m hoping that the failed drive confused unRaid and it thought the channel failed or something. Anyway for me to figure out where the drive in slot 2 (the one not showing up assigned at the moment, it is also the one I replaced, and it has been in the array before). I do have my second unRaid flash drive. These drives have been in my array since I started it years ago. Maybe I could get something off the old flash drives? I've also posted log files to the forum, if I were to find a post with my syslog, would that give me some help? at the moment I have the unRaid powered on, but the array stopped. EDIT: I'm running 5.08d, and I did remember I do have a backup copy of my entire unRaid install on the flash drive. so if there are files there that can help. I have them. Attached the notices that unRaid emailed me. thanks for any and all help, dave Firt_failure_notice.txt Latest_failure_notice.txt

Thanks Joe! That was the problem the md5-deep was not completing so I removed it (didn't have gcc installed). Now I get my unraid status emails. Wondered what happened to them. dave

I've seen a similar thing for my server. If you look at the webpage is that drive being written to? If it is, wait it out and eventually (at least for me) it will mount and start a parity check. dave

All, I have the unraid-swapfile, openssh, and openssl packages installed, running and set to re-install after reboot. However, after every reboot they don't get installed. I looked in the /var/log/syslog hoping to find some messages as to why, but nothing was there until I told them to install via the webpage. It does see that they are already downloaded so it just starts them up. I see the following files in /boot/packages unraid-swapfile-unmenu-package.conf unraid-swapfile.auto_install unraid-swapfile.manual_install I see the same three equivalent files for the other two packages. Other packages I have do auto-install. in my /boot/config/go file I see: cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c Any suggestions of where I can look to try and debug this? thanks, dave

I'd like to add two items to the clean power down script that gets installed from the powerdown-1.02.noarch-unRAID.tgz package. First I'd like to add the shutdown of the swap file Secondly I'd like to add the stopping of Crashplan What is the best way to do this? I'd assume some sed commands to add the functionality after the script has been installed. Can I just add this to the go script after the auto install line? Any suggestions welcomed thanks, dave

I've noticed before as well. I consider this a major bug as you don't realize that your data is not protected. I try to remember to do this after the reboot, but just checked and have 3 weeks of unprotected pictures on my cache drive that are not protected. Can we get this fixed? At least a button that we can click to say "apply on reboot". dave Errrr .... crontab -l never shows the schedule for mover, because it lists the contents of /var/spool/cron/crontabs/root The mover schedule is placed in /etc/cron.d/root ... from the logfile: Aug 1 00:39:56 Tower login[9423]: ROOT LOGIN on '/dev/pts/0' from '10.2.1.15' Aug 1 00:41:29 Tower emhttp: shcmd (77): crontab -c /etc/cron.d - <<< "# Generated mover schedule: 0 */2 * * * /usr/local/sbin/mover |& logger" I will investigate the contents of /etc/cron.d next time my server is rebooted. Just did a reboot. Nothing in the /etc/cron.d - empty. As for crontab -l root@Tower:~# crontab -l # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system, but if they don't the average newbie # might get quite perplexed about getting strange mail every 5 minutes. :^) # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null # check parity every Mon at 8 am: 0 8 * * 1 /root/mdcmd check NOCORRECT 1>/dev/null 2>&1 root@Tower:~# Shawn

I just updated to Beta8c and now I can't get unMenu to work. So I updated to the latest unMenu but here is what I see in the syslog Jul 11 13:26:02 Tower unmenu-status: Starting unmenu web-server Jul 11 13:29:56 Tower unmenu[10077]: awk: ./unmenu.awk:1722: fatal: division by zero attempted Here is line 1722 from my unmenu.awk: resync_speed = sprintf("%d", (resync_db+0) / (resync_dt+0)); #bjp999 3/7/11 Change for 5.0b6 so it appears that resync_dt is zero? Maybe something changed with beta-8c? commenting out that section that was added for 5.0b6 has it up and running again. Not sure what I just removed any help appreciated. thanks dave

I want to rebuild the drive as I've done writes to the drive (many pictures) and need to keep these. So here is what I read: Does this no longer work? BTW I did what you outlined above and it is rebuilding now. Rebuild just finished and it ran fine. Ordered a new single rail 650W Corsair power supply as I think it is power supply related. Thanks Joe for the help.

Joe, I tried what it says: 1. recorded drive assignment 2. stopped array 3. unassigned disk4 (no device) 4. reboot Upon reboot the red dot still is there, and disk4 is assigned to the drive that I previously unassigned it from. What am I doing wrong? thanks, dave

All, Version beta5.0-beta6a I've had issues with disk4 in my array. I noticed a month or so ago that it had been disabled. I replaced it with a new drive, but didn't really thing the original drive was bad. It is still sitting on my desk waiting for me to test it. Now I see as of yesterday disk4 is again disabled. I shutdown, opened the case and replaced the IDE cable with a new one, and checked the power connection. I restarted. I can now via unMenu run a smart test on it and it passes, I've attached the report. I looked at my syslog and don't see anything in the log file that would hint as to what is wrong with hdf or disk 4. I've attached it as well. I've stopped and restarted the array, but the disk4 continues having a red dot by it, not sure what that means, but its not green so I'm assuming it is bad. I don't have an option to run a parity check and unRaid reports that my configuration is valid. Ideas? thanks, dave smarttest.txt syslog-2011-07-09.txt

it ran fine when I kicked it off manually. dave

I've looked at my syslog from the reboot I did yesterday and don't see any crontab entry being created for the mover script. I also looked at one from April 27th and do see this: Apr 27 16:57:54 Tower emhttp: shcmd (4): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Apr 27 16:57:54 Tower emhttp: shcmd (5): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Which makes sense. I don't see that at all in my current syslog file. Could it be that this did not run because I had to replace a drive on this last reboot and rebuild the array? So when this happens somehow the crontab doesn't get setup? I went to the webpage and hit apply on the mover script settings and now see this in syslog: Jun 19 13:10:26 Tower emhttp: shcmd (90): crontab -c /etc/cron.d - <<< "# Generated mover schedule: 40 3 * * * /usr/local/sbin/mover 2>&1 |logger" Which was created by my hitting the apply key on the webpage and I do see it in the /etc/cron.d/root file now. This is why I was/am confused on how this "should" all work. sorry for the ramble, dave

A. what version of unRAID are you running? B. It is set in the unRAID settings... If you've not enabled a cache drive, it might not be there in cron. C. It is usually set to 3:40 AM daily, but you can set it as desired on the unRAID settings page. OK I see it in the settings page and it is set for 3:40AM daily. Wonder why it didn't run last night. I also don't see it in the crontab settings at least not when I run crontab -l I'm running 5.0-Beta6a. I've had the cache drive running for a year or so and never seen any issues, but to be honest I've never really looked at it either. I just noticed because my cache drive filled up yesterday and I had to stop copying over movies as I had no idea what would have happened if it filled up completely. thanks dave

I'm trying to find out the "default" schedule for the mover script. I ran a crontabs -l and it just lists the run_parts script and the only thing in the /etc/* directories is the logrotate script. Is there no default set when you enable the cache drive? I just noticed this issue because I've re-ripped a lot of movies and the cache drive filled up and never moved anything over. I've not manually ran the script and it is working, just trying to understand how it should work. thanks dave

version: version: 5.0-beta6a I've run a no correct parity check three times and get a parity error at the very first of the run. I only get the one, but curious as to how to tell if I should correct parity or not. syslog: upon boot up I see: May 18 08:11:22 Tower kernel: REISERFS (device md5): checking transaction log (md5) (Routine) May 18 08:11:22 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal (Routine) May 18 08:11:22 Tower kernel: REISERFS (device md1): using ordered data mode (Routine) May 18 08:11:22 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal (Routine) May 18 08:11:22 Tower kernel: REISERFS (device md2): using ordered data mode (Routine) May 18 08:11:22 Tower kernel: md: parity incorrect: 128 (Errors) May 18 08:11:22 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal (Routine) May 18 08:11:22 Tower kernel: REISERFS (device md3): using ordered data mode (Routine) When I manually run check I see: May 18 16:08:10 Tower kernel: mdcmd (48): check NOCORRECT (unRAID engine) May 18 16:08:10 Tower kernel: md: recovery thread woken up ... (unRAID engine) May 18 16:08:10 Tower kernel: md: recovery thread checking parity... (unRAID engine) May 18 16:08:11 Tower kernel: md: using 1152k window, over a total of 976762552 blocks. (unRAID engine) May 18 16:08:22 Tower kernel: md: parity incorrect: 128 (Errors) May 18 16:19:02 Tower kernel: mdcmd (50): check NOCORRECT (unRAID engine) May 18 16:19:02 Tower kernel: md: recovery thread woken up ... (unRAID engine) May 18 16:19:02 Tower kernel: md: recovery thread checking parity... (unRAID engine) May 18 16:19:02 Tower kernel: md: using 1152k window, over a total of 976762552 blocks. (unRAID engine) May 18 16:19:02 Tower kernel: md: parity incorrect: 128 (Errors) Suggestions? thanks, dave

unRaid 5.0beta6a OK I attempted setting up some permission on my shares to keep the kids from deleting the movies, music and pictures. All I ran into was lots of problems so I'm trying to reset it all back to public for each share. I have been able to do this and delete the users from the user list (not very easy and required a reboot), but that is done. The issue I'm having is that one share "My Documents" is keeping me from writing to it. If I look at /etc/samba/smb-share.conf I see: [My Documents] path = /mnt/user/My Documents comment = browseable = yes # Public public = yes writeable = yes I've also checked that every disk is set the same. Why would I not be able to write to this share? I checked the file permissions and they are all set to nobody users 770 for directories and 660 for files. I do remember when I first set the shares to secure and set my username to allow read/write I had to log in to access the shares, and I did that once, but was never prompted to do it again. I'm wondering if it is attempting to logging every time I access the share now and the user is unknown so I can't read/write. If this is the case how do I undo this? EDIT: I figure it out. Somehow I changed the include disk list to include a disk where the data did not reside, and put the disk where the data was located in the exclude list. So I could read the data without issue, but could not write anything to it. So if you get a no disk error when writing to a share, and the webpage shows the share space as zero, but you can write directly to the disk in question (or at least the disk you thought to be in questions) check your include/exclude lists in the share definition. dave syslog.txt

Feeling foolish as I just figure it out. The user name has to be all lower case. If I change the name to david instead it worked just fine. Something like this would be helpful in the manual. dave

Version beta 5.6a I'm trying to add users to Tower as I want to have my media drives read only for everything except for me. Hoping to make it so the kids can't delete all the music, pictures and movies. I have user shares enabled and they are working fine now. I go to user tab and hit add user, fill in the info, but the user does not appear. The syslog says: May 1 07:38:27 Tower logger: useradd: invalid user name 'David' May 1 07:38:27 Tower emhttp: shcmd (86): chpasswd <<< David:"*****" May 1 07:38:27 Tower emhttp: _shcmd: shcmd (86): exit status: 1 May 1 07:38:27 Tower emhttp: shcmd (87): smbpasswd -L -s -a David <<< "*****"$'\n'"*****" May 1 07:38:27 Tower emhttp: _shcmd: shcmd (87): exit status: 1 May 1 07:38:27 Tower emhttp: shcmd (88): cp /etc/passwd /etc/shadow /etc/samba/private/smbpasswd /boot/config I've read where it says to enable user share security, but can't find anything in the web page that does that. What am I missing? thanks, dave

I figured I installed it, but looked through the menu trying to find it, but no luck. I'll go look again. OK I found it unraid-status-email all set now,

I just installed Beta5.6a with unmenu so I'm not sure if this is an UnRaid thing or UnMenu, but I get an email every hour saying one or more drives are hot. How do I turn this off? thanks, dave

I'm tried to use the duplicate file script to find the duplicate file on my system, but it does not seem to like the spaces in the name: Apr 30 07:08:20 Tower shfs: duplicate object: /mnt/disk4/My Movies/The Perfect Storm/folder.jpg (Minor Issues) Apr 30 07:09:04 Tower shfs: duplicate object: /mnt/disk4/My Movies/The Perfect Storm.properties (Minor Issues) Apr 30 07:44:39 Tower last message repeated 2 times Apr 30 07:45:34 Tower last message repeated 2 times Apr 30 07:45:44 Tower unmenu[2227]: ls: cannot access /mnt/*/*My: No such file or directory Apr 30 07:45:44 Tower unmenu[2227]: ls: cannot access Movies/The: No such file or directory Apr 30 07:45:44 Tower unmenu[2227]: ls: cannot access Perfect: No such file or directory Apr 30 07:45:44 Tower unmenu[2227]: ls: cannot access Storm.properties*: No such file or directory Apr 30 07:45:44 Tower unmenu[2227]: ls: cannot access /mnt/*/*My: No such file or directory Apr 30 07:45:44 Tower unmenu[2227]: ls: cannot access Movies/The: No such file or directory Apr 30 07:45:44 Tower unmenu[2227]: ls: cannot access Perfect: No such file or directory Apr 30 07:45:44 Tower unmenu[2227]: ls: cannot access Storm/folder.jpg*: No such file or directory Using Beta 5.06a Any one else see this before? thanks, dave

Do the subsequent installs have to compile ssmtp or is it smart enough to just use the already compiled code from the first manual install? If I don't have to have gcc run and compile ssmtp everytime that would be nice. thanks, dave

I had this exact problem and rebooting my PC fixed it for me.