Does anybody have a problem where a virtual machine with DSM5.0-4458 would shutdown every day a random time because of "disk overheating" ?
Disks are virtual, how can they overheat ?
Also from /var/log/messages i frequently have such errors :
Mar 25 15:05:01 DSMesxi5 SystemInfo.cgi: disk_info_get.c:82 Failed to open /dev/sdc, errno=No such file or directory
And last few lines before it shutdown :
Mar 19 19:20:42 DSMesxi5 root: /usr/syno/etc/rc.d/S40irqbalance.sh stopped irqbalance
Mar 19 19:20:47 DSMesxi5 synocheckshare: synocheckshare_vol_unmount.c:147 Unmount Share [iNTERNAL] [/dev/vg1000/lv] [/volume1
Mar 19 19:20:47 DSMesxi5 kernel: [ 1749.903284] md: md2: set sdd5 to auto_remap [0]
Mar 19 19:20:47 DSMesxi5 kernel: [ 1749.903286] md: md2: set sdf5 to auto_remap [0]
Mar 19 19:20:47 DSMesxi5 kernel: [ 1749.903288] md: md2: set sde5 to auto_remap [0]
Mar 20 18:34:06 DSMesxi5 findhostd: findhostd.c:119(FHOSTDProcessNameGet) open [/proc/30933/cmdline] fail:(2)[No such file or
Mar 20 18:34:06 DSMesxi5 findhostd: findhostd.c:69(FHOSTDExit) exit on signal[15]
Mar 20 18:34:06 DSMesxi5 root: /usr/syno/etc/rc.d/S98findhostd.sh stop findhostd
killall: synolunbkp: no process killed
Mar 20 18:34:11 DSMesxi5 root: /usr/syno/etc/rc.d/S40irqbalance.sh stopped irqbalance
Mar 20 18:34:15 DSMesxi5 synocheckshare: synocheckshare_vol_unmount.c:147 Unmount Share [iNTERNAL] [/dev/vg1000/lv] [/volume1
Mar 20 18:34:16 DSMesxi5 kernel: [27216.870381] md: md2: set sdd5 to auto_remap [0]
Mar 20 18:34:16 DSMesxi5 kernel: [27216.870383] md: md2: set sdf5 to auto_remap [0]
Mar 20 18:34:16 DSMesxi5 kernel: [27216.870385] md: md2: set sde5 to auto_remap [0]
And this are always the last line before each forced shutdown. Any info on that?
hello, I have the same problem as yours. Did you find a solution for this? Thanks.
XPEnology gnoBoot
in DSM 5.2 and earlier (Legacy)
Posted
hello, I have the same problem as yours. Did you find a solution for this? Thanks.