2012-03-13 16:52, Hung-Sheng Tsao (LaoTsao) Ph.D wrote:
are the disk/sas controller the same on both server?

Seemingly no. I don't see the output of "format" on Server2,
but for Server1 I see that the 3TB disks are used as IDE
devices (probably with motherboard SATA-IDE emulation?)
while on Server2 addressing goes like SAS with WWN names.

It may be possible that on one controller disks are used
"natively" while on another they are attached as a JBOD
or a set of RAID0 disks (so the controller's logic or its
expected layout intervenes), as recently discussed on-list?

On Mar 13, 2012, at 6:10, P-O Yliniemi<p...@bsd-guide.net>  wrote:


I'm currently replacing a temporary storage server (server1) with the one that 
should be the final one (server2). To keep the data storage from the old one 
I'm attempting to import it on the new server. Both servers are running 
OpenIndiana server build 151a.

Server 1 (old)
The zpool consists of three disks in a raidz1 configuration:
# zpool status
            c4d0    ONLINE       0     0     0
            c4d1    ONLINE       0     0     0
            c5d0    ONLINE       0     0     0

errors: No known data errors

Output of format command gives:
# format
       0. c2t1d0<LSILOGIC-LogicalVolume-3000 cyl 60785 alt 2 hd 255 sec 126>
       1. c4d0<ST3000DM-         W1F07HW-0001-2.73TB>
       2. c4d1<ST3000DM-         W1F05H2-0001-2.73TB>
       3. c5d0<ST3000DM-         W1F032R-0001-2.73TB>

Server 2 (new)
I have attached the disks on the new server in the same order (which shouldn't 
matter as ZFS should locate the disks anyway)
zpool import gives:

root@backup:~# zpool import
   pool: storage
     id: 17210091810759984780
  state: UNAVAIL
action: The pool cannot be imported due to damaged devices or data.

        storage                    UNAVAIL  insufficient replicas
          raidz1-0                 UNAVAIL  corrupted data
            c7t5000C50044E0F316d0  ONLINE
            c7t5000C50044A30193d0  ONLINE
            c7t5000C50044760F6Ed0  ONLINE

zfs-discuss mailing list

Reply via email to