Hi againā¦
Well the scrip does get run via corn. I have cron log enabled and I can see the script being called.
I had initially started off with network restart instead of a reboot ā¦didnāt try with if down and if up thoughā¦
I still think that the reason for the drive not rebooting as per my script when I run into this problem might be the fact the script is not readable at that pointā¦perhaps the data partition is not mounted?
I guess I will try moving the script to / or somethingā¦
What its worh this is messages log after the drive recoverd by pulling the power and powering it back onā¦
Issue occured at 14:03, i got home and power cycled it at around 18:05ā¦ The last line for the 14th hour, shows the network link coming up but then it stopped thereā¦Now that i think more about itā¦so if the logging stopped right there, the drive never proceeded to mount the paritions and thus it seems that the OS never loads completely in this situation and thus my script doesnt even come into playā¦Ā
Jun 25 14:04:43 nas1 kernel: [43.849187] PFE binary version: pfe_nas_2_00_3
Jun 25 14:04:43 nas1 kernel: [43.853696] pfe_firmware_init: class firmware loaded 0xbc0 0xc3010000
Jun 25 14:04:43 nas1 kernel: [43.860172] pfe_load_elf
Jun 25 14:04:43 nas1 kernel: [43.864893] pfe_firmware_init: tmu firmware loaded 0x1a0
Jun 25 14:04:43 nas1 kernel: [43.870233] pfe_load_elf
Jun 25 14:04:43 nas1 kernel: [43.875355] pfe_firmware_init: util firmware loaded 0x1220
Jun 25 14:04:43 nas1 kernel: [43.880914] pfe_ctrl_init
Jun 25 14:04:43 nas1 kernel: [43.913152] timer_add c30ae150
Jun 25 14:04:43 nas1 kernel: [43.916228] timer_add c30ae0f0
Jun 25 14:04:43 nas1 kernel: [43.919299] timer_add c30ae120
Jun 25 14:04:43 nas1 kernel: [43.922376] timer_add c30ae090
Jun 25 14:04:43 nas1 kernel: [43.925460] timer_add c30ae078
Jun 25 14:04:43 nas1 kernel: [43.928543] timer_add c30ae0a8
Jun 25 14:04:43 nas1 kernel: [43.932586] timer_add c30ae0c0
Jun 25 14:04:43 nas1 kernel: [43.935689] ipsec_common_hard_init ipsec_baseaddr:d0c00000 - espah_base:d0c00000
Jun 25 14:04:43 nas1 kernel: [43.944480] timer_add c30ae060
Jun 25 14:04:43 nas1 kernel: [43.947560] pfe_ctrl_init finished
Jun 25 14:04:43 nas1 kernel: [43.950980] pfe_eth_init
Jun 25 14:04:43 nas1 kernel: [43.952744] pfe_ctrl_timer
Jun 25 14:04:43 nas1 kernel: [43.967691] Comcerto MDIO Bus: probed
Jun 25 14:04:43 nas1 kernel: [43.975228] pfe_eth_init_one: preallocating rx & tx queue buffers
Jun 25 14:04:43 nas1 kernel: [43.981661] eth0: pfe_eth_init_one: created interface, baseaddr: d3200000
Jun 25 14:04:43 nas1 kernel: [43.988583] pfe_pcap_init
Jun 25 14:04:43 nas1 kernel: [56.998988] eth0: pfe_eth_open
Jun 25 14:04:43 nas1 kernel: [57.002204] hif_process_client_req: register client_id 0
Jun 25 14:04:43 nas1 kernel: [57.007595] pfe_hif_client_register
Jun 25 14:04:43 nas1 kernel: [57.011114] eth0: pfe_gemac_init
Jun 25 14:04:43 nas1 kernel: [57.014643] bcm54610_config_init: before 0x2c09, after 0x2c8c
Jun 25 14:04:43 nas1 kernel: [57.020673] bcm54610_config_init: before 0x01e1, 0x0300; after 0x0141, 0x0200
Jun 25 14:04:43 nas1 kernel: [62.023075] PHY: comcerto-0:00 - Link is Up - 1000/Full
Jun 25 18:05:35 nas1 kernel: [75.602532] jnl: driver (lke_9.0.0 lke_9.0.0_r233487_b2, LBD=ON) loaded at c30f0000
Jun 25 18:05:35 nas1 kernel: [75.687911] ufsd: module license āCommercial productā taints kernel.
Jun 25 18:05:35 nas1 kernel: [75.694408] Disabling lock debugging due to kernel taint
Jun 25 18:05:36 nas1 kernel: [75.742571] ufsd:: trace mask set to 0000000f
Jun 25 18:05:36 nas1 kernel: [75.747029] ufsd: driver (lke_9.0.0 lke_9.0.0_r233487_b2, LBD=ON, acl, ioctl, bdi, sd(0), fua, bz, tr) loaded at c3130000
Jun 25 18:05:36 nas1 kernel: [75.747042] NTFS support included
Jun 25 18:05:36 nas1 kernel: [75.747046] Hfs+/HfsJ support included
Jun 25 18:05:36 nas1 kernel: [75.747049] optimized: speed
Jun 25 18:05:36 nas1 kernel: [75.747053] Build_for__WD_Sequoia_k3.2.26_2014-08-07_lke_9.0.0_r233487_b2
Below is a normal boot up log. You can see that after the network link is up the data partition gets mounted few seconds later. Guess Iām answering my own questions now.
Can i use soemthing like chkconfig or something to prioritize some services? e.g leave network to come up later in the boot process? Porbably would have other implications!
Jun 9 23:15:17 nas1 kernel: [61.432868] PHY: comcerto-0:00 - Link is Up - 1000/Full
Jun 9 23:15:23 nas1 kernel: [76.633930] jnl: driver (lke_9.0.0 lke_9.0.0_r233487_b2, LBD=ON) loaded at c30f0000
Jun 9 23:15:23 nas1 kernel: [76.703485] ufsd: module license āCommercial productā taints kernel.
Jun 9 23:15:23 nas1 kernel: [76.709910] Disabling lock debugging due to kernel taint
Jun 9 23:15:24 nas1 kernel: [76.759281] ufsd:: trace mask set to 0000000f
Jun 9 23:15:24 nas1 kernel: [76.763730] ufsd: driver (lke_9.0.0 lke_9.0.0_r233487_b2, LBD=ON, acl, ioctl, bdi, sd(0), fua, bz, tr) loaded at c3130000
Jun 9 23:15:24 nas1 kernel: [76.763741] NTFS support included
Jun 9 23:15:24 nas1 kernel: [76.763745] Hfs+/HfsJ support included
Jun 9 23:15:24 nas1 kernel: [76.763749] optimized: speed
Jun 9 23:15:24 nas1 kernel: [76.763752] Build_for__WD_Sequoia_k3.2.26_2014-08-07_lke_9.0.0_r233487_b2
Jun 9 23:15:24 nas1 kernel: [76.763758]
Jun 9 23:15:29 nas1 kernel: [82.342621] EXT4-fs (sda4): barriers disabled
Jun 9 23:15:30 nas1 kernel: [83.615823] EXT4-fs (sda4): mounted filesystem with writeback data mode. Opts: acl,user_xattr,data=writeback,barrier=0,init_itable=10
Jun 9 23:15:30 nas1 kernel: [83.706213] EXT4-fs (sda4): re-mounted. Opts: user_xattr,barrier=0,data=writeback