[OpenIndiana-discuss] System will not boot, boot-archive fails
Richard Patterson
richard at helpquick.co.uk
Tue Sep 22 09:21:57 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ok, I removed the controller again, booted it up fine, changed
time-out to 180.
Removed the backups zpool (zfs export), shutdown and re-installed the
controller.
Booted up fine.
zfs import -f backups
^^Hangs at this point.
A while ago, i had a script running in cron to report on zpool status,
etc.
I must admit, my checking of the reports was a bit lax of late, and I
found the last few had this in the status:
NAME STATE READ WRITE CKSUM
backups ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
c3t50014EE6AEEE4A0Bd0 ONLINE 0 0 0
c3t50014EE6AEEE5C8Bd0 ONLINE 0 0 0
c3t50014EE0591526CAd0 ONLINE 0 0 0
c3t50014EE659992C01d0 ONLINE 0 0 0
c3t50014EE6599926FBd0 ONLINE 0 0 12
c3t50014EE65999205Fd0 ONLINE 0 0 4
c3t50014EE659992081d0 ONLINE 0 0 0
c3t50014EE659993822d0 ONLINE 0 0 0
So, looks like I might have at least 1 failed disk... will need to try
to identify the failed one(s), and pull it / them out.
Thanks so far, I'll update when I've had a chance to pull the faulty
disk(s).
- --
Richard
On 21/09/2015 18:44, jason matthews wrote:
> try the following: delete the zpool cache, /etc/zfs/zpool.cache
> reboot the system, it should boot since it wont try to mount the
> backups zpool change the bootarchive time out to two minutes
> manually import the backups. clear the remaining services in
> maintenance mode
>
> that should get it going.
>
> you probably have a failing disk. reboot to see if the system can
> complete the boot procedure. if bootadm times out again, use
> iostat -nMxC to look for a disk that 100% busy or has outrageous
> svc times etc, or errors. you might even try looking for a disk
> with a solid activity light. if you find such a disk pull it.
>
> are you using "green" drives? green drives tend to spend down
> between 6 and 30 seconds which a problematic on zpool with a large
> number of disks.
>
> j.
>
> On 9/21/15 10:09 AM, Alexander wrote:
>> truss can help to see where boot-archive stumbles
>>
>> -- Alex
>>
>>
>> On 21 Sep 2015 at 20:02:44, Watson, Dan
>> (dan.watson at bcferries.com) wrote:
>>
>> I have had this issue. My (bad) solution was to comment out
>> bootadm from both boot-archive service scripts and run them
>> manually as needed. It seems to be an indicator of too much
>> latency. SVC only waits 20s by default and bootadm update can
>> take up to 100s with sub-par disks.
>>
>> I find when the disks are "good enough" the first run will time
>> out, but after you log in to maintenance mode and clear the
>> service is finishes instantly because it completed when SVC timed
>> it out waiting for it.
>>
>> Dan -----Original Message----- From: Richard Patterson
>> [mailto:richard at helpquick.co.uk] Sent: September 21, 2015 12:49
>> AM To: Discussion list for OpenIndiana Subject: Re:
>> [OpenIndiana-discuss] System will not boot, boot-archive fails
>>
> Thanks Nikola,
>
> On 21/09/2015 07:37, Nikola M wrote:
>>>> There is a bug in the GRUB that is shipped as a part of
>>>> illumos, that breaks with STAGE2 if menu.lst is too big (e.g.
>>>> you have many Boot environments , undetermined how much,
>>>> maybe over 25 BEs?).
>>>>
> I don't think I've encountered this issue, as I only have 4 BEs
> listed in grub.
>
>>>>> OpenIndiana Build oi_151a9 64-bit (illumos 52e13e00ba) 32GB
>>>>> Ram, Quad-core AMD CPU rpool is on a single 250GB SATA
>>>>> drive.
>>>> it is not healthy to be left with no room on disk, it kills
>>>> ZFS performance, etc. You can clear some space from rpool to
>>>> some external drive, for starters.
>>>>
> The rpool has plenty of space left, 56.1G in use, 173G free, so
> doesn't look like that's the problem.
>
> I also did a scrub on rpool, which shows no errors.
>
> As a test, I removed the other 8 drives (took the controller out
> completely), and the system boots fine... seems to be something to
> do with the large "backups" zpool, as the system will not boot with
> it attached.
>
> To make things worse, I can only work on the server at the
> console, which is in a remote office from where I work normally, so
> I'm unable to try things until I get to that office on an evening.
>
> Many thanks
>
> Richard
>>
>> _______________________________________________
>> 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
>> _______________________________________________
>> 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJWAR2zAAoJEAKlOyw2yHcoxg0P/ikF/MeBLAu9hcb+ntijQfvo
X5qGzz0Xj7sMSJik/9mynpeToyue+4wtZMY162e8w66XPnx0T75EfyNPVDVYDNlj
LmoTUxHwY5J9nIurMUed/ZNL+jID/00CCmy2PfNB66aNf9H+j5AL/qw+RQHqHI4C
/TwvF6/2ex39C+fPk5VVlX/J7cMAC5WP7vQVSQIBlApi/zkoBJQm6wt/1MKCMnW6
2EPkldOmzSoSFaf1OLzOOD/9PqVX1LVo8fICdli5ydQZYDIphhxgu88Oj5mEGnyp
3WCTp4TLNcYFx2919MLpB4mvGv6xiP2oa0Rn/ExxYWcjsr/xt87Q/DCFbMytGmAT
VOmF6s9LYukqll5sBK1HQ31vpnZt0eKV0quMYQSZbjHjMycDOIeiDeReEhZgSzAm
nG5O21JXhIkWcoWKjoEQpnMghqZf+OHjVFqSlRn/iZVe/hLazURzr4XmNQm1Ivcy
Sl84zyojYil8dZ1AeJhZsR9IYZtCwIZCKLkh9uViPH66iL4R7lt9nB6nz9DNYzIJ
X+JuT7inMxHdVtjifodXUWDGFCLA1TGEr5imNAal8PJoJJGKAO2g4dk94GP69nHY
u6yfjiUGyyNT0SgPYYocbwVXXfX3bDmcTJJWjPgfqsnDJ5gGMZy01oi0kZG77e51
/tG8N8wLY/F175e4FBnX
=TyYE
-----END PGP SIGNATURE-----
More information about the openindiana-discuss
mailing list