Goodmorning 2 ya all
I updated to version 3.1 and works fine.. but we encounter some problem regarding the update. I would like to tell about my experience about this here. Short version:
Error: "Wont reboot"
Solution: manual reboot
OK so I've uploaded the 3.1 one binary (md5 checked it before). This through the shell (ssh) with the sysadmin account. We have two boxes.. I did this on both at same time (should take one at the time). I bpstop the master server but should do that then the script didnt find my master and stopped. So manually stopped the SLP exclude the date for the actual time in the schedule, wont have any interference on our 5240:s. (here Vertias should develeoped some script to stop enough items on master so that upgrade of deduplication nodes could be done.)
Started the update install <file> enter and prechecked went good, the guide https://www.veritas.com/support/en_US/article.000116014 tells that there will be severeal reboots but (actually three). OK so after waiting for 2.5 hours.. we waited for 1 hour more.. Now something was wrong.
OK now we had checked that the box was in some idle status. And this what we did to get it to work:
Regards Pontus Ankarbåge
We are seeing the same behaviour with one of our 5240 appliances as well, since the 3.1 update. And like your are describing, it takes two resets. If you look on the console, you will probably see the kernel panic. We have had a case open for a while.
There is a tech note for kernel panics with certain conditions and 10GigE cards, but no solution yet: https://www.veritas.com/support/en_US/article.100033703
There is another tech note for kernel panics attributed to FC/SAN connections, this one has a hotfix provided: https://www.veritas.com/support/en_US/article.100040686.html
We also experienced the 'spoold' daemon crash problem after the 3.1 update, which was a major pain, at least there is a fix for that one: https://www.veritas.com/support/en_US/article.100041057