June 29, 201115 yr Every night before I go to sleep I stop the array and then power down the server. I have the clean power down script installed. But, for some reason it did not shut down tonight. The Main web page does not connect like normal, but the other pages were accessible from the server for a few minutes before it stopped connecting. I cannot access any of the shares since Samba was stopped. I can successfully ping the server and receive a response. Any ideas? Log snippet from power down event: Jun 29 02:01:32 unRAID emhttp: shcmd (45): beep -r 2 (Other emhttp) Jun 29 02:01:32 unRAID emhttp: shcmd (46): /etc/rc.d/rc.ntpd stop 2>$stuff$1 | logger (Other emhttp) Jun 29 02:01:32 unRAID logger: Stopping NTP daemon... Jun 29 02:01:32 unRAID emhttp: shcmd (47): /etc/rc.d/rc.samba stop | logger (Other emhttp) Jun 29 02:01:32 unRAID emhttp: shcmd (48): /etc/rc.d/rc.nfsd stop | logger (Other emhttp) Jun 29 02:01:33 unRAID emhttp: Spinning up all drives... (Other emhttp) Jun 29 02:01:33 unRAID emhttp: shcmd (49): sync (Other emhttp) Jun 29 02:01:33 unRAID kernel: mdcmd (58): spinup 0 (Routine) Jun 29 02:01:33 unRAID kernel: mdcmd (59): spinup 1 (Routine) Jun 29 02:01:33 unRAID kernel: mdcmd (60): spinup 2 (Routine) Jun 29 02:01:33 unRAID kernel: mdcmd (61): spinup 3 (Routine) Jun 29 02:01:33 unRAID kernel: mdcmd (62): spinup 4 (Routine) Jun 29 02:01:33 unRAID emhttp: mdcmd: write: Invalid argument (Other emhttp) Jun 29 02:01:33 unRAID kernel: mdcmd (63): stop (unRAID engine) Jun 29 02:01:33 unRAID kernel: md: stop_array: not started (unRAID engine) Jun 29 02:01:43 unRAID emhttp: shcmd (50): /sbin/poweroff (Other emhttp) Jun 29 02:01:43 unRAID shutdown[14518]: shutting down for system halt Jun 29 02:01:43 unRAID init: Switching to runlevel: 0
June 29, 201115 yr Every night before I go to sleep I stop the array and then power down the server. I have the clean power down script installed. But, for some reason it did not shut down tonight. The Main web page does not connect like normal, but the other pages were accessible from the server for a few minutes before it stopped connecting. I cannot access any of the shares since Samba was stopped. I can successfully ping the server and receive a response. Any ideas? Log snippet from power down event: Jun 29 02:01:32 unRAID emhttp: shcmd (45): beep -r 2 (Other emhttp) Jun 29 02:01:32 unRAID emhttp: shcmd (46): /etc/rc.d/rc.ntpd stop 2>$stuff$1 | logger (Other emhttp) Jun 29 02:01:32 unRAID logger: Stopping NTP daemon... Jun 29 02:01:32 unRAID emhttp: shcmd (47): /etc/rc.d/rc.samba stop | logger (Other emhttp) Jun 29 02:01:32 unRAID emhttp: shcmd (48): /etc/rc.d/rc.nfsd stop | logger (Other emhttp) Jun 29 02:01:33 unRAID emhttp: Spinning up all drives... (Other emhttp) Jun 29 02:01:33 unRAID emhttp: shcmd (49): sync (Other emhttp) Jun 29 02:01:33 unRAID kernel: mdcmd (58): spinup 0 (Routine) Jun 29 02:01:33 unRAID kernel: mdcmd (59): spinup 1 (Routine) Jun 29 02:01:33 unRAID kernel: mdcmd (60): spinup 2 (Routine) Jun 29 02:01:33 unRAID kernel: mdcmd (61): spinup 3 (Routine) Jun 29 02:01:33 unRAID kernel: mdcmd (62): spinup 4 (Routine) Jun 29 02:01:33 unRAID emhttp: mdcmd: write: Invalid argument (Other emhttp) Jun 29 02:01:33 unRAID kernel: mdcmd (63): stop (unRAID engine) Jun 29 02:01:33 unRAID kernel: md: stop_array: not started (unRAID engine) Jun 29 02:01:43 unRAID emhttp: shcmd (50): /sbin/poweroff (Other emhttp) Jun 29 02:01:43 unRAID shutdown[14518]: shutting down for system halt Jun 29 02:01:43 unRAID init: Switching to runlevel: 0 That is a BIOS feature known as ACPI. Do you have it enabled in your BIOS? (Without it, the Linux cannot shut the power off) If you can log in via telnet, you can try poweroff and see if it does anything. (different than powerdown in that it only turns off power and does not stop services first)
June 29, 201115 yr Author I get the following when I run the poweroff command, but it still has not shut down fully. I've never had this problem before, and I've been shutting it down like this every night for the past few weeks. Linux 2.6.32.9-unRAID. root@unRAID:~# powerdown Capturing information to syslog. Please wait... version[23877]: Linux version 2.6.32.9-unRAID (root@Develop) (gcc version 4.2.3) #8 SMP Wed Nov 24 01:15:59 MST 2010 ls: cannot access /dev/hd[a-z]: No such file or directory ls: cannot access /dev/hd[a-z]: No such file or directory /etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect status[23933]: State: STOPPED status[23933]: D# Model / Serial Status Device status[23933]: 0 SAMSUNG HD204UI / S2H7J1CZ915646 DISK_OK sda status[23933]: 1 Hitachi HDS5C30 / ML0220F30JPUVD DISK_OK sdb status[23933]: 2 Hitachi HDS5C30 / ML0220F30DKEJD DISK_OK sdc status[23933]: 3 SAMSUNG HD204UI / S2H7J90B407483 DISK_OK sdd status[23933]: 4 SAMSUNG HD154UI / S1XWJX0B300404 DISK_OK sde status[23933]: SMART overall health assessment ls: cannot access /dev/hd[a-z]: No such file or directory status[23933]: /dev/sda: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) status[23933]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net status[23933]: SMART overall-health self-assessment test result: PASSED status[23933]: /dev/sdb: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) status[23933]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net status[23933]: SMART overall-health self-assessment test result: PASSED status[23933]: /dev/sdc: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) status[23933]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net status[23933]: SMART overall-health self-assessment test result: PASSED status[23933]: /dev/sdd: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) status[23933]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net status[23933]: SMART overall-health self-assessment test result: PASSED status[23933]: /dev/sde: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) status[23933]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net status[23933]: SMART overall-health self-assessment test result: PASSED status[23933]: /dev/sdf: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) status[23933]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net status[23933]: /dev/sdf: Unknown USB bridge [0x13fe:0x3d00 (0x100)] status[23933]: Smartctl: please specify device type with the -d option. status[23933]: Use smartctl -h to get a usage summary status[23933]: No active PIDS on the array /etc/rc.d/rc.unRAID: line 195: echo: write error: Invalid argument Removing old syslog: /boot/logs/syslog-20110618-174417.txt Saving current syslog: /boot/logs/syslog-20110629-090604.txt -rwxrwxrwx 1 root root 196239 Jun 29 09:06 /boot/logs/syslog-20110629-090604.txt zip not installed. Consider installing to automatically zip current syslog Broadcast message from root (pts/0) (Wed Jun 29 09:06:07 2011): The system is going down for system halt NOW! I was doing some drywall repairs next to the server and disconnected the keyboard and monitor, could that be what did it?
June 29, 201115 yr Author Since the array and samba were already stopped, I held down the power button until it turned off. It booted up fine and will turn off fine now too. I ran a NOCORRECT verify and I've got 240 errors. Should I run a check to correct parity or just leave it be? I always write to the drives with Terracopy and make sure there are no errors when it compares checksums.
June 29, 201115 yr Since the array and samba were already stopped, I held down the power button until it turned off. It booted up fine and will turn off fine now too. I ran a NOCORRECT verify and I've got 240 errors. Should I run a check to correct parity or just leave it be? I always write to the drives with Terracopy and make sure there are no errors when it compares checksums. Yes, I think you can correct them... especially if they are at low block addresses in the file-system housekeeping areas on the disks.
June 29, 201115 yr Author Since the array and samba were already stopped, I held down the power button until it turned off. It booted up fine and will turn off fine now too. I ran a NOCORRECT verify and I've got 240 errors. Should I run a check to correct parity or just leave it be? I always write to the drives with Terracopy and make sure there are no errors when it compares checksums. Yes, I think you can correct them... especially if they are at low block addresses in the file-system housekeeping areas on the disks. These are the only blocks where errors were reported. They look low to me, are they? Jun 29 09:48:39 unRAID kernel: md: recovery thread woken up ... (unRAID engine) Jun 29 09:48:39 unRAID kernel: md: recovery thread checking parity... (unRAID engine) Jun 29 09:48:39 unRAID kernel: md: using 1152k window, [b]over a total of 1953514552 blocks[/b]. (unRAID engine) Jun 29 09:50:50 unRAID kernel: md: parity incorrect: 23079344 (Errors) Jun 29 09:52:01 unRAID kernel: md: parity incorrect: 36148696 (Errors) Jun 29 09:52:01 unRAID kernel: md: parity incorrect: 36148704 (Errors) Jun 29 09:55:57 unRAID kernel: md: parity incorrect: 82623104 (Errors) Jun 29 09:55:57 unRAID kernel: md: parity incorrect: 82623112 (Errors) Jun 29 09:59:27 unRAID kernel: md: parity incorrect: 125170488 (Errors) Jun 29 10:03:58 unRAID kernel: md: parity incorrect: 178790552 (Errors) Jun 29 10:03:58 unRAID kernel: md: parity incorrect: 178790560 (Errors) Jun 29 10:04:56 unRAID kernel: md: parity incorrect: 190215992 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042240 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042248 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042256 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042264 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042272 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042280 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042288 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042296 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042304 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042312 (Errors) Jun 29 10:05:15 unRAID kernel: md: parity incorrect: 192042320 (Errors)
June 29, 201115 yr Author Ok, so even though I invoked COCORRECT it still seems to have corrected errors. Array Status STARTED, 5 disks in array. Parity is Valid:. Last parity check < 1 day ago . Parity updated 238 times to address sync errors.
June 29, 201115 yr Ok, so even though I invoked COCORRECT it still seems to have corrected errors. Array Status STARTED, 5 disks in array. Parity is Valid:. Last parity check < 1 day ago . Parity updated 238 times to address sync errors. No, it did not. The display when in NOCORRECT mode was never updated to say "detected" vs. "corrected" If you run another NOCORRECT check again, it will again say it corrected them, and it found them again because it is not correcting them.
June 29, 201115 yr Author Ok, so even though I invoked COCORRECT it still seems to have corrected errors. Array Status STARTED, 5 disks in array. Parity is Valid:. Last parity check < 1 day ago . Parity updated 238 times to address sync errors. No, it did not. The display when in NOCORRECT mode was never updated to say "detected" vs. "corrected" If you run another NOCORRECT check again, it will again say it corrected them, and it found them again because it is not correcting them. Ahh, that makes sense then. Thanks for the help, I'll run a parity correction check overnight. One other thing. Can I write to the array during a parity check or should I wait till the check has completed?
June 29, 201115 yr Ok, so even though I invoked COCORRECT it still seems to have corrected errors. Array Status STARTED, 5 disks in array. Parity is Valid:. Last parity check < 1 day ago . Parity updated 238 times to address sync errors. No, it did not. The display when in NOCORRECT mode was never updated to say "detected" vs. "corrected" If you run another NOCORRECT check again, it will again say it corrected them, and it found them again because it is not correcting them. Ahh, that makes sense then. Thanks for the help, I'll run a parity correction check overnight. One other thing. Can I write to the array during a parity check or should I wait till the check has completed? you can write to the array, and read from it too. Neither will have any effect other than cause the parity and data disk heads to seek a bit more and slow down the parity calc a bit while the writes are occurring.
June 29, 201115 yr Author you can write to the array, and read from it too. Neither will have any effect other than cause the parity and data disk heads to seek a bit more and slow down the parity calc a bit while the writes are occurring. Man, unRAID just keeps impressing me! Thanks for your help as always.
June 30, 201115 yr Author Well this is weird. I ran a regular parity check, and it only found and corrected 134 errors vs. the 240 errors of the nocorrect check.
Archived
This topic is now archived and is closed to further replies.