Bought a LSI SAS 9207-8i SGL

[lindsay]

Is there anything to do after adding this controllercard?

The plan is to in the near future to buy another

[apollo567]

Well does it work ?
Original Firmware or IT-mode Firmware ?

[lindsay]

Have not got it yet, but it says FreeBSD is among the systems supported.

[apollo567]

Well,
adding
mfip_load="YES" to System|Advanced|loader.conf

might make sense.

Regards
apollo

[b0ssman]

there is an it mode firmware.

so definitely flash that.

[apollo567]

there is an it mode firmware.

so definitely flash that.

Look at R1003

[b0ssman]

the mfi driver is used for the raid version.

that is not the driver for the it mode.

[apollo567]

the mfi driver is used for the raid version.
that is not the driver for the it mode.

yep and starting with 1003 there will be a better weggui support for this raid version.
It works for N4F with the Raid Bios in Jbod Konfiguration already now without flashing the Controller

[b0ssman]

can you get smart values that way?

[apollo567]

can you get smart values that way?

yes, starting R1003

[ChriZathens]

Is this info valid for all LSI controllers?
Mine is an LSI 3081E-R, but it is flashed in IT mode.. and I get SMART values normally.
The only thing that does not work is spinning down the drives. Does this work for you in r1003?

[b0ssman]

to spindown the drives on a sas controller you need the freebsd package spindown and start it manually.

see
viewtopic.php?f=56&t=5872#p36678

[ChriZathens]

Yeap, have seen spindown package..
Just hoped that with new revision it could happen from default

[ChriZathens]

OK, quick question - I thought I should give spindown a try
I run the following command

Code: Select all

setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.2-release/Latest/ &&  pkg_add -r spindown &&  /usr/local/sbin/spindown -b -p /var/run/spindown.pid -t 1800 -d da0 -d da1 -d da2 -d da3 -d da4 -d da5 -d da6 -d da7 -i 60

I am on 9.1 release, still, hence the setenv command

(Spindown disks da1-da7 after 1800 seconds and check for activity every 60 seconds)
Now how can I check if spindown service is actually running??? From Status|Processes I see nothing relevant....

[b0ssman]

i am on 9.1 and dont need to do the setenv.

i put the command like it is there into the postinit script.

[ChriZathens]

Strange... This is what I got before setenv:

pkg_add -r spindown
Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports ... indown.tbz: File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports ... indown.tbz' by URL

[b0ssman]

good point. i havnt checked if mine is running for a while

[ChriZathens]

I also noticed that ftp://ftp.freebsd.org/pub/FreeBSD/ports ... le/Latest/ is valid, too...
But perhaps the 9.2 version is better

OK, run spindown with -D option, reduced check time to 20 seconds and set idle to 60 seconds for testing

This is what I got:

Code: Select all

device: da0, max_idle_time: 60, rd: 162, wr: 474, frees: 0, other: 15, idle time: 40, state: Spinning
device: da1, max_idle_time: 60, rd: 205, wr: 478, frees: 0, other: 15, idle time: 40, state: Spinning
device: da2, max_idle_time: 60, rd: 239, wr: 472, frees: 0, other: 15, idle time: 40, state: Spinning
device: da3, max_idle_time: 60, rd: 199, wr: 468, frees: 0, other: 15, idle time: 40, state: Spinning
device: da4, max_idle_time: 60, rd: 165, wr: 524, frees: 0, other: 15, idle time: 40, state: Spinning
device: da5, max_idle_time: 60, rd: 144, wr: 522, frees: 0, other: 15, idle time: 40, state: Spinning
device: da6, max_idle_time: 60, rd: 139, wr: 525, frees: 0, other: 15, idle time: 40, state: Spinning
device: da7, max_idle_time: 60, rd: 164, wr: 521, frees: 0, other: 15, idle time: 40, state: Spinning

Stopping device da0
Error received from stop unit command
(pass0:mpt0:0:25:0): START STOP UNIT. CDB: 1b 0 0 0 0 0
(pass0:mpt0:0:25:0): CAM status: SCSI Status Error
(pass0:mpt0:0:25:0): SCSI status: Check Condition
(pass0:mpt0:0:25:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
spindown: Error spinning down device: da0
device: da0, max_idle_time: 60, rd: 162, wr: 474, frees: 0, other: 15, idle time: 60, state: Error
Stopping device da1
Error received from stop unit command
(pass1:mpt0:0:26:0): START STOP UNIT. CDB: 1b 0 0 0 0 0
(pass1:mpt0:0:26:0): CAM status: SCSI Status Error
(pass1:mpt0:0:26:0): SCSI status: Check Condition
(pass1:mpt0:0:26:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
spindown: Error spinning down device: da1
device: da1, max_idle_time: 60, rd: 205, wr: 478, frees: 0, other: 15, idle time: 60, state: Error
Stopping device da2
Error received from stop unit command
(pass2:mpt0:0:27:0): START STOP UNIT. CDB: 1b 0 0 0 0 0
(pass2:mpt0:0:27:0): CAM status: SCSI Status Error
(pass2:mpt0:0:27:0): SCSI status: Check Condition
(pass2:mpt0:0:27:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
spindown: Error spinning down device: da2
device: da2, max_idle_time: 60, rd: 239, wr: 472, frees: 0, other: 15, idle time: 60, state: Error
Stopping device da3
Error received from stop unit command
(pass3:mpt0:0:28:0): START STOP UNIT. CDB: 1b 0 0 0 0 0
(pass3:mpt0:0:28:0): CAM status: SCSI Status Error
(pass3:mpt0:0:28:0): SCSI status: Check Condition
(pass3:mpt0:0:28:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
spindown: Error spinning down device: da3
device: da3, max_idle_time: 60, rd: 199, wr: 468, frees: 0, other: 15, idle time: 60, state: Error
Stopping device da4
Error received from stop unit command
(pass4:mpt0:0:29:0): START STOP UNIT. CDB: 1b 0 0 0 0 0
(pass4:mpt0:0:29:0): CAM status: SCSI Status Error
(pass4:mpt0:0:29:0): SCSI status: Check Condition
(pass4:mpt0:0:29:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
spindown: Error spinning down device: da4
device: da4, max_idle_time: 60, rd: 165, wr: 524, frees: 0, other: 15, idle time: 60, state: Error
Stopping device da5
Error received from stop unit command
(pass5:mpt0:0:30:0): START STOP UNIT. CDB: 1b 0 0 0 0 0
(pass5:mpt0:0:30:0): CAM status: SCSI Status Error
(pass5:mpt0:0:30:0): SCSI status: Check Condition
(pass5:mpt0:0:30:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
spindown: Error spinning down device: da5
device: da5, max_idle_time: 60, rd: 144, wr: 522, frees: 0, other: 15, idle time: 60, state: Error
Stopping device da6
Error received from stop unit command
(pass6:mpt0:0:31:0): START STOP UNIT. CDB: 1b 0 0 0 0 0
(pass6:mpt0:0:31:0): CAM status: SCSI Status Error
(pass6:mpt0:0:31:0): SCSI status: Check Condition
(pass6:mpt0:0:31:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
spindown: Error spinning down device: da6
device: da6, max_idle_time: 60, rd: 139, wr: 525, frees: 0, other: 15, idle time: 60, state: Error
Stopping device da7
Error received from stop unit command
(pass7:mpt0:0:32:0): START STOP UNIT. CDB: 1b 0 0 0 0 0
(pass7:mpt0:0:32:0): CAM status: SCSI Status Error
(pass7:mpt0:0:32:0): SCSI status: Check Condition
(pass7:mpt0:0:32:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
spindown: Error spinning down device: da7

I rebooted the system because I had extended gui enabled to check it it has proven that my controller does not play nice with exgui, leading to these kind of timeouts and errors

EDIT: OK, after reboot seems to work as expected... device spun down

[lindsay]

@appolo567
it show up as LSI SAS2308 now i have to get spindown
What is the commands now to runs S.M.A.R.T on the controller?

One question though as i wonder this card also.

Quite cheaper then the one i got today

[b0ssman]

the card you linked is card you get when you flash an ibm m1015 to it mode.

[lindsay]

I bought it as i could not wait, but nice to know
Is there any i have to set in loader.conf on this card?

[b0ssman]

it seems its shipped with the ir firmware.
on ir mode i dont know but in it mode you dont need to do anything

[lindsay]

It seems easy to do if you follow these instructions

[apollo567]

@appolo567
it show up as LSI SAS2308 now i have to get spindown
What is the commands now to runs S.M.A.R.T on the controller?

One question though as i wonder this card also.

Quite cheaper then the one i got today

My Dell Perc H 310 (LSI Megaraid 9240-8i) worked funily out of the Box for accessing the harddisks ( even with out the additional driver load). After Discussions and some tests together with redAntz we found out in IR you should add mfip_load="YES" to System|Advanced|loader.conf. This is also required to get the Smart Data within the webgui.
With the changes in the Weggui in 1003 you should have then also with the LSI 9211 in IR mode access to the data with the weggui. These two Controller are based on the same LSI 2008 chipset.
If the brandnew (thats the reason why it's more expensive controller) LSI 2308 chipset is supported I don't know .
After a release of a N4F version post 1003 we can check this .

Regards
apollo

[b0ssman]

one thing you can also do is not flash the boot rom.
this way the boot process of the computer is speed up because the lsi controller does not detect drives during boot.

you won't be able to boot of the controller, but you dont want that anyway.

[lindsay]

That`s true b0ssman, and i was discovering something yesterday as i have an old amd opteron ml115 dual 1.83GHZ.
It says it have IPMI 2.0, problem is that 8GB memory is max, i think i will anyway go for this combo in my new nas4free.



Hope this HP NC320i ethernet controller is supported

[b0ssman]

it seems to be working on pfsense 1.2.2.

https://forum.pfsense.org/index.php?topic=12775.0

1.2.2 was freebsd 7.0

[lindsay]

Thanks b0ssman, nice to know, then is the question about the procedure how to access it with IPMI?
Or in another term what do i need?

As you know i have no experience with this at all, but i see the benefits to have it.

[b0ssman]

it depends on the implementation.

you will have an ethernet interface that you need to connect to your network.

normally you will have an web interface running on this, which will give you option to turn on/off etc..