[Solved] OMV unexpected reboot - softdog unexpected close

frecurring · 7. Mai 2014

Hi all,

on a fresh installation of OMV, (sardaukar 0.5.46 on Pendium d with 3GB RAM) using 2x3TB WD in RAID1 and Plex installed using commandline and other official plug-in, I'm experimenting unesxpeted reboot
What i've seen on console monitor is a message "softdog unexpected close not stopping watchdog" and after few secondo a system reboot. :roll:

The system log doens't say anything but minor (usb errors).

I'm not able to say if it appens most when I stream video or not at moment.
Any idea what's happening and why ? Anyone has experienced the same or similar issues?

thnks,

--

Frecurring

votdev · 7. Mai 2014

The watchdog does not get triggered during a given time, thus it forces a reboot. This can occur if your system is under heavy load.

frecurring · 7. Mai 2014

Hi votdev,

thanks for your reply.

So every time CPU goes 100% i should expect a reboot ?
With my old installation using same sowftware but old HD (for test purposes) I've never experienced the problem.

How may I debug in detail what's causign the softdog not being touched ?

--

Frecurring

votdev · 7. Mai 2014

No, the watchdog does not get triggered when CPU goes >= 100%, otherwise it would be a really bad feature or behaviour.
YOu have to find out what causes the watchdog daemon not to write to the device file which is checked by the kernel every N seconds. If this write does not happen within this time the kernel triggers the reboot. So you have to find out if it is possible that the watchdog daemon was killed unexpected/unregulary..

frecurring · 7. Mai 2014

Hi votdev,

i'm trying to understand better the problem.

I see during the omv startup process

...
starting watchdog keepalive daemon: wd_keepalive
stopping watchdog keepalive daemom
stopping watchdog daemon
...

checking ps -ef and wd_keepalive is not running

I can confirm softdog message and reboot happens whenduring PLEX Media content streaming to my TV.

does it is normal the wd_keepalive start and stop during start-up process and is not running ?

thanks

davidh2k · 7. Mai 2014

Zitat

I can confirm softdog message and reboot happens whenduring PLEX Media content streaming to my TV.

Volker said it could be due to high load that the watchdog gets triggered. What has your NAS for specs? How high is the load when streaming content?

Greetings
David

frecurring · 8. Mai 2014

Hi,

sardaukar 0.5.46 on Pendium D 2.8 GHz with 3GB RAM, WD red RAID 1
CPU go to 100% during streaming if this is what you mean with "how high ..."

Receiving also some faithful email
Date: Thu, 08 May 2014 05:37:32 +0100
Action: alert
Host: OMVHome
Description: cpu user usage of 100.0% matches resource limit [cpu user usage>95.0%

BTW
Yesterday i've experimented reboot and Plex was non streaming anything :cry:

frecurring · 8. Mai 2014

HI all,

coming back to home I've discovered that the RAID 1 (just setup few days ago with a fresh OMV installation) in resynch state :cry:

the output of the mdstat if the following

root@OMVHome:~# cat /proc/mdstat
Personalities : [raid1]
md127 : active raid1 sdb[0] sda[1]
2930265424 blocks super 1.2 [2/2] [UU]
[>....................] resync = 1.1% (34032128/2930265424) finish=2864.6min speed=16850K/sec

unused devices: <none>

and trying to improve speed resynch again

root@OMVHome:~# mdadm --grow --bitmap=internal /dev/md127
mdadm: failed to set internal bitmap.

i'm wondering if there is something wrong with HD or with HW in general

the resynch state is due to continue reboot in your opinion ?
any idea / suggestion ?

thanks

frecurring · 9. Mai 2014

HI all,

cause week-end is coming I'm going to enjoy free-time trying to solve the issues encountered.

I've found one error in one disk as follows :

Code

======================================================================


root@OMVHome:~# smartctl --all /dev/sda 
smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net


=== START OF INFORMATION SECTION ===
Device Model:     WDC WD30EFRX-68EUZN0
Serial Number:    WD-..
Firmware Version: 80.00A80
User Capacity:    3,000,592,982,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   9
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Fri May  9 17:37:33 2014 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED


General SMART Values:
Offline data collection status:  (0x80)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		 (37800) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 255) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x703d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.


SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   181   180   021    Pre-fail  Always       -       5950
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       65
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       108
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       19
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       11
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       133
194 Temperature_Celsius     0x0022   119   107   000    Old_age   Always       -       31
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0


SMART Error Log Version: 1
ATA Error Count: 1
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
[b][u]
Error 1 occurred at disk power-on lifetime: 1 hours (0 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.[/u][/b]


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 01 00 00 00 00  Error: ABRT


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d5 01 e1 4f c2 00 08      00:55:35.490  SMART READ LOG
  b0 d5 01 e1 4f c2 00 08      00:55:35.490  SMART READ LOG
  b0 d6 01 e0 4f c2 00 08      00:55:35.489  SMART WRITE LOG
  b0 d6 01 e0 4f c2 00 08      00:55:35.488  SMART WRITE LOG
  b0 d5 01 e0 4f c2 00 08      00:55:35.488  SMART READ LOG


SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]




SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


======================================================================

Alles anzeigen

My idea is start from scratch and trying to rebuild RAID 1 array again.

So my question what should be the right procedure/steps to rightly dismantle the RAID 1 array ?
do I need to erase the superblock information before reuse the two disks on array building ?
because the HDD is still in the return back time policy do you think I should return the HDD ?

thanks for your help,

frecurring · 22. Mai 2014

I finally found that there was a faulty RAM memory banks

I removed the RAM banks and the problem has disappeared but in the meantime it has corrupted the filesystem

I re-installed everything again.

WastlJ · 23. Mai 2014

I recently read an IT blog that the strangest problems can occur with faulty ram banks... Need to keep that in mind.

Glad you found your problem!

frecurring · 23. Mai 2014

It was really a PAIN and time consuming :o

the real error I did is introduce 2 different impovements at the same time.

I introduced the
1) RAM banks and
2) reinstall everything using a new Disk

Fre

Jetzt mitmachen!