http://www.newegg.ca/Product/Produc...15788-_-Product

http://www.newegg.ca/Product/Produc...E9473-_-Product

我是來到 阿里巴巴 還是淘寶

對了

卡敗了沒???

還沒 很吸引人..
但是找不到地方可以用......
手邊只有3TB/4TB的HDD...

了解∼

我主力還是在 2TB






當初敗太多個了


冬天到了
可以開機整理資料了

我之前的20顆WD SAS 6Gbps 1TB差不多都快壞光了.....

好像你東西都不怎麼耐用

這樣也去了不少 $$$$ 吧

這是LSI使用者可能會遇到的討厭問題..
因為這問題發生後真的很煩人....
Q1:
"I am getting the following information in my Logs. Is there a problem?"
A1:
It is working as designed, if they are SATA drives and the array is a SAS.
A SATA drive may not rebuild a SAS drive array so this is a warning telling you the drive may not rebuild a SAS array.

If you have a SATA array and a SAS array and want to use a spare, make sure that you have set the spare drives (S-ATA or SAS) as a designated spare, not global spare.
Q1的描述很少人這樣做, 但是這種情況就算是SATA array依然也會有. 這問題很噁心..
alarm會一直響不停, 很煩!..

Q2:
Enabling 'Use Unconfigured Good as Emergency Hot Spare (EHSP)' can cause alarm to sound on LSISAS2108 based controllers (e.g. 9260, 9260CV).
A2:
By default 'Use Unconfigured Good as Emergency Hot Spare (EHSP)' is disabled.

It can be checked/enabled/disabled with MegaCLI:

To check the current value: MegaCli -AdpGetProp enableeug -aN|-a0,1,2|-aALL (e.g MegaCli -AdpGetProp enableeug -a0)
To enable 'Use Unconfigured Good as Emergency Hot Spare (EHSP)': MegaCli -AdpSetProp enableeug=on -aN|-a0,1,2|-aALL (e.g MegaCli -AdpSetProp enableeug=on -a0)
To disable 'Use Unconfigured Good as Emergency Hot Spare (EHSP)': MegaCli -AdpSetProp enableeug=off -aN|-a0,1,2|-aALL (e.g MegaCli -AdpSetProp enableeug=off -a0)


It can be checked/enabled/disabled with StorCLI:

To check the current value: storcli /cx show enableeug (e.g storcli /c0 show enableeug)
To enable 'Use Unconfigured Good as Emergency Hot Spare (EHSP)': storcli /cx set enableeug=on (e.g. storcli /c0 set enableeug=on)
To disable 'Use Unconfigured Good as Emergency Hot Spare (EHSP)': storcli /cx set enableeug=off (e.g. storcli /c0 set enableeug=off)
If 'Use Unconfigured Good as Emergency Hot Spare (EHSP)' is enabled and an unconfigured good drive (or the same drive that drops from the RAID volume, then is incorporated back in later) is used to rebuild the RAID volume, then the alarm will sound continuously, even once the RAID volume is done rebuilding.

There are several ways to keep the alarm from sounding:

Disable the alarm
Clear the alarm (note: the alarm will sound again after a system restart)
Have the RAID volume copy back the drive that was used as an emergency hot spare to a different drive. Once the different drive is part of the RAID array, then the alarm will no longer sound. If desired, you can copy back that new drive back to the original drive. The alarm will then no longer sound.
You can delete the RAID volume, then recreate it. Since deleting the RAID volume will result in the loss of all data, be sure to backup any data that you want to keep before deleting the RAID volume.
If you are using LSI SAS2108 firmware v12.12.0-0139/2.130.373-2022 or newer, then this beeping will not happen.
Upgrading the firmware to v12.12.0-0139/2.130.373-2022 or newer after the beeping starts won't resolve the issue. To stop the beeping, you must do one of the four steps described above.

Q1:
Are Advanced Format / 4K / 512e disk drives supported on LSI RAID controllers?
A1:
4K / Advanced Format drives are supported by some LSI controllers models. See the Compatibility list to see which specific models have been tested:

LSI1078 based controllers - These do not support 4K drives
LSISAS2108 based controllers - These do not support 4K drives
LSISAS2208-based - Some specific 4K drives are listed as compatible
LSISAS3108-based - Some specific 4K drives are listed as compatible

512e is supported with LSI MegaRAID LSISSAS2108-based controllers (e.g. 9260/9261/9280) starting with the MR4.8 code set release.

512e is supported with LSI MegaRAID LSISSAS2208-based controllers (e.g. 9265/9271/9285) starting with the MR5.5 code set release.

也許有一種情況是, LSISAS2108更新了f/w. 但是512e的最佳化支持, 依然可能不確定是否啟動. 最快的方式就是安裝FTS的ServerView RAID Manager來檢查對於512e支持是否有啟動...

Q2:
Sector alignment needs with MegaRAID controllers
A2:
MegaRAID controllers actually store their configuration data at the end of the drive, using the last 512MB of space on each drive. This space is used for both the configuration data necessary to ensure mapping of where the data should be written as well as something of a swap file for when a Migration is done (adding another disk or changing the RAID level of an existing array).

For this reason, no additional OS alignment considerations are needed when using LSI MegaRAID controllers. Sector 0 of each drive will be the first sector that is passed up to the OS (whether 4k, 512b, or emulated 512b from 4k).

In addition to the above, please keep in mind that only 512b sectors are supported by LSI for our MegaRAID products at this time. See the LSI compatibility list to see if 4K drives have been added to the list. Future support of 4k sectors is planned, although there is no firm date or product selection for this.
4k support在LSISAS2208之後以實作.

最近敗了不少的 4TB

所以手又開始癢了

（喂喂喂... 客廳那個 雜七雜八的 16+ HDD 的機器先讓它運作好嗎 從10月就放到現在了）

LSI 9300 MegaRAID SAS 9361-4i

目前看上的傢伙

手上已經有張 9260 所以不想再買一樣的卡了

LSI 9271-4i 是退一步的選擇

可是 在 Newegg 兩個卡只差 $0 ...


不管怎麼樣
還是想再買張 Intel RES2SV240 回來搭配
實在不想買兩個 Port 的 controller card 回來

新卡是配 LSISAS3108 看了一下好像沒什麼會需要的功能