RE: No Device Node assigned for HD?

2009-08-23 Thread Daniel Eriksson

> You have two options:
> 1. Use the RR2310 BIOS screen (or hptraidconf from inside FreeBSD) to
> initialize the drive and create a single drive JBOD array with it.
> 2. Connect the drive to a header on your motherboard and create a
> partition table on it, then reconnect it to your RR2310 card.

I would suggest doing #2 above if you don't plan on using the drive as
part of a RR2310-controlled array. If you add a partition table and let
your RR2310 card treat it as "Legacy" then the drive can be moved around
freely between motherboard connectors and RR2310 connectors. If you do
#1 then you need a RocketRAID card to access the data on the drive.

/Daniel Eriksson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


RE: No Device Node assigned for HD?

2009-08-22 Thread Daniel Eriksson
Rob wrote:

> The only difference I've found is that in the RocketRAID BIOS, the 3 
> 500GB drives are recognized with a Legacy Status, whereas the 1TB is 
> recognized as New Status.  Not sure what that means or how to 
> change it. 

Your "problem" is that the old drives you have hooked up to the
RocketRAID card all have a partition table. When the RR BIOS sees that
partition table it assumes it is a "Legacy" drive and exposes it to the
OS as a single drive JBOD array. Your brand new 1 TB drive has nothing
on it, and your RocketRAID card is waiting for you to initialize it and
create an array with it before exposing it to the OS.

You have two options:
1. Use the RR2310 BIOS screen (or hptraidconf from inside FreeBSD) to
initialize the drive and create a single drive JBOD array with it.
2. Connect the drive to a header on your motherboard and create a
partition table on it, then reconnect it to your RR2310 card.

Partition table example:
# gpart create -t GPT adXX
# gpart add -b YY -s ZZ -t freebsd-ufs adXX

/Daniel Eriksson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: No Device Node assigned for HD?

2009-08-21 Thread Rob
I should clarify my statement a bit.  FreeBSD notices the channel 
starting up when the disk is inserted, but it doesn't recognize that 
there is a disk there.  I usually see something like:


da2 at hptrr0 bus 0 target 2 lun 0
da2:  Fixed Direct Access SCSI-0 device

once I insert a disk, but I see nothing but the channel start up when I 
insert this new disk.  I've had a 500GB drive in this channel previously 
and it was identified correctly, so I know the channel on the card is ok.


I've also updated to the latest firmware on the card and as expected, no 
change.  So I guess the question is, why isn't FreeNSD recognizing the disk?


Rob

Rob wrote:
I've a 10 disk server that I am using as a file server.  I split the 
disks up unto 3 partitions, with a being part of a gmirror for /, b 
being part of a gmirror for swap, and d being part of the zfs pool. I've 
got 6 SATA headers on my MB, and 4 from a HighPoint RocketRAID 2310 
controller which I'm just using as an SATA controller (no RAID 
functionality).


I recently added an Hitachi 1TB drive to the RocketRAID controller, but 
I'm not seeing FreeBSD assign it a device node.  FreeBSD recognizes the 
drive insertion, but doesn't give it a device node.  All the drives are 
SATA hot-swap, so I connected the drive to a header off the MB and 
FreeBSD happily gave it a device node.  Additionally, I already have a 
few of these drives in the array, but they're all connected to headers 
on the MB.  This is the first attempt at adding one to the RocketRAID 
controller.  The controller currently has 3 other disks in it that are 
500GB, and FreeBSD has had no problems with them.  The RocketRAID 
controller's BIOS recognizes the disk as well, so it doesn't seem the 
card is incapable of handling disks that large.  I've even tried 
rebooting the system after the drive has been connected, but no luck.


Here's the respective info from the boot sequence as it pertains to the 
RocketRAID and the drives attached to it:


hptrr: start channel [0,0]
hptrr: start channel [0,1]
hptrr: start channel [0,2]
hptrr: start channel [0,3]
hptrr: [0 0] Start channel soft reset.
hptrr: [0 1] Start channel soft reset.
hptrr: [0 2] Start channel soft reset.
hptrr: [0 3] Start channel soft reset.
hptrr: channel [0,0] started successfully
hptrr: channel [0,1] started successfully
hptrr: channel [0,2] started successfully
hptrr: channel [0,3] started successfully
hptrr0: [GIANT-LOCKED]
hptrr0: [ITHREAD]
...
da0 at hptrr0 bus 0 target 0 lun 0
da0:  Fixed Direct Access SCSI-0 device
da1 at hptrr0 bus 0 target 1 lun 0
da1:  Fixed Direct Access SCSI-0 device
da2 at hptrr0 bus 0 target 2 lun 0
da2:  Fixed Direct Access SCSI-0 device
...

The only difference I've found is that in the RocketRAID BIOS, the 3 
500GB drives are recognized with a Legacy Status, whereas the 1TB is 
recognized as New Status.  Not sure what that means or how to change it. 
 The sizes are reported correctly in the RocketRAID BIOS.  I believe 
there is a BIOS update available for the card, but I wouldn't think it 
would be necessary since the card's BIOS seems to recognize the card 
just fine.


Any suggestions/help?

Rob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"freebsd-questions-unsubscr...@freebsd.org"




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


No Device Node assigned for HD?

2009-08-20 Thread Rob
I've a 10 disk server that I am using as a file server.  I split the 
disks up unto 3 partitions, with a being part of a gmirror for /, b 
being part of a gmirror for swap, and d being part of the zfs pool. 
I've got 6 SATA headers on my MB, and 4 from a HighPoint RocketRAID 2310 
controller which I'm just using as an SATA controller (no RAID 
functionality).


I recently added an Hitachi 1TB drive to the RocketRAID controller, but 
I'm not seeing FreeBSD assign it a device node.  FreeBSD recognizes the 
drive insertion, but doesn't give it a device node.  All the drives are 
SATA hot-swap, so I connected the drive to a header off the MB and 
FreeBSD happily gave it a device node.  Additionally, I already have a 
few of these drives in the array, but they're all connected to headers 
on the MB.  This is the first attempt at adding one to the RocketRAID 
controller.  The controller currently has 3 other disks in it that are 
500GB, and FreeBSD has had no problems with them.  The RocketRAID 
controller's BIOS recognizes the disk as well, so it doesn't seem the 
card is incapable of handling disks that large.  I've even tried 
rebooting the system after the drive has been connected, but no luck.


Here's the respective info from the boot sequence as it pertains to the 
RocketRAID and the drives attached to it:


hptrr: start channel [0,0]
hptrr: start channel [0,1]
hptrr: start channel [0,2]
hptrr: start channel [0,3]
hptrr: [0 0] Start channel soft reset.
hptrr: [0 1] Start channel soft reset.
hptrr: [0 2] Start channel soft reset.
hptrr: [0 3] Start channel soft reset.
hptrr: channel [0,0] started successfully
hptrr: channel [0,1] started successfully
hptrr: channel [0,2] started successfully
hptrr: channel [0,3] started successfully
hptrr0: [GIANT-LOCKED]
hptrr0: [ITHREAD]
...
da0 at hptrr0 bus 0 target 0 lun 0
da0:  Fixed Direct Access SCSI-0 device
da1 at hptrr0 bus 0 target 1 lun 0
da1:  Fixed Direct Access SCSI-0 device
da2 at hptrr0 bus 0 target 2 lun 0
da2:  Fixed Direct Access SCSI-0 device
...

The only difference I've found is that in the RocketRAID BIOS, the 3 
500GB drives are recognized with a Legacy Status, whereas the 1TB is 
recognized as New Status.  Not sure what that means or how to change it. 
 The sizes are reported correctly in the RocketRAID BIOS.  I believe 
there is a BIOS update available for the card, but I wouldn't think it 
would be necessary since the card's BIOS seems to recognize the card 
just fine.


Any suggestions/help?

Rob
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"