A bit more data. I concluded after my initial, rather lengthy attempt at getting this to work that there was some hardware specific issue that resulted in not being able to set un_phy_blocksize=0x1000 & ashift=12. I'd be delighted if that were not the case, but happy to buy a "known to work" disk. So I'm looking for an HGST disk per previous post. Other suggestions welcome.
# cfgadm -v -c unconfigure usb9/3 Unconfigure the device: /devices/pci@0,0/pci10de,cb79@4,1:3 This operation will suspend activity on the USB device Continue (yes/no)? yes cfgadm: Hardware specific failure: Cannot issue devctl to ap_id: /devices/pci@0,0/pci10de,cb79@4,1:3 # cfgadm -v -c disconnect usb9/3 Disconnect the device: /devices/pci@0,0/pci10de,cb79@4,1:3 This operation will suspend activity on the USB device Continue (yes/no)? yes cfgadm: Hardware specific failure: Cannot issue devctl to ap_id: /devices/pci@0,0/pci10de,cb79@4,1:3 -------------------------------------------- On Wed, 3/26/14, Reginald Beardsley <[email protected]> wrote: Subject: Re: [OpenIndiana-discuss] Using large (3-4 TB) USB disks for backups To: "Discussion list for OpenIndiana" <[email protected]> Date: Wednesday, March 26, 2014, 8:43 AM Here's what happens w/ oi151a8. I was using a7 the last time. The physical size doesn't get set correctly w/ the result that ashift=9. # echo "::walk sd_state | ::grep '.!=0' | ::print struct sd_lun un_sd |::print struct scsi_device sd_inq | ::print struct scsi_inquiry inq_vid inq_pid" | mdb -k inq_vid = [ "Toshiba " ] inq_pid = [ "External USB 3.0" ] # echo ::sd_state | mdb -k | egrep '(^un|_blocksize)' un 3: ffffff0148254cc0 un_sys_blocksize = 0x200 un_tgt_blocksize = 0x1000 un_phy_blocksize = 0x200 un_f_tgt_blocksize_is_valid = 0x1 Add entry in sd.conf: sd-config-list = "*Toshiba*" ,"physical-block-size:4096"; # update_drv -vf sd Cannot unload module: sd Will be unloaded upon reboot. Forcing update of sd.conf. sd.conf updated in the kernel. # echo ::sd_state | mdb -k | egrep '(^un|_blocksize)' un 3: ffffff0148254cc0 un_sys_blocksize = 0x200 un_tgt_blocksize = 0x1000 un_phy_blocksize = 0x200 un_f_tgt_blocksize_is_valid = 0x1 Rebooted system # echo ::sd_state | mdb -k | egrep '(^un|_blocksize)' un 3: ffffff0140e28d00 un_sys_blocksize = 0x1000 un_tgt_blocksize = 0x1000 un_phy_blocksize = 0x200 un_f_tgt_blocksize_is_valid = 0x1 Note sys_blocksize got set, but not phys_blocksize. # zpool create tosh_pool c0t0d0p0 # zdb | egrep 'ashift| name' name: 'rpool' ashift: 9 name: 'tosh_pool' ashift: 9 # -------------------------------------------- On Tue, 3/25/14, Andrew Gabriel <[email protected]> wrote: Subject: Re: [OpenIndiana-discuss] Using large (3-4 TB) USB disks for backups To: [email protected] Date: Tuesday, March 25, 2014, 11:31 PM On 26/03/2014 03:07, Reginald Beardsley wrote: > Has anyone been able to ZFS format a 3-4 TB USB drive w/ OI so that it worked properly? I was defeated by a 3 TB Toshiba drive, but am hoping some other make might work w/o generating misaligned messages. It helps if you paste in the terminal window showing the exact commands you issued and their responses. -- Andrew _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
