the syslog is being filled continuously with this.

 

Aug 16 13:09:24 Tower kernel: md: could not read superblock from /boot/config/super.dat
Aug 16 13:09:24 Tower kernel: md: initializing superblock
Aug 16 13:09:24 Tower emhttp: shcmd (616): udevadm settle
Aug 16 13:09:24 Tower emhttp: Device inventory:
Aug 16 13:09:24 Tower emhttp: WDC_WD30EZRS-00J99B0_WD-WCAWZ0263675 (sda) 2930266584
Aug 16 13:09:24 Tower emhttp: shcmd (617): /usr/local/sbin/emhttp_event driver_loaded
Aug 16 13:09:24 Tower emhttp_event: driver_loaded
Aug 16 13:09:24 Tower kernel: mdcmd (1): import 0 0,0
Aug 16 13:09:24 Tower kernel: mdcmd (2): import 1 0,0
Aug 16 13:09:24 Tower kernel: mdcmd (3): import 2 0,0
Aug 16 13:09:29 Tower emhttp: shcmd (618): rmmod md-mod |& logger
Aug 16 13:09:29 Tower emhttp: shcmd (619): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger
Aug 16 13:09:29 Tower emhttp: shcmd (620): udevadm settle
Aug 16 13:09:29 Tower kernel: md: unRAID driver removed
Aug 16 13:09:29 Tower kernel: md: unRAID driver 2.1.4 installed
Aug 16 13:09:29 Tower kernel: read_file: error 2 opening /boot/config/super.dat
Aug 16 13:09:29 Tower kernel: md: could not read superblock from /boot/config/super.dat
Aug 16 13:09:29 Tower kernel: md: initializing superblock
Aug 16 13:09:29 Tower emhttp: Device inventory:
Aug 16 13:09:29 Tower emhttp: WDC_WD30EZRS-00J99B0_WD-WCAWZ0263675 (sda) 2930266584
Aug 16 13:09:29 Tower emhttp: shcmd (621): /usr/local/sbin/emhttp_event driver_loaded
Aug 16 13:09:29 Tower emhttp_event: driver_loaded
Aug 16 13:09:29 Tower kernel: mdcmd (1): import 0 0,0
Aug 16 13:09:29 Tower kernel: mdcmd (2): import 1 0,0
Aug 16 13:09:29 Tower kernel: mdcmd (3): import 2 0,0
Aug 16 13:09:34 Tower emhttp: shcmd (622): rmmod md-mod |& logger
Aug 16 13:09:34 Tower emhttp: shcmd (623): modprobe md-mod super=/boot/config/super.dat slots=3 |& logger
Aug 16 13:09:34 Tower emhttp: shcmd (624): udevadm settle
Aug 16 13:09:34 Tower kernel: md: unRAID driver removed
Aug 16 13:09:34 Tower kernel: md: unRAID driver 2.1.4 installed
Aug 16 13:09:34 Tower kernel: read_file: error 2 opening /boot/config/super.dat
Aug 16 13:09:34 Tower kernel: md: could not read superblock from /boot/config/super.dat
Aug 16 13:09:34 Tower kernel: md: initializing superblock
Aug 16 13:09:34 Tower emhttp: Device inventory:
Aug 16 13:09:34 Tower emhttp: WDC_WD30EZRS-00J99B0_WD-WCAWZ0263675 (sda) 2930266584
Aug 16 13:09:34 Tower emhttp: shcmd (625): /usr/local/sbin/emhttp_event driver_loaded
Aug 16 13:09:34 Tower emhttp_event: driver_loaded
Aug 16 13:09:34 Tower kernel: mdcmd (1): import 0 0,0
Aug 16 13:09:34 Tower kernel: mdcmd (2): import 1 0,0
Aug 16 13:09:34 Tower kernel: mdcmd (3): import 2 0,0
Aug 16 13:09:39 Tower emhttp: shcmd (626): rmmod md-mod |& logger

 

this is 5.0-rc5-r8168 on a new installation.

 

currently no drives are assigned to the array as it is pre-clearing a new 3.0T drive.

this only seems to occur when I log in.

 

i.e. no events over night. first thing this morning at 07:32 it started up again.

Ok, this occuring when i am navigated to http://tower/Main or any other sub-dir.

 

currently simplefeatures webGUI is installed and when the current pre-clear is done I will remove it and reboot and check this again.

 

 

its either a webGUI thing or a simplefeatures thing, will follow up.

Ok, this occuring when i am navigated to http://tower/Main or any other sub-dir.

 

currently simplefeatures webGUI is installed and when the current pre-clear is done I will remove it and reboot and check this again.

 

 

its either a webGUI thing or a simplefeatures thing, will follow up.

It will appear every time the web-interface refreshes itself while the array is stopped.   

(with or without simple-features, but simple-features might refresh the interface more often)

every 5 seconds by my count.

 

is this a bug or by design?

every 5 seconds by my count.

 

is this a bug or by design?

The messages are there by design every time you refresh the web-interface when the array is stopped.

 

I think it is simple-features that is refreshing the screen every 5seconds for you.  The combination results in the large number of messages.

ok then, simple features is outta here. This is just a pre-clear system...