twe driver, 1+ terabyte array, fdisk and disklabel
So I'm having some problems with 5.1-RELEASE. I'm not sure if these have already been addressed but as I have found no mention of any of these problems on the mailing lists (web searchable anyway) or deja and google, I've subscribed myself to current and am looking for possible answers. :) I have a 3ware 7500-8. I also have 8 Western Digital Special Edition 250GB drives attached to said RAID card. I currently have one RAID-5 array configured for a total of 1.75T. There seem to be no real issues on the hardware side of this equation. I just grabbed the 5.1-RELEASE ISO and tried to install. No dice, although I have had mixed results. The disk geometry as reported (guessed actually, as it tells me the geometry reported by BIOS is obviously wrong and continues to remind me it's guessing every single time I move lines) in fdisk is 212808/255/63, for a grand total of 3418760520 sectors (again, as reported by fdisk). If I, at this point, say use entire disk it gives me roughly: --- offset size(st) endnameftype descsubtype flags 0 63 62 - 12unused 0 63 3418760457 3418760519 twed0s1 8 freebsd 165 -876206776 4536 3418765055 - 12unused 0 Obvious problems there. And also, why do there appear to be more sectors listed here than in the sectors reported at the top of the screen (3418765055 versus 3418760520)? And the negative offset. Riiight... :) So then I try to do dangerously dedicated mode. I eventually give up on the CLI and switch to wizard mode. I'm finally able to make it dedicated. So now I have: --- offset size(st) endnameftype descsubtype flags 0 3418765056 3418765055 twed0s1 8 freebsd 165 Yay. Now on to disklabel, right? Well, at this point, regardless of whether my fdisk looks like example 1 above or example 2, I get this in disklabel: --- Fatal Error: Partitions are larger than actual chunk?? - PRESS ANY KEY TO REBOOT Haha. There are only two ways I've found to make this work so far, and I'm not happy with either really. One is simple. Use RAID-10, and my disk array drops to 1T. Fast, but not what I'm looking for. The second is to use create slice in fdisk, and it puts the default number of 3.4 billion sectors in the field for the size of the slice I want to create. When I hit enter, it actually only ends up using 2 billion some odd sectors, and then I can create a second slice of the remaining drive. At that point, disklabel at least runs without dying right away, but then I have an approximately 1T slice followed by a 600 something gigabyte slice. Again, not what I'm looking for. Any advice? Are the disk tools just not 64 bit clean or something? Or is this a kernel, device driver or fs layer problem? -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a-- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- This sentence no verb. end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: twe driver, 1+ terabyte array, fdisk and disklabel
On Wed, Aug 13, 2003 at 11:10:27PM -0500, Mark Nipper wrote: On 13 Aug 2003, Brooks Davis wrote: My workaround was to split the array into a 2 disk RAID1 and a 6 disk RAID5. Sysinstall will install on the small mirror and then you can use the RAID5 array raw. On some other systems, I'm not going to be booting from the arrays so I'll use the entire array as a large RAID5 volume without any partions. Duh. I should have thought of something along these lines. I just left my 1.75GB RAID-5 array in place and only took a few gigabytes out of it for slice 1. Then I installed everything into that for the base system. Worked like a charm. Next I went ahead post installation and did cvsup and used fdisk and disklabel (outside sysinstall of course) to create the current, ridiculous slice and partition. Yay. :) --- /dev/twed0s2a 1.5T 2.0K 1.5T 0%/data Ahh, I though about that but got frustated with my other ideas not working and fell back to using two arrays. I may give that a shot since the system isn't in production yet. -- Brooks pgp0.pgp Description: PGP signature
Re: twe driver, 1+ terabyte array, fdisk and disklabel
On Wed, Aug 13, 2003 at 04:55:20PM -0500, Mark Nipper wrote: Haha. There are only two ways I've found to make this work so far, and I'm not happy with either really. One is simple. Use RAID-10, and my disk array drops to 1T. Fast, but not what I'm looking for. The second is to use create slice in fdisk, and it puts the default number of 3.4 billion sectors in the field for the size of the slice I want to create. When I hit enter, it actually only ends up using 2 billion some odd sectors, and then I can create a second slice of the remaining drive. At that point, disklabel at least runs without dying right away, but then I have an approximately 1T slice followed by a 600 something gigabyte slice. Again, not what I'm looking for. Any advice? Are the disk tools just not 64 bit clean or something? Or is this a kernel, device driver or fs layer problem? I ran into this recently myself. The main problem is with sysinstall, but there are other problems after that. Sysinstall should be able to handle up to 2TB disks since that's what MBR partition tables support according to Microsoft, but obviously it chokes earlier. Soon we're going to have to find a way to move to GPT parititions because 3.3TB arrays will be feasiable by Q1 2004 (probably sooner) according to the 3Ware rep I spoke to recently. My workaround was to split the array into a 2 disk RAID1 and a 6 disk RAID5. Sysinstall will install on the small mirror and then you can use the RAID5 array raw. On some other systems, I'm not going to be booting from the arrays so I'll use the entire array as a large RAID5 volume without any partions. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp0.pgp Description: PGP signature
Re: twe driver, 1+ terabyte array, fdisk and disklabel
On 13 Aug 2003, Brooks Davis wrote: My workaround was to split the array into a 2 disk RAID1 and a 6 disk RAID5. Sysinstall will install on the small mirror and then you can use the RAID5 array raw. On some other systems, I'm not going to be booting from the arrays so I'll use the entire array as a large RAID5 volume without any partions. Duh. I should have thought of something along these lines. I just left my 1.75GB RAID-5 array in place and only took a few gigabytes out of it for slice 1. Then I installed everything into that for the base system. Worked like a charm. Next I went ahead post installation and did cvsup and used fdisk and disklabel (outside sysinstall of course) to create the current, ridiculous slice and partition. Yay. :) --- /dev/twed0s2a 1.5T 2.0K 1.5T 0%/data Which reminds me, any chance of putting in more useful information to fdisk and disklabel from the command line? I had to fire up sysinstall just to figure out all the sector boundaries and sizes. What a pain! :) Anyway, thanks for the feedback. My brain was elsewhere. -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a-- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- Do you believe in destiny, that even the powers of time can be ordered to a single purpose? The luckiest man who walks this earth is the one who finds true love. -- Dracula, Bram Stoker's Dracula, 1992 end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
