On Jan 21, 2007, at 1:40 AM, Steve Watt wrote:
In [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
Václav Haisman wrote:
What does lsdev or whatever it was say? Does it show any devices
besides
the raw disks?
So I booted from CD and ran lsdev, and showed something like this
(from
memory)
In [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
Václav Haisman wrote:
What does lsdev or whatever it was say? Does it show any devices besides
the raw disks?
So I booted from CD and ran lsdev, and showed something like this (from
memory)
0: Drive A
2: Disk 0
1: FFS
You need to get into
Steve Watt wrote:
You need to get into your SCSI BIOS (don't know what the key
sequence is for 3ware, it's ^A for Adaptec)
Alt-F3
funnily enough...
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
On Sun, January 21, 2007 8:47 am, Matthew Seaman wrote:
Steve Watt wrote:
You need to get into your SCSI BIOS (don't know what the key
sequence is for 3ware, it's ^A for Adaptec)
Alt-F3
funnily enough...
It's ALT+3 for all our 3Ware Escalade cards (PATA/SATA).
Freddie Cash
[EMAIL
Suleiman Souhlal wrote:
Jo Rhett wrote:
So I've been searching for hours now, and it appears that short of
reading the C code, there's no documentation of the boot2 menu
prompt.
Sure, it says drive:driver(unit,slice,part)
But no combination of those three that I can find actually works.
Jo Rhett wrote:
I'd like to add to this that the handbook is riddled full of
undocumented terms, like BIOS Drive #. How do you determine this for a
SCSI drive?
Depends on your controller. If it doesn't register a drive with BIOS,
you don't get to access it like that.
Jo Rhett wrote:
So I've been searching for hours now, and it appears that short of
reading the C code, there's no documentation of the boot2 menu prompt.
Sure, it says drive:driver(unit,slice,part)
But no combination of those three that I can find actually works.
There's two LUNs:
On Thursday 11 January 2007 23:55, Jo Rhett wrote:
On Jan 11, 2007, at 8:50 PM, Jo Rhett wrote:
So I've been searching for hours now, and it appears that short of
reading the C code, there's no documentation of the boot2 menu prompt.
I'd like to add to this that the handbook is riddled
John Baldwin wrote:
A BIOS driver number is the number you pass to the BIOS to access a drive.
Typically drive 0x0 is a floppy drive and hard drives start at 0x80.
Usually the SCSI BIOS will list the BIOS driver number during the POST
messages and it will look like 80, 81, etc. There is no
Václav Haisman wrote:
What does lsdev or whatever it was say? Does it show any devices besides
the raw disks?
So I booted from CD and ran lsdev, and showed something like this (from
memory)
0: Drive A
2: Disk 0
1: FFS
--
Jo Rhett
senior geek
Silicon Valley Colocation
On Friday 12 January 2007 10:56, Jo Rhett wrote:
John Baldwin wrote:
A BIOS driver number is the number you pass to the BIOS to access a drive.
Typically drive 0x0 is a floppy drive and hard drives start at 0x80.
Usually the SCSI BIOS will list the BIOS driver number during the POST
Okay, let me make this really clear. My BIOS doesn't tell me which
drive is which, and the BIOS of the 3ware card doesn't tell me what
number the drive is going to be labeled either.
I need some command I can run from the freebsd CD to tell me what
freebsd observes.
Like I mentioned
On Friday 12 January 2007 12:37, Jo Rhett wrote:
Okay, let me make this really clear. My BIOS doesn't tell me which
drive is which, and the BIOS of the 3ware card doesn't tell me what
number the drive is going to be labeled either.
I need some command I can run from the freebsd CD to
On Jan 12, 2007, at 10:12 AM, John Baldwin wrote:
Like I mentioned before, lsdev only showed me a single drive.
Then the 3ware BIOS doesn't let the boot software see your second
drive,
so there's no way to load /boot/loader off that drive since boot2 and
the loader both rely on the BIOS to
On Friday 12 January 2007 16:12, Jo Rhett wrote:
On Jan 12, 2007, at 10:12 AM, John Baldwin wrote:
Like I mentioned before, lsdev only showed me a single drive.
Then the 3ware BIOS doesn't let the boot software see your second
drive,
so there's no way to load /boot/loader off that
So I've been searching for hours now, and it appears that short of
reading the C code, there's no documentation of the boot2 menu prompt.
Sure, it says drive:driver(unit,slice,part)
But no combination of those three that I can find actually works.
There's two LUNs:
drive 0: single 2TB
On Jan 11, 2007, at 8:50 PM, Jo Rhett wrote:
So I've been searching for hours now, and it appears that short of
reading the C code, there's no documentation of the boot2 menu prompt.
I'd like to add to this that the handbook is riddled full of
undocumented terms, like BIOS Drive #. How do
Jo Rhett wrote:
So I've been searching for hours now, and it appears that short of
reading the C code, there's no documentation of the boot2 menu prompt.
Sure, it says drive:driver(unit,slice,part)
But no combination of those three that I can find actually works.
There's two LUNs:
drive
18 matches
Mail list logo
