Fireball3

After successfully bricking the Fujitsu D2607 by downflashing it I'm proud to be able to contribute to this thread and hereby report: LSI MegaRAID with SAS2008 chipsets 3) DELL Perc H310 as well as H200 Flashed successfully to LSI9211-8i IT (P20) 3TB Drive Support with this card: YES (UPDATE: 5.0Beta7 added 3TB Drive support) Drive Spin Down support: YES (UPDATE: Added as of 5.0Beta7) Drive Temp Readings: YES Toolset_PercH310 to LSIMegaraid.zip (DOS, via bootable usb key) http://www45.zippyshare.com/v/51016808/file.html (for some reason I can't embed the link...) MD5:80174075959fb7d1ff8c6362f7241bfe Update on 06.08.2014 Included the P19 firmware http://www21.zippyshare.com/v/9541812/file.html Update on 01.12.2014 Possible issues with P20 firmware! See this post and this. Update on 23.10.2015 There is an new version of Avago (former LSI) P20 (20.00.04.00) which seems to be OK with unRAID. See this post. Update on 15.09.2015 User opentoe found out that the DELL IT firmware is also working with unRAID. It's your decision what to flash. Flashing DELL firmware is easier and supported by DELL! opentoe's verdict on DELL IT or Avago (former LSI). Update on 07.06.2016 There is a new firmware from Avago. P20.00.07.00 The toolset has been updated accordingly. First impressions. http://www3.zippyshare.com/v/xZKIOHaz/file.html https://www.mediafire.com/?8f82hx4c032a929 MD5: 24f7d428292e00f9dee6f715d8564202 Update on 30.12.2016 Firmware is still P20.00.07.00 Switch to RUFUS for bootdisk creation. Added alternative ways to extract controller info if MegaCli is not working. https://www.mediafire.com/?9cbklh4i1002n23 MD5: 7d90f84c831e8b939c5536d9eb03ba81 Update on 23.02.2017 Firmware is still P20.00.07.00 Uses sas2flsh through the whole process. Tested on a "backflashed" H200, to be confirmed on a stock H200 card and on H310's. Card backup is now dumping the full flash. This can be used to restore the initial condition of the card. Added script for automatic SAS address extraction. No reboot necessary any more. https://www.mediafire.com/?0op114fpim9xwwf MD5: 2fbe3d562846e493714a9e8ac3f15923 Due to missing UEFI environment, no changes nor testing with UEFI shell. Update on 30.03.2017, v2 Firmware is still P20.00.07.00 Spiced up the routines with some checks to automatically select the right tool if one is not working. Tested on a stock H310 as well as a H200 - works for me. Post your experience in the forum. https://www.mediafire.com/?6b77v4s7czluvs2 MD5: 6cb92336ff537aeb838085a028aa6601 Update on 11.04.2017, v3 Firmware is still P20.00.07.00 Added files for use in an EFI environment. Untested due to missing hardware. Post your experience in the forum. https://www.mediafire.com/?9ovj2rxuaf43wv4 MD5: t.b.d. Update on 17.04.2017, v4 <--- this is the latest, use this one! Firmware is still P20.00.07.00 Corrections for EFI environment. Untested due to missing hardware. Post your experience in the forum. https://www.mediafire.com/?py9c1w5u56xytw2 MD5: t.b.d. If you experience the "failed to initialize PAL" error somewhere in step 5, you have to boot from UEFI shell and try again or use another mainboard. See here how to use UEFI shell (Kudos 2 Maglin). Make sure you read and understand the __READMEFIRST.txt before starting! If you experience troubles or something is not clear, don't hesitate to ask for help. You can help improving the howto by doing so. Chances are small but you can brick the controller!

@itimpi OK. Will try it without preclearing. @garycase In fact, I was doing some testing until now and replacing the 500GB parity with 4TB was the first step to start with the "real" server. As I explained: I pulled the "missing" drive in order to force the "parity-swap". As I wasn't able to do "parity-swap", I put the "missing" drive back and started the parity rebuild on the 4TB drive. Parity was good before pulling the 500GB parity. Everything OK. Shares were accessible during the parity rebuild. I thought it would be good to practice a bit prior to "going live" with the server. I don't think that I did a mistake but it's true, that there is no step by step instruction on how to do a "parity-swap". This is funny, I read this argument every time, and I wonder how that should work? At some point one might have tens of TB of data. Might be costly to back up that amount of data. I fully agree with you, it would be better to do so, but it's not reasonable for private use.

I gave up last night. My intention was to use the "missing" drive as a cache drive and simultaneusly put the new 4TB parity drive in use. But obviously there seems to be an issue with the "parity-swap" function. Because I didn't want to waste the night waiting for answers, I started the alternative. Since I still had the "missing" drive, I triggered a parity rebuild. After that I will pull the "missing" drive and use it as cache drive. I will let unRAID rebuild the "missing" on the old parity drive. Q1: Do I have to preclear a drive that is used for replacing a failed one? Q2: Do I have to preclear a drive that I intend to use as cache? Nevertheless, it remains be checked if this "parity-swap" function is broken in rc16c! I won't be able to contribute with testing after having the 4TB parity installed.

I started another preclear run yesterday night and just had a short view on the progress this morning. Doesn't look good. It was doing the zeroing pass and write rate was about 7MB/s. Then I had a short look at the syslog which is 9MB and full of IO errors for the last 3 hours. I'm not sure if it's really the drive because I also started a parity rebuild and one more preclear on another drive. I can provide an excerpt of the syslog this evening. Now I restarted the preclear. The other tasks will finish in about 2 hours. So when it's zeroing time again the full resources will be available for this preclear process. @RobJ: How can I perform a RMA-ing time is over. It's out of warranty since 12/2012 :-( Edit: I opened a ticket at WD and asked them why the drive is not reallocating the pending sectors. I'll keep you posted if they answer.

Here are the screenshots Trying to find that thread with the "copy button" but its not so easy... Edit: Here is the "copy button" thread http://lime-technology.com/forum/index.php?topic=25433.msg221507#msg221507 After assigning the disks I cannot start the array.

Hi, I'm desperately trying to do a "Parity Swap". If you are adding a new disk or replacing a disabled disk, try Parity-Swap. I changed the new drive (the biggest) to parity and the old parity to the missing drive. In an other tread i read a "copy" button should appear - but not here. What am I missing??? Running rc16c Cheers Fireball3

Noticed this thread shortly after posting my results here. http://lime-technology.com/forum/index.php?topic=28989.0 Sorry for that but perhaps you can have a look at it?

Hi, I precleared this drive twice. Unfortunately I didn't save the results of the first run but here is the most recent one. The test passed but as you can see, there are a lot of sectors pending re-allocation. Why isn't this done? The raw value of "Reallocated_Sector_Ct" is 0. I understand there are enough sectors left to re-allocate bad ones. What is your opinion? Regards ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sdb == WDC WD15EADS-00P8B0 WD-WMAVU0911268 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 5:57:07 (70 MB/s) == Last Cycle's Zeroing time : 5:31:46 (75 MB/s) == Last Cycle's Post Read Time : 11:22:26 (36 MB/s) == Last Cycle's Total Time : 22:52:19 == == Total Elapsed Time 22:52:19 == == Disk Start Temperature: 29C == == Current Disk Temperature: 35C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 115 121 0 ok 35 No SMART attributes are FAILING_NOW 35 sectors were pending re-allocation before the start of the preclear. 41 sectors were pending re-allocation after pre-read in cycle 1 of 1. 188 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 193 sectors are pending re-allocation at the end of the preclear, a change of 158 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ @start Disk: /dev/sdb smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD15EADS-00P8B0 Serial Number: WD-WMAVU0911268 Firmware Version: 01.00A01 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Aug 18 22:16:39 2013 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (32400) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 186 182 021 Pre-fail Always - 5691 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1299 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 3817 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 187 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 145 193 Load_Cycle_Count 0x0032 194 194 000 Old_age Always - 19908 194 Temperature_Celsius 0x0022 121 103 000 Old_age Always - 29 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 35 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 3408 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. @finish Disk: /dev/sdb smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD15EADS-00P8B0 Serial Number: WD-WMAVU0911268 Firmware Version: 01.00A01 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon Aug 19 21:08:58 2013 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (32400) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 186 182 021 Pre-fail Always - 5691 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1299 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 3840 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 187 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 145 193 Load_Cycle_Count 0x0032 194 194 000 Old_age Always - 19909 194 Temperature_Celsius 0x0022 115 103 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 193 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 3408 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

Still looking for an appropriate HBA. It's not so easy to find one at reasonable prices in Europe/Germany - I envy you guys in the US!. Found a Perc H310 @ebay for about 70€+shipping but would that work? Is it correct, that despite the IT mode that comes with the dell firmware, this controller will not necessarily work with unraid since it is not the LSI firmware? I suppose the driver for this specific firmware is provided by ESXi? So, if I don't want to set up an ESXi, the fact that IT mode is working is not enough. Then one should try the last steps described in this thread: http://forums.servethehome.com/raid-controllers-host-bus-adapters/467-dell-h200-flash-firmware-procedure-dell-servers.html The OP did that with the Perc H200. Doing it with the H310 is an EXPERIMENT!

Yes, that was my last hope. This guy apparently has it working with "unsupported firmware" (LSI 9240 8i???) http://mmurayama.blogspot.de/2013/02/setting-up-jbod-with-fujitsu-d2607-raid.html Now this is really bad news isn't it? :'( :'( :'( :'(...going to search the forums... :'( :'( :'( Edit: Ford Perfect, it's been a while, but I read you also had troubles flashing the M1015. You flashed with I also flashed the LSI firmware with megarec not sas2flash. Would it be possible to flash the IT.rom with megarec instead of sas2flash?

Hi 2 all unraiders! I'm in the process of gathering equipment for an unraid server. I already set up an ASUS M4A87TD EVO with a 140 Sempron and 2GB RAM. Unraid is already running with 3 test drives. Before going live with the big drives I want to make sure to have enough free slots for upgrading because I expect the 5+1 (sata+esata) slots that come with the mobo will soon be fully equipped. After reading this http://lime-technology.com/forum/index.php?topic=12767.msg139775#msg139775 I shot myself a Fujitsu D2607 on ebay and yesterday I tried to put it in IT mode with the MEGA firmware. Tried v10 and v11 and it seems it's not possible. I have the same issue as described here (Failed to validate MfgPage2!): http://lime-technology.com/forum/index.php?topic=12767.msg137851#msg137851 At that point I turned google on again and found a thread on a german forum. http://www.hardwareluxx.de/community/f15/lsi-megaraid-und-dell-perc-5-6-sas-sata-pcie-5-a-793769-74.html#post19868191 User tdz2000 states that it is not possible to flash the FSC D2607 with IR/IT firmware. Well, that's what I already learned... But he provides a method to flash the LSI MegaRAID SAS 9240-8i firmware. Unfortunately I don't fully understand what he's trying to do in his steps. Any help appreciated! Let me translate it for you: 1. download the firmware from FSC website and run it //purpose not clear 2 me// - reboot - 2. megarec -writesbr 0 sbrempty.bin //write an empty.sbr like in the tutorial available in this tread// 3. megarec -cleanflash 0 //delete flash// - reboot - 4. Megarec -writesbr 0 sbrlsi.bin //don't know which sbrlsi.bin to use; he just says: sbrlsi.bin is found with google... :-( ; in fact, I found one file which is suitable for 9260, 9280 a.s.o and I wonder if it will work for 9240 also?; anybody here with a proper sbrlsi.bin? // 5. download firmware for LSI MegaRAID SAS 9240-8i and megarec -m0flash 0 xxxxxxxx.rom - reboot - 6. Megarec -writesbr 0 D2607.bin //write the original Fujitsu SBR else it will "hang up" at boot// 7. MegaOEM -AdpSetSASA xxxxxxxxxxxxxxxx -a0 //write back the card id - will not work with mega.exe; use megaoem.exe (a0 = controller number if there are more than 1)// I had problems in finding the sbrlsi.bin and obviously chose a wrong one because it issued an error but the next step went through (had it all done in a batch file). At that point I had to stop because there was no more time for toying around. Today I have to let him write a new ADAPTERS.TXT to get some more information and make sure it's a LSI. Now I'm wondering if I can make use of the card without the dedicated IT mode? What problems should I expect? br Fireball