[OpenIndiana-discuss] System will not boot, boot-archive fails
Nikola M
minikola at gmail.com
Wed Sep 23 09:25:10 UTC 2015
If drives had beed set as JBOD (on disk format not related to disk
controller)
then drives themselves should work on any machine and controller and OS
using OpenZFS.
Of course, it is best not to have SAS/SATA expanders and to use SAS
controller for SAS and SATA for SATA.
I would Leave all disks in and try to import with some another install
of both Openindiana, other illumos distro or even FreBSD and Linux with
ZFSOnLinux.
You can install OI Hipster in VirtualBox and then do zfs send/receive
system and user datasets to the main system disk/rpool to newly made and
empied BE. That way you can also boot OI Hipster and see if importing
behaves differently with newest illumos.
I bet it's some hardware failure to aether controller, expanders and/or
disk(s).
On 09/23/15 11:12 AM, Richard Patterson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ok, I identified the possibly faulty drives, and took them out. (Doing
> a full test on them in another box)
>
> Trying to import the backups zpool without the 2 drives (raidz2 so
> should be ok):
>
> zpool import -f backups
>
> Hangs the server after about 10 mins. (I had top running, and it's
> stopped updating)
>
> Any ideas?
>
> Regards
>
> Richard
>
> On 22/09/2015 10:21, Richard Patterson wrote:
>> 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).
>>
>>
>> _______________________________________________ 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/
>
> iQIcBAEBAgAGBQJWAmziAAoJEAKlOyw2yHcoS2sP/RGX6S4P1HKEgzKnSqpRdGD3
> 5G3+v2n6u8obO2ZGR0aUsdGiJ/vGi2ny6btpKya5AI5U2doABV4ACUWNkoD0rNaj
> zE2zuO/qlKjk8Nv3ozzqhXtNGMUKGSkz+x1x92hgQKkIoviZLO0cUMTtcZYW6aIk
> P4vokucs6JFbCTOsZa0sjT3qpmSyw1yqc1y/j0mM2ac1c1pkQNMhFsUwKi4PnOML
> vmNawJCExTvHKNIFoqBXXEZiC7olNMUyG7uhTsK4CxPfCAHCrPBCTcOZZHAF8T8n
> BTqHh8WVaoUsVo9ZNYisjtKSW6lfEHtOYyjnYVRUw3XNT27LTYRzwblaP8PgYav+
> EmB+aQHLm33k1oIXctkm1SaO9bFXWghhhkMlp5dxocLlsSiH050rS0lc/dWrSGTX
> 9LgsR9tUEefl/DFI6UO30xzMtCkuPML76irnlPfcXEqYICjHLVCWiqGAkAcfFjFp
> UmYs0cop97HnSiWHZ5+m7cSLyjQGAOBCLx00IcoXbzaS/2g+g5tE9AxjKPxszY85
> Z+MCE9VcK/RQs9Krd8BD4MaOoUR/xAg/alGjmWWp5MfLwujJi/4RRRZjo22SgDoa
> +BmEg1w1cENoG6oBD5B8vhDFz5ZrMpEgQoza3jV+3OeYj93AzVQDn/p8Anof6RKv
> BHrpZJdtD2Gmr0rTtraf
> =15xt
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
More information about the openindiana-discuss
mailing list