Re: v20z ongoing death situation

In article <PKSdnY_rBtAJjabVnZ2dnUVZ_j-dnZ2d@xxxxxxxxxx>,
"Trinean" <trinean@xxxxxxxxx> wrote:

Here's all I could find:

http://bugs.opensolaris.org/view_bug.do?bug_id=6582327

Hopefully you can figure out how to boot off the DVD-ROM.
According to the bug it's probably an out-of-sync boot archive.

Thanks for that: it's pretty helpful and gives me a plan of attack once I
get the v20z booted. It will require a trip to the co-lo but I should be
able to boot into "safe mode" from GRUB.

I think it was patch 120012 (-14 in my case) that did for me too.

--

Sak Wathanasin
Network Analysis Limited
http://www.network-analysis.ltd.uk
.

Relevant Pages

  • Re: "superblock last write time is in the future" on boot
    ... > the fsck portion of boot. ... e2fsprogs has no bug at all. ... "One disk to rule them all, ...
    (Debian-User)
  • Re: Booting directly into X problems
    ... if I first boot into winxp and then reboot into ... > bug that is related to the 845 video card there. ... reboot to FC2 it works or cold-boot in linux but in "Interactive mode". ...
    (Fedora)
  • Re: What is going on with fbreseal?
    ... When I boot for the first time after fbreseal, ... please add SOS and BOOTLOG switches to your boot.ini to see where it hangs. ... Must be a bug. ... If it doesn't work for you the same way, you want to report the bug to MS using the link provided above. ...
    (microsoft.public.windowsxp.embedded)
  • Re: "superblock last write time is in the future" on boot
    ... >> the fsck portion of boot. ... > e2fsprogs has no bug at all. ... > "One disk to rule them all, ...
    (Debian-User)
  • Linux 2.6.17: PM-Timer bug warning?
    ... BIOS-provided physical RAM map: ... 127MB HIGHMEM available. ... Simple Boot Flag value 0x87 read from CMOS RAM was invalid ... * This chipset may have PM-Timer Bug. ...
    (Linux-Kernel)