[OpenIndiana-discuss] krtld failed to open, again...

[Jim Klimov]

15 июня 2016 г. 8:25:26 CEST, Gabriele Bulfon <gbulfon at sonicle.com> пишет:
>Wow!!!! Jim you saved me! :)) I found around 20 entries in menu.lst,
>removed 10 and now it boots!!!! :))))
>Also, you saved my original boot SSD that I thought to be corrupted and
>not safe to use.
>I'm sure I can do the same on it and it will boot again too!
>Thanks so much Jim!
>Question: how can we be warned by the system about a possible too big
>menu.lst before "the happening"?
>Gabriele
>----------------------------------------------------------------------------------------
>Sonicle S.r.l.
>:
>http://www.sonicle.com
>Music:
>http://www.gabrielebulfon.com
>Quantum Mechanics :
>http://www.cdbaby.com/cd/gabrielebulfon
>----------------------------------------------------------------------------------
>Da: Jim Klimov
>A: Discussion list for OpenIndiana
>Gabriele Bulfon
>Data: 14 giugno 2016 20.30.32 CEST
>Oggetto: Re: [OpenIndiana-discuss] krtld failed to open, again...
>14 ???? 2016 ?. 18:59:02 CEST, Gabriele Bulfon
>?????:
>Thanks, I will check this.
>Anyway I'm still not sure the problem can be the grub, because grub
>loads, shows the boot environments, let me choose the active one, and
>then here it fails when running any be.
>Do you still think installgrub can fix it?
>----------------------------------------------------------------------------------------
>Sonicle S.r.l.
>:
>http://www.sonicle.com
>Music:
>http://www.gabrielebulfon.com
>Quantum Mechanics :
>http://www.cdbaby.com/cd/gabrielebulfon
>----------------------------------------------------------------------------------
>Da: Nikola M
>A: Discussion list for OpenIndiana
>Data: 14 giugno 2016 10.51.09 CEST
>Oggetto: Re: [OpenIndiana-discuss] krtld failed to open, again...
>On 06/14/16 10:35 AM, Gabriele Bulfon wrote:
>Thanks Nikola, I think it may be caused by a power down here that
>turned off the machine not behind an ups.
>Machine is a NAS like machine, with 4 sata disks and an SSD.
>Because SSD failed once with a similar problem, I didn't feel safe
>using it again as boot, so I reinstalled on a free small SATA, keeping
>dev data on a raidz pool of 3 sata.
>Now the same with the sata boot...
>It's not the first time I have machines going down for power failure,
>but never lost a zpool.
>Actually, the rpool can be imported, but just can't boot showing those
>grabled unix path error.
>I tried booting from DVD, shell, mounting rpool on /a and forcing a
>rebuild via bootadm update-archive -R /a -v : archive were correctly
>rebuilt, but still can't boot, looking for a garbled unix path.
>How can I just reinstall grub keeping the rpool safe? Will it keep my
>boot environments?
>Thanks!
>Gabriele
>Firstly backup everything if not already, to external HD, that could be
>detached physically.
>See if this helps:
>http://wiki.openindiana.org/oi/How+to+migrate+the+root+pool
>http://wiki.openindiana.org/oi/Boot+hangs
>http://wiki.openindiana.org/oi/Advanced+-+Manual+installation+of+OpenIndiana+from+LiveCD+media
>/sbin/installgrub /boot/grub/stage1 /boot/grub/stage2
>/dev/rdsk/c2t0d0s0
>_______________________________________________
>openindiana-discuss mailing list
>openindiana-discuss at openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss
>_______________________________________________
>openindiana-discuss mailing list
>openindiana-discuss at openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss
>Just in case: how many grub menu entries do you have? Maybe you're
>hitting its RAM constraint? Roughly 25 entries are too many, and it
>overflows...
>If this matches, try booting from a livedvd again and edit the
>rpool/boot/grub/menu.lst (IIRC OTOH).
>Hope this helps,
>Jim
>--
>Typos courtesy of K-9 Mail on my Samsung Android
>_______________________________________________
>openindiana-discuss mailing list
>openindiana-discuss at openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss

I have the warning in my zfs-split-root scripts that I update my oi and omnios systems with ;)

Feel free to include a copy into your distro and/or push for porting the logic into common illumos ;p

Probably a warning belongs in beadm or bootadm (the latter wraps menu management iirc), and it is not a firm limit of X etntries - depends on grub code and menu entry sizings, as well as on being an issue with grub-0.97 based loader (not sparc, not grub2 etc.).

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android