crusader3k4
Cadet
- Joined
- Aug 4, 2015
- Messages
- 6
@solarisguy Thanks for that. I upgraded to 20.00.04.00 without any problems.
@AlVal Thanks for clarifying!
@AlVal Thanks for clarifying!
[root@nas] /tmp/Installer_P20_for_FreeBSD/sas2flash_freebsd_amd64_rel# ./sas2flash -listall LSI Corporation SAS2 Flash Utility Version 20.00.00.00 (2014.09.18) Copyright (c) 2008-2014 LSI Corporation. All rights reserved Adapter Selected is a LSI SAS: SAS2008(B2) Num Ctlr FW Ver NVDATA x86-BIOS PCI Addr ---------------------------------------------------------------------------- 0 SAS2008(B2) 12.00.00.00 0c.00.c0.08 No Image 00:04:00:00 Finished Processing Commands Successfully. Exiting SAS2Flash.
[root@nas] /tmp/Installer_P20_for_FreeBSD/sas2flash_freebsd_amd64_rel# ./sas2flash -list LSI Corporation SAS2 Flash Utility Version 20.00.00.00 (2014.09.18) Copyright (c) 2008-2014 LSI Corporation. All rights reserved Adapter Selected is a LSI SAS: SAS2008(B2) Controller Number : 0 Controller : SAS2008(B2) PCI Address : 00:04:00:00 SAS Address : 55cd2e4-0-0004-9924 NVDATA Version (Default) : 0c.00.c0.08 NVDATA Version (Persistent) : 0c.00.c0.08 Firmware Product ID : 0x2213 (IT) Firmware Version : 12.00.00.00 NVDATA Vendor : Intel NVDATA Product ID : Intel(R) SSD 910 BIOS Version : N/A UEFI BSD Version : N/A FCODE Version : N/A Board Name : Intel(R) SSD 910 Board Assembly : N/A Board Tracer Number : CVRD31130088400C Finished Processing Commands Successfully. Exiting SAS2Flash.
Yes, it seems so. The update is safe to on-disk data, but you can disconnect the drive if you're paranoid.As it appears to already be in IT mode, does this mean that I only have to "upgrade" the current firmware and I won't lose all the data on the disk? (I use this disk as the system dataset pool as well as for jails.)
The EFI version of sas2flash is typically more successful in weird cases and is generally safer, since FreeNAS isn't running.Can I then use the utility on freenas without booting into some other prompt?
The BIOS extension ROM (also available as an EFI extension ROM for P20) allows you to boot from the card and to manage the card. Since it's in IT mode, you can only view the SAS topology and configure spinup delays, I believe.Also, there appears to not be any bios installed. What does this imply? Is the bios what makes the disk bootable? (I have another identical disk and would like to make it bootable for use in my normal Desktop.)
Yes, it seems so. The update is safe to on-disk data, but you can disconnect the drive if you're paranoid.
The EFI version of sas2flash is typically more successful in weird cases and is generally safer, since FreeNAS isn't running.
The BIOS extension ROM (also available as an EFI extension ROM for P20) allows you to boot from the card and to manage the card. Since it's in IT mode, you can only view the SAS topology and configure spinup delays, I believe.
I updated from within FreeNAS itself using the FreeBSD installer utility that was found at the same page as the firmware download. My update went without a hitch. I didn't even have to reboot.
c) [C stands for complicated] :D
- redo things not saved
Only networking, depending on your current setup.Seems easy enough. What kind of things wouldn't be saved?
Also, some people perform customizations outside of the FreeNAS framework. Let's say adding something to /usr/local/bin like unrar, as opposed to having unrar in a jail.Only networking, depending on your current setup.Seems easy enough. What kind of things wouldn't be saved?
Hi Folks,
So I'm about to have 2 weeks off and I figure this would be a great time to go around and upgrade all stuff at home. So I just want to confirm the best procedure before i go upgrading the firmware.
Build: FreeNAS-9.3-STABLE-201506292130 (before they updated the driver)
Motherboard: SuperMicro X10SL7-F
Controller: LSI 2308
Current Firmware: 16
So I assume I still need to upgrade to 20? This version ftp://ftp.supermicro.com/Driver/SAS/LSI/2308/Firmware/IT/PH20.00.04.00-IT.zip ?
I plan do using EFI to re-flash the controller. In what order would you recommend I do this?
a) Upgrade freenas, reboot into EFI and flash controller, reboot than boot into freenas
b) Shutdown, boot into EFI & Flash Controller, reboot into freenas than upgrade freenas.
Looking for the safest option as whilst i do have a backup of the important stuff, I currently don't have enough space to backup my media since it grow abit to much when i went BD-RIP crazy =P. <-- To be fixed when wife lets me spend $$
Also, some people perform customizations outside of the FreeNAS framework. Let's say adding something to /usr/local/bin like unrar, as opposed to having unrar in a jail.
Well I guess I'm a moron. Do you mean if you're in FreeNAS (not in a jail) and type a command that only exists in a jail, it will work? How does that work? The defaults paths don't seem to reach into jails.Which is moron-class stupid, since you can run the unrar-that's-in-a-jail in the host environment.
The path can probably be found, but will the jail unrar work in FreeBSD 10.x?Well I guess I'm a moron. Do you mean if you're in FreeNAS (not in a jail) and type a command that only exists in a jail, it will work? How does that work? The defaults paths don't seem to reach into jails.
Well I guess I'm a moron. Do you mean if you're in FreeNAS (not in a jail) and type a command that only exists in a jail, it will work? How does that work? The defaults paths don't seem to reach into jails.
The path can probably be found, but will the jail unrar work in FreeBSD 10.x?