> On Oct 7, 2015, at 8:27 AM, Alessio Ciregia <[email protected]> wrote: > > I have physically replaced a broken disk in a SmartOS server. > Unfortunately the zpool replace command says: > > zpool replace zones c0t3d0 > cannot replace c0t3d0 with c0t3d0: devices have different sector alignment > > I have found this document: > <http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks>
In your case, an existing 512 byte sector drive and pool vdev are set in stone. > > The other disks have > un_phy_blocksize = 0x200 > that is supposed to be 512b block size, right? > Instead, the new disk has > un_phy_blocksize = 0x1000 > that is 4k block size, isn't it? > > In such document a possible solution is to edit the /kernel/drv/sd.conf > file, and reload the sd driver. But such operation needs a reboot. > At reboot time, changes to sd.conf file will be lost. > > How can I solve this issue? It is not a good idea to do this, hence the restriction. > Anyone with previous experiences? Tears await those who force 4K sector drives to do 512 byte sector work. Your best solution is to replace with a 512n drive. Yes, these are still being manufactured. -- richard ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
