Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
On Thu, Jun 23, 2011 at 1:20 PM, Richard Elling richard.ell...@gmail.com wrote: 2TB limit for 32-bit Solaris. If you hit this, then you'll find a lot of complaints at boot. By default, an Ultra-24 should boot 64-bit. Dunno about the HBA, though... I think the limit is 1TB for 32-bit. I've tried to use 2TB drives on an Atom N270-based board and they were not recognized, but they worked fine under FreeBSD. -B -- Brandon High : bh...@freaks.com ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
I cannot run format -e to change it since it will crash my sys or the server I am trying to attach the disk to. Did you try to do as Jim Dunham said? zpool create test_pool c5t0d0p0 zpool destroy test_pool format -e c5t0d0p0 partition print controlD -- Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 97542685 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
It wouldn't let me # zpool create test_pool c5t0d0p0 cannot create 'test_pool': invalid argument for this pool operation Thanks, Kitty On 06/23/11 03:00, Roy Sigurd Karlsbakk wrote: I cannot run format -e to change it since it will crash my sys or the server I am trying to attach the disk to. Did you try to do as Jim Dunham said? zpool create test_pool c5t0d0p0 zpool destroy test_pool format -e c5t0d0p0 partition print controlD ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
kitty@oracle.com said: It wouldn't let me # zpool create test_pool c5t0d0p0 cannot create 'test_pool': invalid argument for this pool operation Try without the p0, i.e. just: # zpool create test_pool c5t0d0 Regards, Marion ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
Hi Kitty, Try this: # zpool create test c5t0d0 Thanks, Cindy On 06/23/11 12:34, Kitty Tam wrote: It wouldn't let me # zpool create test_pool c5t0d0p0 cannot create 'test_pool': invalid argument for this pool operation Thanks, Kitty On 06/23/11 03:00, Roy Sigurd Karlsbakk wrote: I cannot run format -e to change it since it will crash my sys or the server I am trying to attach the disk to. Did you try to do as Jim Dunham said? zpool create test_pool c5t0d0p0 zpool destroy test_pool format -e c5t0d0p0 partition print controlD ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
Kitty, It wouldn't let me # zpool create test_pool c5t0d0p0 cannot create 'test_pool': invalid argument for this pool operation I overlooked the Ultra24 part of your original posting. SPARC platforms don't support disks with partitions. zpool create test_pool c5t0d0 zpool destroy test_pool format -e c5t0d0 partition print controlD Thanks, Kitty On 06/23/11 03:00, Roy Sigurd Karlsbakk wrote: I cannot run format -e to change it since it will crash my sys or the server I am trying to attach the disk to. Did you try to do as Jim Dunham said? zpool create test_pool c5t0d0p0 zpool destroy test_pool format -e c5t0d0p0 partition print controlD ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
I wonder if there is a limit on the size of disk to mount for Solaris. I was able to run format on a WD 1TB disk several months ago. The diff is that it's a 2.5TB one this time. It might also be a driver issue. Need to ck on that. honeybun# zpool create test_pool c5t0d0 cannot open '/dev/dsk/c5t0d0s0': I/O error Thanks, Kitty On 06/23/11 11:54, Jim Dunham wrote: Kitty, It wouldn't let me # zpool create test_pool c5t0d0p0 cannot create 'test_pool': invalid argument for this pool operation I overlooked the Ultra24 part of your original posting. SPARC platforms don't support disks with partitions. zpool create test_pool c5t0d0 zpool destroy test_pool format -e c5t0d0 partition print controlD Thanks, Kitty On 06/23/11 03:00, Roy Sigurd Karlsbakk wrote: I cannot run format -e to change it since it will crash my sys or the server I am trying to attach the disk to. Did you try to do as Jim Dunham said? zpool create test_pool c5t0d0p0 zpool destroy test_pool format -e c5t0d0p0 partition print controlD ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
On Jun 23, 2011, at 1:13 PM, Kitty Tam wrote: I wonder if there is a limit on the size of disk to mount for Solaris. I was able to run format on a WD 1TB disk several months ago. The diff is that it's a 2.5TB one this time. 2TB limit for 32-bit Solaris. If you hit this, then you'll find a lot of complaints at boot. By default, an Ultra-24 should boot 64-bit. Dunno about the HBA, though... -- richard ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[zfs-discuss] Cannot format 2.5TB ext disk (EFI)
I am trying to mount a WD 2.5TB external drive (was IFS:NTFS) to my OSS box. After connecting it to my Ultra24, I ran pfexec fdisk /dev/rdsk/c5t0d0p0 and changed the Type to EFI. Then, format -e or format showed the disk was config with 291.10GB only. Selecting a disk would crash my OSS box. The same if I connected it to a s10x box. Anything I am missing in order to format the disk with EFI label and creating a zpool with it? Here is some screen shots == --- If it were attached to the OSS box 2. Logical Node: /dev/rdsk/c5t0d0p0 -- WD2.5TB ext disk Physical Node: /p Access permissions: Medium is not write protected. # format -e Searching for disks...done c5t0d0: configured with capacity of 291.10GB AVAILABLE DISK SELECTIONS: 0. c3t0d0 DEFAULT cyl 36469 alt 2 hd 255 sec 63 /pci@0,0/pci8086,2940@1c/pci1000,3091@0/sd@0,0 1. c3t1d0 DEFAULT cyl 36469 alt 2 hd 255 sec 63 /pci@0,0/pci8086,2940@1c/pci1000,3091@0/sd@1,0 2. c3t2d0 SEAGATE-ST330055SSUN300G-0791-279.40GB /pci@0,0/pci8086,2940@1c/pci1000,3091@0/sd@2,0 3. c3t3d0 SEAGATE-ST330055SSUN300G-0791-279.40GB /pci@0,0/pci8086,2940@1c/pci1000,3091@0/sd@3,0 4. c5t0d0 WD-Ext HDD 1021-2021-291.10GB /pci@0,0/pci108e,5351@1d,7/storage@5/disk@0,0 Specify disk (enter its number): pfexec fdisk /dev/rdsk/c5t0d0p0 Total disk size is 60800 cylinders Cylinder size is 80325 (512 byte) blocks Cylinders Partition Status Type Start End Length % = == === = === == === 1 EFI 0 7600 7601 14 --- if it were attached to a s10x box, it would crash after running format or format -e and select the disk. # Jun 20 15:35:09 swsdlcmir1 su: 'su root' succeeded for kitty on /dev/pts/3 panic[cpu0]/thread=fe8c5c60: BAD TRAP: type=e (#pf Page fault) rp=fe8c5a10 addr=a212a000 sched: #pf Page fault Bad kernel fault at addr=0xa212a000 pid=0, pc=0xfb8367ca, sp=0xfe8c5b08, eflags=0x10216 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f0xmme,fxsr,pge,mce,pae,pse cr2: a212a000 cr3: 128ec000 cr8: c rdi: a212a000 rsi: fe84dd4327d0 rdx: 4000 rcx: 506 r8: fe84def9a258 r9: 9b3f133a rax: 0 rbx: 4000 rbp: fe8c5b50 r10: 800f5000 r11: 34 r12: fe84d2318c00 r13: 0 r14: a0f2fe40 r15: 9b3f1300 fsb: 8000 gsb: fbc29cc0 ds: 43 es: 43 fs: 0 gs: 1c3 trp: e err: 2 rip: fb8367ca cs: 28 rfl: 10216 rsp: fe8c5b08 ss: 30 fe8c5920 unix:real_mode_end+7f81 () fe8c5a00 unix:trap+5e6 () fe8c5a10 unix:_cmntrap+140 () fe8c5b50 unix:bcopy_altentry+55a () fe8c5b60 ehci:ehci_handle_bulk_qtd+3f () fe8c5b80 ehci:ehci_handle_normal_qtd+2e () fe8c5bc0 ehci:ehci_traverse_active_qtd_list+5f () fe8c5bf0 ehci:ehci_intr+e4 () fe8c5c40 unix:av_dispatch_autovect+78 () fe8c5c50 unix:intr_thread+5f () panic: entering debugger (continue to save dump) Welcome to kmdb kmdb: unable to determine terminal type: assuming `vt100' Loaded modules: [ crypto cpc uppc neti ptm ufs unix cpu_ms.AuthenticAMD.15 zfs krtld s1394 uhci hook lofs genunix ip logindmux usba specfs pcplusmp md nfs random cpu.generic sctp arp ] [0] Thanks, Kitty -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
Kitty, I am trying to mount a WD 2.5TB external drive (was IFS:NTFS) to my OSS box. After connecting it to my Ultra24, I ran pfexec fdisk /dev/rdsk/c5t0d0p0 and changed the Type to EFI. Then, format -e or format showed the disk was config with 291.10GB only. The following message about configured with capacity of is very suspect, in that Solaris is not seeing either an EFI or VTOC disk label # format -e Searching for disks...done c5t0d0: configured with capacity of 291.10GB . . What are the results of the following operations? zpool create test_pool c5t0d0p0 zpool destroy test_pool format -e c5t0d0p0 partition print controlD Jim Selecting a disk would crash my OSS box. The same if I connected it to a s10x box. Anything I am missing in order to format the disk with EFI label and creating a zpool with it? Here is some screen shots == --- If it were attached to the OSS box 2. Logical Node: /dev/rdsk/c5t0d0p0 -- WD2.5TB ext disk Physical Node: /p Access permissions: Medium is not write protected. # format -e Searching for disks...done c5t0d0: configured with capacity of 291.10GB AVAILABLE DISK SELECTIONS: 0. c3t0d0 DEFAULT cyl 36469 alt 2 hd 255 sec 63 /pci@0,0/pci8086,2940@1c/pci1000,3091@0/sd@0,0 1. c3t1d0 DEFAULT cyl 36469 alt 2 hd 255 sec 63 /pci@0,0/pci8086,2940@1c/pci1000,3091@0/sd@1,0 2. c3t2d0 SEAGATE-ST330055SSUN300G-0791-279.40GB /pci@0,0/pci8086,2940@1c/pci1000,3091@0/sd@2,0 3. c3t3d0 SEAGATE-ST330055SSUN300G-0791-279.40GB /pci@0,0/pci8086,2940@1c/pci1000,3091@0/sd@3,0 4. c5t0d0 WD-Ext HDD 1021-2021-291.10GB /pci@0,0/pci108e,5351@1d,7/storage@5/disk@0,0 Specify disk (enter its number): pfexec fdisk /dev/rdsk/c5t0d0p0 Total disk size is 60800 cylinders Cylinder size is 80325 (512 byte) blocks Cylinders Partition Status Type Start End Length % = == === = === == === 1 EFI 0 7600 7601 14 --- if it were attached to a s10x box, it would crash after running format or format -e and select the disk. # Jun 20 15:35:09 swsdlcmir1 su: 'su root' succeeded for kitty on /dev/pts/3 panic[cpu0]/thread=fe8c5c60: BAD TRAP: type=e (#pf Page fault) rp=fe8c5a10 addr=a212a000 sched: #pf Page fault Bad kernel fault at addr=0xa212a000 pid=0, pc=0xfb8367ca, sp=0xfe8c5b08, eflags=0x10216 cr0: 8005003bpg,wp,ne,et,ts,mp,pe cr4: 6f0xmme,fxsr,pge,mce,pae,pse cr2: a212a000 cr3: 128ec000 cr8: c rdi: a212a000 rsi: fe84dd4327d0 rdx: 4000 rcx: 506 r8: fe84def9a258 r9: 9b3f133a rax: 0 rbx: 4000 rbp: fe8c5b50 r10: 800f5000 r11: 34 r12: fe84d2318c00 r13: 0 r14: a0f2fe40 r15: 9b3f1300 fsb: 8000 gsb: fbc29cc0 ds: 43 es: 43 fs: 0 gs: 1c3 trp: e err: 2 rip: fb8367ca cs: 28 rfl: 10216 rsp: fe8c5b08 ss: 30 fe8c5920 unix:real_mode_end+7f81 () fe8c5a00 unix:trap+5e6 () fe8c5a10 unix:_cmntrap+140 () fe8c5b50 unix:bcopy_altentry+55a () fe8c5b60 ehci:ehci_handle_bulk_qtd+3f () fe8c5b80 ehci:ehci_handle_normal_qtd+2e () fe8c5bc0 ehci:ehci_traverse_active_qtd_list+5f () fe8c5bf0 ehci:ehci_intr+e4 () fe8c5c40 unix:av_dispatch_autovect+78 () fe8c5c50 unix:intr_thread+5f () panic: entering debugger (continue to save dump) Welcome to kmdb kmdb: unable to determine terminal type: assuming `vt100' Loaded modules: [ crypto cpc uppc neti ptm ufs unix cpu_ms.AuthenticAMD.15 zfs krtld s1394 uhci hook lofs genunix ip logindmux usba specfs pcplusmp md nfs random cpu.generic sctp arp ] [0] Thanks, Kitty -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
4. c5t0d0WD-Ext HDD 1021-2021-291.10GB /pci@0,0/pci108e,5351@1d,7/storage@5/disk@0,0 Specify disk (enter its number): pfexec fdisk /dev/rdsk/c5t0d0p0 Total disk size is 60800 cylinders Cylinder size is 80325 (512 byte) blocks Cylinders Partition Status Type Start End Length % = == === = === == === 1 EFI 0 7600 7601 14 Your EFI partition only has 7601 cylinders. That is why format(1M) can only see 291GB. 7601 * 80325 (Cylinder size) * 512 = 291GB Larry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
I cannot run format -e to change it since it will crash my sys or the server I am trying to attach the disk to. It is a 2.5TB drive for sure. On 06/22/11 13:12, Larry Liu wrote: 4. c5t0d0WD-Ext HDD 1021-2021-291.10GB /pci@0,0/pci108e,5351@1d,7/storage@5/disk@0,0 Specify disk (enter its number): pfexec fdisk /dev/rdsk/c5t0d0p0 Total disk size is 60800 cylinders Cylinder size is 80325 (512 byte) blocks Cylinders Partition Status Type Start End Length % = == === = === == === 1 EFI 0 7600 7601 14 Your EFI partition only has 7601 cylinders. That is why format(1M) can only see 291GB. 7601 * 80325 (Cylinder size) * 512 = 291GB Larry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
You can try #fdisk /dev/rdsk/c5d0t0p0 to delete all the partitions and exit. You don't have to create EFI partition in fdisk(1M) because it only create the PMBR but not the EFI label. Then try format -e again. The panic sounds like a bug in USB driver to me. Larry 于 2011/6/22 13:48, Kitty Tam 写道: I cannot run format -e to change it since it will crash my sys or the server I am trying to attach the disk to. It is a 2.5TB drive for sure. On 06/22/11 13:12, Larry Liu wrote: 4. c5t0d0WD-Ext HDD 1021-2021-291.10GB /pci@0,0/pci108e,5351@1d,7/storage@5/disk@0,0 Specify disk (enter its number): pfexec fdisk /dev/rdsk/c5t0d0p0 Total disk size is 60800 cylinders Cylinder size is 80325 (512 byte) blocks Cylinders Partition Status Type Start End Length % = == === = === == === 1 EFI 0 7600 7601 14 Your EFI partition only has 7601 cylinders. That is why format(1M) can only see 291GB. 7601 * 80325 (Cylinder size) * 512 = 291GB Larry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Cannot format 2.5TB ext disk (EFI)
On Wed, Jun 22, 2011 at 02:01:12PM -0700, Larry Liu wrote: You can try #fdisk /dev/rdsk/c5d0t0p0 Or just dd /dev/zero over the raw device, eject and start from clean. -- Dan. pgpqmaR5Jw6Q0.pgp Description: PGP signature ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
