Frank,

do you see anything interesting messages from nvme in /var/adm/messages
after the system hung?


Hans


On Fri, Jun 17, 2016 at 01:38:00AM +0200, Frank M. wrote:
> supplement:
> --------------------------------------------------
> --------------------------------------------------
> OmniOS:
> --------
> I imported the nvme-zpool and shutdown the system. After cold-boot the
> system hangs, ssh or console-login is not possible.
> After cold-boot with detached nvme from vm the system boots and has
> following errors:
> 
> --------------------------------------------------
> root@san-05:/root# fmdump -Vp
> TIME                           UUID                                 
> SUNW-MSG-ID
> Jun 16 2016 23:04:54.331544000 059581a5-b6fb-e4ea-ee75-e4653cfa8977 
> ZFS-8000-D3
> 
>   TIME                 CLASS                                 ENA
>   Jun 16 23:04:51.5047 ereport.fs.zfs.vdev.open_failed       
> 0x00514429e6700801
> 
> nvlist version: 0
>         version = 0x0
>         class = list.suspect
>         uuid = 059581a5-b6fb-e4ea-ee75-e4653cfa8977
>         code = ZFS-8000-D3
>         diag-time = 1466118294 132765
>         de = fmd:///module/zfs-diagnosis
>         fault-list-sz = 0x1
>         fault-list = (array of embedded nvlists)
>         (start fault-list[0])
>         nvlist version: 0
>                 version = 0x0
>                 class = fault.fs.zfs.device
>                 certainty = 0x64
>                 asru = zfs://pool=nvp1/vdev=bbed2c1c802d9802
>                 resource = zfs://pool=nvp1/vdev=bbed2c1c802d9802
>         (end fault-list[0])
> 
>         fault-status = 0x3
>         severity = Major
>         __ttl = 0x1
>         __tod = 0x57633096 0x13c2f5c0
> 
> TIME                           UUID                                 
> SUNW-MSG-ID
> Jun 16 2016 23:04:54.531124000 ec1bcc4d-02fd-4454-ce2d-a8f7505f7ad6 
> ZFS-8000-CS
> 
>   TIME                 CLASS                                 ENA
>   Jun 16 23:04:51.5047 ereport.fs.zfs.zpool                  
> 0x00514429e6700801
> 
> nvlist version: 0
>         version = 0x0
>         class = list.suspect
>         uuid = ec1bcc4d-02fd-4454-ce2d-a8f7505f7ad6
>         code = ZFS-8000-CS
>         diag-time = 1466118294 354680
>         de = fmd:///module/zfs-diagnosis
>         fault-list-sz = 0x1
>         fault-list = (array of embedded nvlists)
>         (start fault-list[0])
>         nvlist version: 0
>                 version = 0x0
>                 class = fault.fs.zfs.pool
>                 certainty = 0x64
>                 asru = zfs://pool=nvp1
>                 resource = zfs://pool=nvp1
>         (end fault-list[0])
> 
>         fault-status = 0x3
>         severity = Major
>         __ttl = 0x1
>         __tod = 0x57633096 0x1fa84f20
> --------------------------------------------------
> 
> That means, in all my other cold-boot-tests the nvme was attached to
> the vm but the zpool on this nvme wasnt attached(imported).
> 
> Now I exported the faulty (because non-existent) zpool and shutdown
> the system.
> After attaching the nvme to the vm the vm boots but format hangs as
> always. Soft-boot - all is okay again, format shows me all disks.
> After importing the zpool I can work best with as many soft-boots as I
> want... ...until next cold-boot.
> 
> Frank


-- 
%SYSTEM-F-ANARCHISM, The operating system has been overthrown


-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com

Reply via email to