From: joe fletcher (joe_fletcher@btconnect.com)
Date: Mon Sep 11 2006 - 03:36:01 EDT
Hi All,
Thanks to Armin and John for their responses. Armin's suggestion (f/w update changed WWID of the drives and broke the DDR db) seems the most probable cause though in the end I've restored the system from backups and used this as an opportunity to move the system disk images from the internal drive bay to a mirror in the attached RAID array.
Armin wrote:
"try this link
http://unix.derkeiler.com/Mailing-Lists/Tru64-UNIX-Managers/2004-08/0099.html
"
It isn't clear to me why the linux install which was on another of the internal drives also broke since I'm guessing it doesn't use the DDR db.
The system is working again which is what counts.
Cheers
Joe
---------------------------------- originally -----------------------------------
I've got an ES40 running 5.1b. I've just updated the drive firmware and now the system won't boot. It fails with a message "kernel stack invalid, halt code =2 ". Boot block loads ok before the crash
For info there's another drive in the internal bay which holds a linux installation and it won't boot either, so it seems the firmware update is definitely the issue.
Any ideas of how this can be fixed? I can't easily downgrade the firmware as I don't have a record of the old version (Doh!).
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:31 EDT