February 4, 201313 yr Unraid 4.7 Just had a failure yesterday on my very stable system (other then drive failures) Lost drive 7 and the Cache drive. Could not cleanly power down the array as something was trying to deal with the cache drive, but kept failing - syslog was over 2GB and growing fast. Powered off the array, replaced drive 7, removed the cache drive (don't have another one kicking around here) Powered back up. Unassigned the cache drive, started the array. Drive 7 is rebuilding. Lost all of my user shares. In the configuration they were all blank. all data and shares are on the disk. Tried recreating one of them (Media) creates the "file" in /mnt/user/Media, but no files. Tried restarting Samba no effect.. Any Ideas? SysLog attached since reboot and start of rebuild syslog-2013-02-04.txt
February 4, 201313 yr Let the rebuild complete, then reboot. File systems were being replayed so were not available when the user-shares were started. Oh yes, your UPS seems to think its battery needs to be replaced. eb 4 05:42:34 Tower kernel: REISERFS (device md2): checking transaction log (md2) Feb 4 05:43:21 Tower kernel: REISERFS (device md2): replayed 199 transactions in 47 seconds Feb 4 05:43:21 Tower kernel: REISERFS (device md2): Using r5 hash to sort names Feb 4 05:43:34 Tower kernel: REISERFS (device md1): replayed 237 transactions in 60 seconds Feb 4 05:43:35 Tower kernel: REISERFS (device md1): Using r5 hash to sort names Feb 4 05:43:48 Tower kernel: REISERFS (device md3): replayed 250 transactions in 74 seconds Feb 4 05:43:48 Tower kernel: REISERFS (device md3): Using r5 hash to sort names Feb 4 05:43:57 Tower kernel: REISERFS (device md4): replayed 358 transactions in 83 seconds Feb 4 05:43:57 Tower kernel: REISERFS (device md4): Using r5 hash to sort names Feb 4 05:45:13 Tower ntpd[1500]: synchronized to 192.75.12.11, stratum 2 Feb 4 05:46:24 Tower kernel: REISERFS (device md6): replayed 552 transactions in 230 seconds Feb 4 05:46:25 Tower kernel: REISERFS (device md6): Using r5 hash to sort names Feb 4 05:47:48 Tower kernel: REISERFS (device md5): replayed 957 transactions in 314 seconds Feb 4 05:47:48 Tower kernel: REISERFS (device md5): Using r5 hash to sort names Feb 4 05:47:56 Tower kernel: REISERFS (device md7): replayed 836 transactions in 322 seconds Feb 4 05:47:56 Tower kernel: REISERFS (device md7): Using r5 hash to sort names Feb 4 05:48:23 Tower kernel: REISERFS (device md8): replayed 2054 transactions in 349 seconds Feb 4 05:50:57 Tower apcupsd[10353]: UPS battery must be replaced Joe L.
February 4, 201313 yr Author Okay that makes a little more sense. The UPS has been complaining about that for about 6 months now, yet it still has 30mins runtime. I think it's tripping on battery age.
February 5, 201313 yr Author All good. thanks Joe. Also upgraded to RC11 - just need to start reading about the new pluggin system... time for more fun!
February 5, 201313 yr The UPS has been complaining about that for about 6 months now, yet it still has 30mins runtime. I think it's tripping on battery age. Are you sure about that? Claiming 30 min run time is usually just based on [assumed capacity] / [current usage]. Note my use of the word "assumed" and not ACTUAL. Have you ACTUALLY tested your UPS to make sure the battery capacity is up to snuff? Battery capacity does in fact decrease with age. 2-3 years for a UPS battery is about all you should expect, even less if it has poor ventilation. If it is repleacable, Batteries+ is a great place to get replacements.
February 5, 201313 yr The UPS has been complaining about that for about 6 months now, yet it still has 30mins runtime. I think it's tripping on battery age. Are you sure about that? Claiming 30 min run time is usually just based on [assumed capacity] / [current usage]. Note my use of the word "assumed" and not ACTUAL. Have you ACTUALLY tested your UPS to make sure the battery capacity is up to snuff? Unless you paid over $200 for the battery backup, I would seriously doubt that it could run the system for 30 minutes even when it was brand new. To get 30 minutes of loaded runtime, you are typically spending more than $400.
Archived
This topic is now archived and is closed to further replies.