Search the Community

Showing results for tags 'lsi'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Storage Hardware
    • SMB/Enterprise Storage
    • RAID Cards and HBAs
    • Solid State Drives (SSD)
    • Hard Disk Drives (HDD)
    • Home Storage and Computer Hardware
    • What Drive Should I Buy?
  • StorageReview News, Reviews and Projects
    • Storage News & Reviews
    • Enterprise Test Lab Reviews/Projects
  • General
    • Site Suggestions & Help
    • Storage and Tech Bargains
    • StorageReview Marketplace
    • The Bar & Grille
    • Reliability & Performance Drive Databases

Calendars

  • Community Calendar

Found 8 results

  1. Hi, I have LSI Syncro CS 9271-8i installed and I found small issue here: I created a Node A and it has a shared Virtual Disk (VD). Now, when Node A reboots, the VD is being transferred to peer Node B and the VD will stay in Node B - no matter node A is up or not. Is this normal? Any expert here knows how to transfer VD from Node B back to Node A when A is online? Below is the information --- I would appreciate it if anyone here could give me some feedback. Thanks. #/opt/MegaRAID/storcli/storcli64 /c0 show Generating detailed summary of the adapter, it may take a while to complete. Controller = 0 Status = Success Description = None Product Name = LSI Syncro CS 9271-8iQ Serial Number = SV40421776 SAS Address = 500605b008929d30 PCI Address = 00:85:00:00 System Time = 06/25/2017 00:24:34 Mfg. Date = 01/23/14 Controller Time = 06/25/2017 00:24:33 FW Package Build = 23.6.1-0018 BIOS Version = 5.43.00.0_4.12.05.00_0x06000500 FW Version = 3.330.05-2793 Driver Name = megaraid_sas Driver Version = 06.811.02.00-rh1 Vendor Id = 0x1000 Device Id = 0x5B SubVendor Id = 0x1000 SubDevice Id = 0x927B Host Interface = PCI-E Device Interface = SAS-6G Bus Number = 133 Device Number = 0 Function Number = 0 Drive Groups = 2 ... /c0/v0 : ====== --------------------------------------------------------------- DG/VD TYPE State Access Consist Cache Cac sCC Size Name --------------------------------------------------------------- 0/0 RAID0 Optl RW Yes RWTC - ON 558.406 GB --------------------------------------------------------------- Cac=CacheCade|Rec=Recovery|OfLn=OffLine|Pdgd=Partially Degraded|Dgrd=Degraded Optl=Optimal|RO=Read Only|RW=Read Write|HD=Hidden|TRANS=TransportReady|B=Blocked| Consist=Consistent|R=Read Ahead Always|NR=No Read Ahead|WB=WriteBack| AWB=Always WriteBack|WT=WriteThrough|C=Cached IO|D=Direct IO|sCC=Scheduled Check Consistency PDs for VD 0 : ============ ------------------------------------------------------------------------------ EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type ------------------------------------------------------------------------------ 10:0 16 Onln 0 558.406 GB SAS HDD N N 512B ST3600057SS U - ------------------------------------------------------------------------------ EID-Enclosure Device ID|Slt-Slot No.|DID-Device ID|DG-DriveGroup DHS-Dedicated Hot Spare|UGood-Unconfigured Good|GHS-Global Hotspare UBad-Unconfigured Bad|Onln-Online|Offln-Offline|Intf-Interface Med-Media Type|SED-Self Encryptive Drive|PI-Protection Info SeSz-Sector Size|Sp-Spun|U-Up|D-Down|T-Transition|F-Foreign UGUnsp-Unsupported|UGShld-UnConfigured shielded|HSPShld-Hotspare shielded CFShld-Configured shielded|Cpybck-CopyBack|CBShld-Copyback Shielded VD0 Properties : ============== Strip Size = 256 KB Number of Blocks = 1171062784 Span Depth = 1 Number of Drives Per Span = 1 Write Cache(initial setting) = WriteBack Disk Cache Policy = Disk's Default Encryption = None Data Protection = None Active Operations = None Exposed to OS = Yes Creation Date = 22-06-2017 Creation Time = 02:46:01 AM Host Access Policy = Shared Peer Has Access = YES VD GUID = 4c5349202020202000105b0000107b9269897c46660b80f9 Emulation type = default Is LD Ready for OS Requests = Yes SCSI NAA Id = 600605b008929d3020ddebe9760e1fec
  2. This intel/LSI card seems to support 6GB/s data transfer and mentions SAS specifically. It also mentions SATA but has numerous references to SATA II not III in it's documentation. I have a SATA II capable older system and was thinking of reusing this raid card I no longer use as a SATA III card to improve thruput of the SATA III hard drives in the system. Anyone know what this card really is? If it is SATA II only, any suggestions of cards that I could use? Just a basic SSD drive and a few hard drives. No raid at the moment that I'm planning but if the card supported hardware raid wouldn't mind just don't want to spend much on anything for this older system I'm reviving. Thanks. JR
  3. Hi forum. I'm looking to buy the mentioned controller. One online shop (I'd rather not tell ) offers the non-Dell version of the controller for 700 USD and the Dell version for 480 USD. The specifications look similar. Both are based on the LSISAS2208 chip and both have two SFF-8087 ports. The Dell version specifies model: 403-BBEL. The non-dell is the standard LSI model: LSI00331. Apart from the model and the price, I see no difference. I suspect that the Dell version may have some limitations because of the reduced price, but it is difficult for me to guess what those might be since my experience with cards of this type is limited. I plan on purchasing the cachecade module (ssd cache) along side the controller. Thus, if the Dell controller does not support cachecade, ill go with the more expensive one. Have you encountered a similar "deal" in the past? What do they usually entail? How can I figure out what the differences are short of emailing the shop and asking them (I have already done that). If the answer can be found on the manufacturers site (LSI and Dell), then any points on what to look for are welcome. If the difference lies in the return policy and warranty, I'm willing to take the chance. I can guess that "KIT" vs "non-KIT" pertains to included cables in the raid-controller market. Dell version: LSI version:
  4. During today's attempts to make filesystem on a 15 TB virtual drive (RAID60) built on top of MegaRAID SAS 2108 from 4Tb SAS 7.2K drives I figured that each time I am receiving the following error : ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir I had IDC technical support to reseat the controller, check all SAS cables to disks, reseat the disks, which were marked as Failed after receiving the above error message. Also, I have tried: - create filesystem on partitioned device : /dev/sdb1; - create filesystem on LVM on top of PV, which contains of /dev/sdb - add disks in RAID50 and create filesystem on both device and LVM. Btw, command, which I am using to create filesystem is: mkfs.ext4 -L home /dev/vg00/lv_home or mkfs.ext4 /dev/sdb1 My special suspect is put into "Background initialization" process, seen in Virtual drive info: and that this virtual drive is in inconsistent state: MegaRaid documents are telling the following about "Background Initialization" and I cannot get if it is 100% necessary to be completed before further operations with drive or not: Perhaps, someone can advise on why filesystem fails to be created there and if I really need to allow "Background Initialization" process to finish before creating fs?
  5. I have a LSI MegaRAID SAS 9260-16i RAID controller. Somehow it's become corrupted and now it the machine won't load the card on startup. The following message appears: On-board expander FW or mfg image is corrupted. Flash expander FW and mfg image using recovery tools. This is before POST has completed so I can't boot the machine, load the BIOS or load the WebBIOS in order to try and flash the firmware. It's running the latest version of the firmware (2.130.403-3066, package build 12.15.0-0189). I've tried booting the machine with a good RAID card with the corrupt on in a second PCI but it still fails to load the corrupt card. Any help appreciated!
  6. Hello, anyone using LSI MegaRAID SAS 9271-8i controller ? While controller is doing consistencycheck and I pauze it or reboot my server - controller is not booting anymore and all RAID data is lost. We already replaced our controller with RMA - no luck. If anyone tries to reproduce - be warned that data lost may occur! Debian 7.5 Linux xxxxxx 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux Firmware 3.240.05-2282 Firmware 3.340.55-3173 LSI MegaRAID SAS Driver 00.00.06.12-rc1 LSI MegaRAID SAS Driver 00.00.06.703.11
  7. Hi I have 3, 3TB WD Red drives on a LSI 9260CV in raid 5. Read = always read ahead IO Policy = Cached IO Write = Always write back OS= Win 2012R2 latest, firmware Drivers lastest I did some benchmarks and I can only explain the sequential results. The rest I dont get it, Raid5 is supposed to have slower writes due to parity calculation. The LSI card has 512K cache and for sure it influenses the results: the numbers get smaller as the ratio cahe/file size changes. While this is normal, there is always 50% more throughtput for random writes and this is consistent whatever the file size. I would expect that ratio to drop also as the test file grows bigger (if the cache was the reason for this strange performance). Here are results for a tiny file that fits entirely into the boards cache, so numbers reflect PCI transfer not disk perfomance. What did I miss ? m a r c
  8. I’m trying to run two HBA’s in the same server (SuperMicro X9SCA Mother Board) and am running into an issue where only 1 of the cards will initialize during the pre-boot phase of startup. The initialization is not random, but is instead based on the physical order of the cards in the server (Whatever is closest to the CPU boots). Unsurprisingly, the card that does not initialize is not seen by the OS. One card is an LSI 9211-8i (SAS2008) flashed in IT mode, the other is a rebranded LSI 1068e (Dell SAS 6) still with default IR firmware. I’ve looked around google and can’t seem to find an answer as to why this doesn’t work, as the general consensus is that it shouldn’t be too much trouble. Any ideas would be appreciated, thanks!