13 messages in org.freebsd.freebsd-scsi1TB issue| From | Sent On | Attachments |
|---|---|---|
| Tu...@Beach House | Jun 1, 2004 4:04 pm | |
| Kenneth D. Merry | Jun 1, 2004 4:40 pm | |
| Tu...@Beach House | Jun 1, 2004 4:53 pm | |
| Kenneth D. Merry | Jun 1, 2004 5:43 pm | |
| Tu...@Beach House | Jun 1, 2004 5:52 pm | |
| Kenneth D. Merry | Jun 1, 2004 5:56 pm | |
| Brooks Davis | Jun 1, 2004 6:03 pm | |
| Tu...@Beach House | Jun 1, 2004 6:12 pm | |
| Paul Saab | Jun 1, 2004 11:36 pm | |
| David Malone | Jun 2, 2004 2:49 am | |
| Bruce Evans | Jun 2, 2004 3:51 am | |
| Kenneth D. Merry | Jun 2, 2004 6:11 am | |
| Dan Strick | Jun 2, 2004 6:35 am |
| Subject: | 1TB issue | |
|---|---|---|
| From: | Kenneth D. Merry (ke...@kdm.org) | |
| Date: | Jun 1, 2004 4:40:19 pm | |
| List: | org.freebsd.freebsd-scsi | |
On Tue, Jun 01, 2004 at 19:04:51 -0400, Tuc at Beach House wrote:
Hi,
Having a SCSI Geometry issue on a 5.2.1-RELEASE-p4 system. It has a Symbios SDMS PCI SCSI, 53C1010-66 adapter that shows up as :
sym0: <1010-66> port 0xa000-0xa0ff mem 0xf6000000-0xf6001fff,0xf6800000-0xf68003 ff irq 25 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS.
And to it I'm connecting an EasyRaid II RAID box. There is LITTLE I can configure on it, basically termination, SCSI ID, and Raid 0/1/0+1/3/5 and thats pretty much it.
When the system boots, the splash screen claims the geometry is 1024/255/63 at 40M sync, and 16 wide. In the controller I've used "Alternate CHS Mapping" and "SCSI Plug and Play Mapping" without any differences.
When FreeBSD boots, it sees :
(noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. da0 at sym1 bus 0 target 3 lun 0 da0: <easyRAID II > Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 1060184MB (2171256832 512 byte sectors: 255H 63S/T 135154C)
When I try to /stand/sysinstall it, fdisk pitches a serious fit about it.
What can I do to get this configured properly? It seems that if I bring it down to RAID-1+0, it configures up fine (Not sure what the geometry shows as, sorry).
See another recent message on this list from Brooks Davis. It sounds like sysinstall has issues with large arrays in -current, but fdisk works okay.
Try doing your installation on a smaller fdisk partition within sysinstall, and then once you're installed, use the command line fdisk to create another slice and use up the rest of the array.
Ken
-- Kenneth Merry ke...@kdm.org