savestheday Posted August 15, 2011 Share Posted August 15, 2011 Okay having a really odd issue.... I just precleared (5) new hard drives. I have (4) slots open in my unRAID. What I planned on doing was bringing 4 of the 5 online to completely fill my unRAID server. (1) drive is a 2TB Hitachi Coolspin, (4) are the Samsung green 2tb drives. Problem is, I can't choose the Hitachi whatsoever in the GUI. unRAID sees it because it's in unMENU and I can test it with preclear. So a few things I was thinking.... Do you think that unRAID just sees that I have only (4) slots left and automatically chooses the first (4) drives? (this hitachi is technically the last device /dev/sdx) If so, why am I unable to replace one of my 1TB drives with it? Would I have to assign these (4) Samsungs first and then restart and then be able to replace my 1TB with this 2TB hitachi? Second thought was, and I know from a prior post it shouldn't matter, but this Hitach drive is NOT a 4k AF drive but preclear set it up as one based on my preference in the the web gui. You think that has anything to do with it? Again, I highly doubt it, but just throwing that out there. Hope someone can help me! EDIT Had 2 ideas...maybe it was Simple Features? Nope. Happens in default web gui. I also brought 3 of the Samsung drives online thinking that maybe it'd let me chose the Hitachi? Nope that didn't work either Quote Link to comment
Joe L. Posted August 15, 2011 Share Posted August 15, 2011 Okay having a really odd issue.... I just precleared (5) new hard drives. I have (4) slots open in my unRAID. What I planned on doing was bringing 4 of the 5 online to completely fill my unRAID server. (1) drive is a 2TB Hitachi Coolspin, (4) are the Samsung green 2tb drives. Problem is, I can't choose the Hitachi whatsoever in the GUI. unRAID sees it because it's in unMENU and I can test it with preclear. So a few things I was thinking.... Do you think that unRAID just sees that I have only (4) slots left and automatically chooses the first (4) drives? (this hitachi is technically the last device /dev/sdx) If so, why am I unable to replace one of my 1TB drives with it? Would I have to assign these (4) Samsungs first and then restart and then be able to replace my 1TB with this 2TB hitachi? Second thought was, and I know from a prior post it shouldn't matter, but this Hitach drive is NOT a 4k AF drive but preclear set it up as one based on my preference in the the web gui. You think that has anything to do with it? Again, I highly doubt it, but just throwing that out there. Hope someone can help me! #1. post a syslog. #2. What license do you have? The 4k alignment is perfectly fine for any drive. That is not the issue. You might be discovering a bug nobody else has since you are adding so many disks at the same time, but since you did not include a syslog, no way to tell. Joe L. Joe L. Quote Link to comment
savestheday Posted August 15, 2011 Share Posted August 15, 2011 I have a pro license, the $119 one. Syslog attached. Thx! (please read my edit above, hope I didn't screw up the process by bringing 3 of the 4 online) Damn syslog wouldn't upload, it's here tho: http://cl.ly/2R3J1e0O3S0L1T1p2D42 Looks like I found the issue! Aug 14 21:40:38 EchoBase emhttp: SAMSUNG_HD204UI_S2H7J1CZC06138 (sdr) 1953514584 Aug 14 21:40:38 EchoBase emhttp: SAMSUNG_HD204UI_S2H7JD2ZA12046 (sdt) 1953514584 Aug 14 21:40:38 EchoBase emhttp: SAMSUNG_HD204UI_S2H7JD2ZA12067 (sdu) 1953514584 Aug 14 21:40:38 EchoBase emhttp: SAMSUNG_HD204UI_S2H7JD2ZA12066 (sdv) 1953514584 Aug 14 21:40:38 EchoBase emhttp: SAMSUNG_HD204UI_S2H7JD2ZA12047 (sdw) 1953514584 Aug 14 21:40:38 EchoBase emhttp: too many devices to add ../../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host2/port-2:7/end_device-2:7/target2:0:7/2:0:7:0/block/sdx Aug 14 21:40:38 EchoBase emhttp: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=21 |& logger Aug 14 21:40:38 EchoBase kernel: xor: automatically using best checksumming function: pIII_sse Aug 14 21:40:38 EchoBase kernel: pIII_sse : 13513.200 MB/sec Aug 14 21:40:38 EchoBase kernel: xor: using function: pIII_sse (13513.200 MB/sec) Aug 14 21:40:38 EchoBase kernel: md: unRAID driver 2.1.2 installed Quote Link to comment
Joe L. Posted August 15, 2011 Share Posted August 15, 2011 EchoBase emhttp: too many devices to add ../../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host2/port-2:7/end_device-2:7/target2:0:7/2:0:7:0/block/sdx I ve never seen that message before. Quote Link to comment
savestheday Posted August 15, 2011 Share Posted August 15, 2011 EchoBase emhttp: too many devices to add ../../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host2/port-2:7/end_device-2:7/target2:0:7/2:0:7:0/block/sdx I ve never seen that message before. Maybe I should feel honored to have found something no one else found! So good news (sort of). I pulled the last (unassigned) SAMSUNG drive from the Norco and left the hitachi in there. I'm now able to assign the Hitachi So I'm surmising that maybe my first theory was true. It sees (4) slots left in your unRAID and chooses the first four drives it finds. Not sure it's a major bug - I'm an edgecase. I had all of these drives left over from two FreeNAS's. Something to keep in mind tho. Quote Link to comment
hackztor Posted August 15, 2011 Share Posted August 15, 2011 I just had a 1.5tb drive get disabled due to a write fail, so I unmounted it and rebooted to try and remount it making it think its a new disk and recover data. Instead it showed the drive as 2tb and now says replace drive with a larger drive. Anything I can do but buy a new 2tb to put in its place? Quote Link to comment
bonienl Posted August 15, 2011 Share Posted August 15, 2011 After restarting the server I copied two files over to it. As expected write counters of both "parity" disk and selected disk increment, but I noticed a huge difference in counter values (see picture below). Is this normal behavior? I would expect both counters to be more or less the same. Quote Link to comment
Interstellar Posted August 15, 2011 Share Posted August 15, 2011 After restarting the server I copied two files over to it. As expected write counters of both "parity" disk and selected disk increment, but I noticed a huge difference in counter values (see picture below). Is this normal behavior? I would expect both counters to be more or less the same. Not necessarily! If a bit doesn't need updating then that means no write! So seems fine to me. Quote Link to comment
Joe L. Posted August 15, 2011 Share Posted August 15, 2011 After restarting the server I copied two files over to it. As expected write counters of both "parity" disk and selected disk increment, but I noticed a huge difference in counter values (see picture below). Is this normal behavior? I would expect both counters to be more or less the same. Not necessarily! If a bit doesn't need updating then that means no write! So seems fine to me. It is normal. They use differing buffering schemes. The data disks end up being buffered by the file-system buffers, so they have less (but probably larger) writes. Quote Link to comment
Interstellar Posted August 15, 2011 Share Posted August 15, 2011 Having some serious issues with my server atm. Aug 15 17:06:15 Tower shfs/user: duplicate object: /mnt/disk4/Media/.DS_Store (Minor Issues) Aug 15 17:06:15 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:30 Tower last message repeated 17 times Aug 15 17:06:31 Tower ntpd_intres[1135]: DNS pool.ntp.org -> 192.53.103.108 Aug 15 17:06:31 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:32 Tower ntpd[1125]: Listen normally on 2 eth0 192.168.1.110 UDP 123 (Network) Aug 15 17:06:32 Tower ntpd[1125]: new interface(s) found: waking up resolver Aug 15 17:06:32 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:34 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:34 Tower logger: Mon Aug 15 17:05:33 BST 2011 - Hard Drives active, resetting counter Aug 15 17:06:35 Tower cnid_dbd[11940]: Set syslog logging to level: LOG_NOTE Aug 15 17:06:35 Tower cnid_dbd[11940]: Error opening lockfile: Permission denied (Errors) Aug 15 17:06:35 Tower cnid_dbd[11940]: main: fatal db lock error (Errors) Aug 15 17:06:35 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:36 Tower cnid_dbd[11997]: Set syslog logging to level: LOG_NOTE Aug 15 17:06:36 Tower cnid_dbd[11997]: Error opening lockfile: Permission denied (Errors) Aug 15 17:06:36 Tower cnid_dbd[11997]: main: fatal db lock error (Errors) Aug 15 17:06:36 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:36 Tower afpd[5188]: transmit: Request to dbd daemon (db_dir /mnt/user/Media) timed out. Aug 15 17:06:36 Tower afpd[5188]: enumerate(vid:8, did:2, name:'.'): error adding dir: 'Films' (Errors) Aug 15 17:06:36 Tower shfs/user: duplicate object: /mnt/disk4/Media/.DS_Store (Minor Issues) Aug 15 17:06:36 Tower cnid_metad[11998]: Multiple attempts to start CNID db daemon for "/mnt/user/Media" failed, wiping the slate clean... (Minor Issues) Aug 15 17:06:36 Tower cnid_dbd[11998]: Set syslog logging to level: LOG_NOTE Aug 15 17:06:36 Tower cnid_dbd[11998]: Error opening lockfile: Permission denied (Errors) Aug 15 17:06:36 Tower cnid_dbd[11998]: main: fatal db lock error (Errors) Aug 15 17:06:36 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:36 Tower cnid_metad[1476]: error in sendmsg: Broken pipe (Errors) Aug 15 17:06:36 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:37 Tower cnid_dbd[12020]: Set syslog logging to level: LOG_NOTE Aug 15 17:06:37 Tower cnid_dbd[12020]: Error opening lockfile: Permission denied (Errors) Aug 15 17:06:37 Tower cnid_dbd[12020]: main: fatal db lock error (Errors) Aug 15 17:06:37 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:57 Tower last message repeated 21 times Aug 15 17:06:57 Tower afpd[5188]: transmit: Request to dbd daemon (db_dir /mnt/user/Media) timed out. Aug 15 17:06:57 Tower afpd[5188]: enumerate(vid:8, did:2, name:'.'): error adding dir: 'Films' (Errors) Aug 15 17:06:58 Tower shfs/user: duplicate object: /mnt/disk4/Media/.DS_Store (Minor Issues) Aug 15 17:06:58 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:07:16 Tower last message repeated 19 times Aug 15 17:07:17 Tower cnid_dbd[12437]: Set syslog logging to level: LOG_NOTE Aug 15 17:07:17 Tower cnid_dbd[12437]: Error opening lockfile: Permission denied (Errors) Aug 15 17:07:17 Tower cnid_dbd[12437]: main: fatal db lock error (Errors) Aug 15 17:07:17 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:07:18 Tower cnid_dbd[12454]: Set syslog logging to level: LOG_NOTE Aug 15 17:07:18 Tower cnid_dbd[12454]: Error opening lockfile: Permission denied (Errors) Aug 15 17:07:18 Tower cnid_dbd[12454]: main: fatal db lock error (Errors) Aug 15 17:07:18 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:07:19 Tower cnid_metad[12455]: Multiple attempts to start CNID db daemon for "/mnt/user/Media" failed, wiping the slate clean... (Minor Issues) Aug 15 17:07:19 Tower cnid_dbd[12455]: Set syslog logging to level: LOG_NOTE Aug 15 17:07:19 Tower cnid_dbd[12455]: Error opening lockfile: Permission denied (Errors) Aug 15 17:07:19 Tower cnid_dbd[12455]: main: fatal db lock error (Errors) Aug 15 17:07:19 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:07:19 Tower afpd[5188]: transmit: Request to dbd daemon (db_dir /mnt/user/Media) timed out. Aug 15 17:07:19 Tower afpd[5188]: enumerate(vid:8, did:2, name:'.'): error adding dir: 'Films' (Errors) Aug 15 17:07:34 Tower logger: Mon Aug 15 17:05:33 BST 2011 - Hard Drives active, resetting counter Aug 15 17:07:36 Tower shfs/user: duplicate object: /mnt/disk4/Media/.DS_Store (Minor Issues) Aug 15 17:07:37 Tower cnid_dbd[12754]: Set syslog logging to level: LOG_NOTE Aug 15 17:07:37 Tower cnid_dbd[12754]: Error opening lockfile: Permission denied (Errors) Aug 15 17:07:37 Tower cnid_dbd[12754]: main: fatal db lock error (Errors) Aug 15 17:07:37 Tower afpd[5188]: read: Connection reset by peer and OS X Lion is throwing "Something wrong with the volume's CNID DB, using temporary CNID DB instead" errors. Help?! Quote Link to comment
savestheday Posted August 15, 2011 Share Posted August 15, 2011 Having some serious issues with my server atm. Aug 15 17:06:15 Tower shfs/user: duplicate object: /mnt/disk4/Media/.DS_Store (Minor Issues) Aug 15 17:06:15 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:30 Tower last message repeated 17 times Aug 15 17:06:31 Tower ntpd_intres[1135]: DNS pool.ntp.org -> 192.53.103.108 Aug 15 17:06:31 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:32 Tower ntpd[1125]: Listen normally on 2 eth0 192.168.1.110 UDP 123 (Network) Aug 15 17:06:32 Tower ntpd[1125]: new interface(s) found: waking up resolver Aug 15 17:06:32 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:34 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:34 Tower logger: Mon Aug 15 17:05:33 BST 2011 - Hard Drives active, resetting counter Aug 15 17:06:35 Tower cnid_dbd[11940]: Set syslog logging to level: LOG_NOTE Aug 15 17:06:35 Tower cnid_dbd[11940]: Error opening lockfile: Permission denied (Errors) Aug 15 17:06:35 Tower cnid_dbd[11940]: main: fatal db lock error (Errors) Aug 15 17:06:35 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:36 Tower cnid_dbd[11997]: Set syslog logging to level: LOG_NOTE Aug 15 17:06:36 Tower cnid_dbd[11997]: Error opening lockfile: Permission denied (Errors) Aug 15 17:06:36 Tower cnid_dbd[11997]: main: fatal db lock error (Errors) Aug 15 17:06:36 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:36 Tower afpd[5188]: transmit: Request to dbd daemon (db_dir /mnt/user/Media) timed out. Aug 15 17:06:36 Tower afpd[5188]: enumerate(vid:8, did:2, name:'.'): error adding dir: 'Films' (Errors) Aug 15 17:06:36 Tower shfs/user: duplicate object: /mnt/disk4/Media/.DS_Store (Minor Issues) Aug 15 17:06:36 Tower cnid_metad[11998]: Multiple attempts to start CNID db daemon for "/mnt/user/Media" failed, wiping the slate clean... (Minor Issues) Aug 15 17:06:36 Tower cnid_dbd[11998]: Set syslog logging to level: LOG_NOTE Aug 15 17:06:36 Tower cnid_dbd[11998]: Error opening lockfile: Permission denied (Errors) Aug 15 17:06:36 Tower cnid_dbd[11998]: main: fatal db lock error (Errors) Aug 15 17:06:36 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:36 Tower cnid_metad[1476]: error in sendmsg: Broken pipe (Errors) Aug 15 17:06:36 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:37 Tower cnid_dbd[12020]: Set syslog logging to level: LOG_NOTE Aug 15 17:06:37 Tower cnid_dbd[12020]: Error opening lockfile: Permission denied (Errors) Aug 15 17:06:37 Tower cnid_dbd[12020]: main: fatal db lock error (Errors) Aug 15 17:06:37 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:06:57 Tower last message repeated 21 times Aug 15 17:06:57 Tower afpd[5188]: transmit: Request to dbd daemon (db_dir /mnt/user/Media) timed out. Aug 15 17:06:57 Tower afpd[5188]: enumerate(vid:8, did:2, name:'.'): error adding dir: 'Films' (Errors) Aug 15 17:06:58 Tower shfs/user: duplicate object: /mnt/disk4/Media/.DS_Store (Minor Issues) Aug 15 17:06:58 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:07:16 Tower last message repeated 19 times Aug 15 17:07:17 Tower cnid_dbd[12437]: Set syslog logging to level: LOG_NOTE Aug 15 17:07:17 Tower cnid_dbd[12437]: Error opening lockfile: Permission denied (Errors) Aug 15 17:07:17 Tower cnid_dbd[12437]: main: fatal db lock error (Errors) Aug 15 17:07:17 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:07:18 Tower cnid_dbd[12454]: Set syslog logging to level: LOG_NOTE Aug 15 17:07:18 Tower cnid_dbd[12454]: Error opening lockfile: Permission denied (Errors) Aug 15 17:07:18 Tower cnid_dbd[12454]: main: fatal db lock error (Errors) Aug 15 17:07:18 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:07:19 Tower cnid_metad[12455]: Multiple attempts to start CNID db daemon for "/mnt/user/Media" failed, wiping the slate clean... (Minor Issues) Aug 15 17:07:19 Tower cnid_dbd[12455]: Set syslog logging to level: LOG_NOTE Aug 15 17:07:19 Tower cnid_dbd[12455]: Error opening lockfile: Permission denied (Errors) Aug 15 17:07:19 Tower cnid_dbd[12455]: main: fatal db lock error (Errors) Aug 15 17:07:19 Tower afpd[5188]: read: Connection reset by peer Aug 15 17:07:19 Tower afpd[5188]: transmit: Request to dbd daemon (db_dir /mnt/user/Media) timed out. Aug 15 17:07:19 Tower afpd[5188]: enumerate(vid:8, did:2, name:'.'): error adding dir: 'Films' (Errors) Aug 15 17:07:34 Tower logger: Mon Aug 15 17:05:33 BST 2011 - Hard Drives active, resetting counter Aug 15 17:07:36 Tower shfs/user: duplicate object: /mnt/disk4/Media/.DS_Store (Minor Issues) Aug 15 17:07:37 Tower cnid_dbd[12754]: Set syslog logging to level: LOG_NOTE Aug 15 17:07:37 Tower cnid_dbd[12754]: Error opening lockfile: Permission denied (Errors) Aug 15 17:07:37 Tower cnid_dbd[12754]: main: fatal db lock error (Errors) Aug 15 17:07:37 Tower afpd[5188]: read: Connection reset by peer and OS X Lion is throwing "Something wrong with the volume's CNID DB, using temporary CNID DB instead" errors. Help?! I ran this script from Nezil to get rid of all my db files: /etc/rc.d/rc.atalk stop cd /mnt find disk*/ -name .AppleD* -exec rm -r {} \; That fixed it for me. It should recreate them after that. The other thing I did was follow Nezil's instructions a few pages back to edit the default location. Been working a lot better since then. Quote Link to comment
PeterB Posted August 16, 2011 Share Posted August 16, 2011 I believe that the circumstances I encountered the other night represents a problem in unRAID, but I'm not sure whether it applies only to current betas. I first reported it in this thread. I left the machine doing a non-correcting parity check during which there was a power cut. At the time I left it, everything was proceeding perfectly normally and there were no errors being reported. For reasons which are not important, apcupsd was not active, so the machine experienced the power cut when the ups battery expired. When power was restored, and the system restarted, it appears that it began performing a correcting parity check. At some point during this sequence of events, a data drive failed, and unRAID/unMENU was reporting "Parity updated 67 times to address sync errors". Now, if parity was being updated because one of the data drives had failed, this would seem to be a serious problem, almost certainly resulting in corruption/loss of data when a drive replacement/recovery is performed. I would be much happier if I knew that a correcting parity check could only be initiated as a deliberate choice by the user. It would also be much more secure if any corrections were suspended immediately any drive error occurs. Quote Link to comment
bcbgboy13 Posted August 16, 2011 Share Posted August 16, 2011 I did not have any problems running beta 10 (apart from something odd) Regarding the slow speed reported by many: I recently performed "swap-disable" - replaced the old 2TB WD EARS parity disk with precleared 3TB Hitachi Green and then in the same shot used the older parity disk to upgrade 1TB Hitachi data disk. Results: Aug 7 16:45:39 unraid emhttp: writing GPT on disk 0 (sdg) with partition 1 offset 64 Aug 7 16:45:39 unraid emhttp: shcmd (130): sgdisk -Z /dev/sdg &> /dev/null Aug 7 16:45:41 unraid kernel: sdg: sdg1 Aug 7 16:45:41 unraid emhttp: shcmd (131): sgdisk -o -a 64 -n 1:64:0 /dev/sdg |& logger Aug 7 16:45:42 unraid logger: Creating new GPT entries. Aug 7 16:45:42 unraid logger: The operation has completed successfully. Aug 7 16:45:42 unraid emhttp: shcmd (132): udevadm settle Aug 7 16:45:42 unraid kernel: sdg: sdg1 Aug 7 16:45:42 unraid emhttp: copying disk2 to disk0... Aug 7 17:15:41 unraid apcupsd[1445]: Power failure. Aug 7 17:15:43 unraid apcupsd[1445]: Power is back. UPS running on mains. Aug 7 18:31:10 unraid apcupsd[1445]: Power failure. Aug 7 18:31:12 unraid apcupsd[1445]: Power is back. UPS running on mains. Aug 7 23:03:07 unraid apcupsd[1445]: Power failure. Aug 7 23:03:09 unraid apcupsd[1445]: Power is back. UPS running on mains. Aug 8 03:00:08 unraid emhttp: Start array... Aug 8 03:00:08 unraid kernel: mdcmd (45): start SWAP_DSBL Aug 8 03:00:08 unraid kernel: unraid: allocating 54200K for 1280 stripes (10 disks) ... Aug 8 11:08:31 unraid kernel: md: sync done. time=29292sec Aug 8 11:08:31 unraid kernel: md: recovery thread sync completion status: 0 This one resulted in something odd - the interface states that my last parity check was done more than 15000 hours ago (in red color) So I did a parity check: Aug 8 23:36:57 unraid kernel: mdcmd (70): check NOCORRECT Aug 8 23:36:57 unraid kernel: md: recovery thread woken up ... Aug 8 23:36:57 unraid kernel: md: recovery thread checking parity... Aug 8 23:36:57 unraid kernel: md: using 1152k window, over a total of 2930266532 blocks. ... Aug 9 13:07:09 unraid kernel: md: sync done. time=48609sec Aug 9 13:07:09 unraid kernel: md: recovery thread sync completion status: 0 48609 seconds are 810 minutes or app. 61.7 MB/s This is 10 disk system (6 on the MB SATA and 4 on an M1015 card in PCIe x8 port). Unfortunately I do not recall the speed of the previous checks... Quote Link to comment
Interstellar Posted August 17, 2011 Share Posted August 17, 2011 Having the array stop issue now. Have to force restart it to get anywhere! Quote Link to comment
mejutty Posted August 23, 2011 Share Posted August 23, 2011 I don't know if i'm the only one having the issue but when I set my timezone to +8 for Perth Australia and then set ntp time when the server is rebooted it writes the time back to the bios as UTC time which is my time -8, what then happens is the server boots, starts up with the UTC time that is now in bios then ntp gets the correct time 8 hours ahead and all my disk spin down straight away. The ony way I have been able to get consistant time is the set UTC timezone and turn off ntp. Quote Link to comment
Whaler_99 Posted January 16, 2012 Share Posted January 16, 2012 Still running Beta 10 as it has been pretty solid for me. Waiting for the rest of the beta's to work out their bugs. My server has been fine for months - then suddenly tonight it powered itself down. Not sure why - no alerts due to power failure (and there was not one, I am at home). Just shut itself down. Can someone review the log for me and see if they can see why? Log is large - but the powerdown was tonight, Jan 15, 23:00 - just after that. Thx, Shawn syslog-20120115-230805.zip Quote Link to comment
PeterB Posted January 16, 2012 Share Posted January 16, 2012 No indication as to why but, at 23:06:01, someone, or something, invoked Powerdown! Jan 15 18:47:06 Tower sSMTP[13646]: Sent mail for root@ (221 2.0.0 closing connection q40sm44697382anh.18) uid=0 username=root outbytes=1892 Jan 15 23:06:01 Tower logger: Powerdown initiated Jan 15 23:06:01 Tower rc.unRAID[4589]: Stopping unRAID. The rest of the log messages are the normally system status logging which occurs on every controlled powerdown. Thie powerdown could have been invoked from a remote connection, but there is no evidence of a remote connection being established, the command being typed on a directly attached keyboard, or a short press on the power button. Quote Link to comment
Whaler_99 Posted January 16, 2012 Share Posted January 16, 2012 No indication as to why but, at 23:06:01, someone, or something, invoked Powerdown! Jan 15 18:47:06 Tower sSMTP[13646]: Sent mail for root@ (221 2.0.0 closing connection q40sm44697382anh.18) uid=0 username=root outbytes=1892 Jan 15 23:06:01 Tower logger: Powerdown initiated Jan 15 23:06:01 Tower rc.unRAID[4589]: Stopping unRAID. The rest of the log messages are the normally system status logging which occurs on every controlled powerdown. Thie powerdown could have been invoked from a remote connection, but there is no evidence of a remote connection being established, the command being typed on a directly attached keyboard, or a short press on the power button. Exactly my thoughts - I was just wondering if I had missed something. That server sits in the crawl space and I know no one hit the power button and I was not connected to it, via telnet or web. The weird thing, it was a controller powerdown, so no parity check when it booted up. Baffling. Shawn Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.