Ix4-300D as iSCSI target cause alert disk is full

I am using ix4-300D with RAID5 as iSCSI target.
Once I create largest volume using all capacity, ix4-300D sends warning disk is full.  Because we monitor this iSCSI target using E-mail alert, I want to eliminate this warning message.  There is no configuration point on Web management GUI.  
I guess other people using this unit as iSCSI target have same concern.  If you know something, please help me about this.  Thanks in advance.
Alert message:
The amount of free space on your Lenovo ix4-300d is below 10% of your total capacity.

Thank you for your reply.
I gave up to use 11% of diskspace as iSCSI target of VMware ESXi because catching alert message is more important for production environment.  I hoped interface to disable some type of alerts.
I am not sure about using remained 11% space for NFS NAS or something.  It is because iSCSI Target volume will contain VM Guest OS volumes which require very stable operation. 

Similar Messages

  • Ix4-300d Add iSCSI Drive Issue

    Hello Everyone, I have a brand new, out of the box ix4-300d. When i go into the iSCSI area, enable the iSCSI feature and click "Add an iSCSI Drive" the add drive area does not appear. I have tried this in IE 9, IE 11, and Chrome 43.0.2357.130 m. See below for screenshot.
    The system is updated to the latest Firmware and I even did a factory reset of the device with no luck.  Any ideas on what I need to do to fix this? EDIT: I realized this is in the wrong forum could a Mod move this one - sorry for the trouble. Thxm-S 

    Interesting. I just created a standard share on the device. After I did that, the iSCSI drive configuration area appeared and was accessible. I have no idea why this worked but it did!!! -S

  • Ix4-300d addiing hdd issue

    Hi!
    I started off with 3x3tb in RAID5 and now upgraded with a 4th disk of the same model. Extension went smoothly, and I see the new size in the Drive Management (as well as the header bar), however the shares still report the old size. Already tried rebooting but didnt bring the expected success
    My guess is that some storage pool would need extending, but I didnt find any such option anywhere. Any help appreciated 
    Cheers,
    Franky
    Solved!
    Go to Solution.

    Hi,
    I have the same problem actually with my new ix4-300d. Started with 3 3TB-Disks in Raid5 and added No 4.
    Total Drive Size:10.92 TB
    Capacity:8.13 TB
    Used Space:4.01 TB
    Free Space:1.32 TB
    Unallocated:2.71 TB
    Firmware Version 4.1.102.29716
    Logfile entries:
    08/26/2014 5:28 pm        System    9070    Expanding data storage.
    08/26/2014 5:28 pm        System (svcd)    9088    Storage verification completed.
    08/27/2014 4:27 pm        System    9076    Storage expansion completed.
    Several times the message like
    08/27/2014 6:37 pm        System    6923    The device is configuring storage...
    The link "Perform an offline file system check then reboot" in Drive Management Settings did only reboot and no fs check started.
    In this forum I found the link to ix4-300d/manage/diagnostics.html. The "Perform an offline file system check then reboot"-link in the storage section started a fs check, no change.
    What can be done?Thanks für Help HCHO

  • Ix4-300d iSCSI disconnect Windows 2012R2

    Hello Everyone,
    I just recently purchased (3 days ago) an ix4-300D and updated it to the latest patch.  I have 4 x WD 3TB Disks and they are configured with a raid 0 configuration.  I then have 2 NICs (not bonded) and using the second port for the iSCSI LAN (192.168.100.100, Jumbo Frames 9000) and the 1st port for accessing the device (192.168.1.100).  I carve out 3 TB iSCSI LUN (with CHAP) and give it a name. My Windows Server sees this (under the 192.168.100.X network) and I"m able to bring it online, mount it, format it and use the LUN.  I then start copying about 2.5 TB of Data off an ix2 back to this Ix4 and about 1/4 through the copy, the iSCSI disconnects and the actual unit is frozen., It won't respond to web interface on the 192.168.1.x LAN either. I have to actually unplug it and then plug it back in for the unit to respond.   I know that iSCSI works on the Window Server as I replaced a custom NAS Server using OpenFiler and worked for over 2 years w/o issues/reboots or anything else. The only thing that has changed is the NAS box (the ix4-300d).  Can anyone think of anything I could be doing wrong? What to check? I am thinking it is a bad unit but I want to check everything first.
    I will say the only thing that *could* be out of line (but is VERY doubtful is the problem) is that 3 of the WD drives are 3TB Reds and 1 is a 3 TB Black. I'm going to remove the black drive and redo the entire unit to see if that resolves the problem but I doubt it will.  I know the Reds are "certified".
    I have already removed the Jumbo Frames just in case (though the windows networking card supports Jumbo Frames 9000 since the old SAN was working with these w/o issue).
    Thoughts anyone???

    Hello CPXGreg
    Using a mixed disk array can cause instabilities, so I do recommend that you try using the unit without the WD Black disk for at least testing.
    Next, there are various factors that could cause or contribute to a firmware lock like this.  Usually this is caused by media server crashing, which then escalates to a full firmware lock.  I recommend checking that media server has been turned off for now and any unused protocols.  If the unit still locks up I recommend that you contact LenovoEMC support to have a dump report from the unit reviewed.  This way we can check what may be at the root of the issue.
    LenovoEMC Contact Information is region specific. Please select the correct link then access the Contact Us at the top right:
    US and Canada: https://lenovo-na-en.custhelp.com/
    Latin America and Mexico: https://lenovo-la-es.custhelp.com/
    EU: https://lenovo-eu-en.custhelp.com/
    India/Asia Pacific: https://lenovo-ap-en.custhelp.com/
    http://support.lenovoemc.com/

  • Server 2012 R2 iSCSI Target - Multiple targets per iSCSI Virtual Disk with CHAP

    Scenario I am trying to achieve is this:
    Windows Server 2012 R2 serves as iSCSI Target configured to have 1 iSCSI Virtual Disk
    2 Hyper-V servers connecting to this target with iSCSI Inistator and have multiple targets for that iSCSI Virtual Disk using CHAP
    **These 2 are nodes in fail over cluster, this iSCSI is added as a CSV.
    Issue that I have, is that you can only have 1 target per iSCSI Virtual Disk
    Both Hyper-V servers can connect to this LUN without issue when I add both initiator IDs to the target, but once I enable CHAP, you can only put one initiator ID in the "Name" field, so I can only connect from 1 Hyper-V server.
    Do you know of a way around this?

    From my understanding, "chaptest" is a single target, my goal was to make 2 targets to the same iSCSI virtual disk.
    So if you were to right click the iSCSI virtual disk that "chaptest" is assigned to and click "Assign iSCSI Veritual Disk...", then select "New iSCSI Target, and proceed with the wizard it removes the "chaptest" target
    and adds the new one just created.
    My goal was to have 2 targets to 1 iSCSI VD, but seeing your screenshot, with 2 initiators connected, that goal doesn't seem needed anymore.
    I was under the impression that the "User name" = the iscsi initiator IQN name, which had to be unique. That is why I thought I would need 2 targets.
    Thanks

  • Ix4-300d JBOD as truly independent disks

    When I first bought the ix4-300d, I instlaled just one drive.  I just tried installing a second drive, but I cannot get the two drives to show up as two truly independent drives, just one volume.  I want to choose the drive in whch I can store the data on.  It doesn't look like this is possible.  Can the firmware be upgraded to have this ability?

    I would not put too much hope on this.
    As far as I have seen the ix4 -series never has been designed for supporting more than one volume ( either JBOD or Raid). You could try with iSCSI-Configurations, but I never have seen that alive yet.

  • Ix4-300d disk firmware

    Hi,
    I recently bought ix4-300d with 4 2TB ST2000DM001-1ER164 (firmware CC25). Already having updated the devices firmware I saw on this thread 1524192 "We do not recommend or see it necessary to update the firmware unless you have firmware CC37 or lower". Now considering I have CC25 and the latest version by seagate is CC4H I was wondering how to upgrade the drives. I am fairly technical but I do not want to void the warranty so was looking at an official solution.
    Thanks

    Hello gsharad007
    LenovoEMC does not have a firmware (seagate firmware) update utility that will run through the ix4-300d.  If you wish to update the internal hard disks' seagate firmware, please go to the seagate support page to download any updates and apply them to the disks outside of the ix4-300d chassis.  This would not void the warranty on the ix4-300d.
    LenovoEMC Contact Information is region specific. Please select the correct link then access the Contact Us at the top right:
    US and Canada: https://lenovo-na-en.custhelp.com/
    Latin America and Mexico: https://lenovo-la-es.custhelp.com/
    EU: https://lenovo-eu-en.custhelp.com/
    India/Asia Pacific: https://lenovo-ap-en.custhelp.com/
    http://support.lenovoemc.com/

  • Lenovo Iomega ix4-300d Disk Firmware Upgrade

    Hi guys,
    Is there a any way to upgrade my Seagate ST2000DM001-9YN164 Firmware from the IX4-300D device?
    The Seagate have a firmware upgrade utility, but is a livecd and it is for i686 hardware.
    Solved!
    Go to Solution.

    We do not recommend or see it necessary to update the firmware unless you have firmware CC37 or lower. Is there a particular reason you wanted to upgrade the firmware? These drives should work with our device without needing to update the firmware.
    If you want to upgrade the firmware, then you will have to do so manually by taking the hard drives out individually and connecting them to your computer. Seagate has a program called SeaTools (http://www.seagate.com/support/downloads/seatools/) that you should be able to update the firmware with. However, be advised that if you are in warranty and perform the update and the device is damaged, it will void your warranty.
    Have questions and need answers?
    Search the database for answers to FAQ's, software/driver downloads, tutorials, news, features and more!
    LenovoEMC Support & Downloads
    LenovoEMC North America Support Contact Page

  • Ix4-300d network interface going off-line

    I just got a new ix4-300d to use as an iSCSI target in a relatively low-performance requirement file server.
    I have used ix4-200d and ix4-300d in the past for iSCSI targets in disk-based backup scenarios wihtout issues. 
    I am having problems with this one, though. I am attempting to copy data to this new unit (with a VHD mounted from the iSCSI connection to the system), and while data seems to copy OK, at some point the network interface quits working somehow. 
    When this occurs, the unit still thinks that the interface is configured, and everything seems OK, I just cannot connect. Obviously, this causes my iSCSI initiators to die, and the VM hosted crashes hard. At that point, I have to restart the storage unit, and then reconnect my initiators, and then bring everything back online.
    I've updated the firmware to the latest, but it wasn't that far out of date. I've found an article titled "Network storage device is not assigned an IP address" in the knowledgebase that points ot a problem with the software in the 4.0.2 series, and I was at 4.0.6, and am now current in 4.0.8. I am testing the process again, but wanted to check with the community to see if anyone has experienced anything similar and/or could offer some idea of why this interface quits working.
    For what it's worth, the other units I have worked with were all in the 3.x series of software.
    Thanks for any help/information anyone can provide.
    Solved!
    Go to Solution.

    Hi chloeroxymax,
    Do you have discovery enabled?
    If not, check the box for "Enable discovery with iSNS" under the iSCSI settings and select "Use local iSNS server".
    Then, on your iSCSI Initiator, go to the Discovery tab. Click "Add Server" under iSNS servers and enter the IP address of the NAS.
    The device should show up under the Targets tab (you may have to click the refresh button)
    On your other NAS devices, go to the iSCSI settings page and select "Enable discovery with iSNS" but select "Use external iSNS server" and type in the IP address of the ix4-300d NAS.
    This may help things run smoothly. If the device is still disconnecting, I would recommend contacting technical support since this is a new device and you are covered by the warranty for support.
    Have questions and need answers?
    Search the database for answers to FAQ's, software/driver downloads, tutorials, news, features and more!
    LenovoEMC Support & Downloads
    LenovoEMC North America Support Contact Page

  • I need confirmation, please help me! (about adding new hdd on my ix4-300d)

    Hello,
    I buy recently a Lenovo ix4-300d, I have installed one hdd seagate 2To (ST2000VN000).
    I saved many documents on it..
    Today I want to install 2 others hdd WD 1To (WD10EZEX).
    After reboot a message tells me I need to erase all data on the news disks before I can use it, so I confirm, all seems ok.. After that a message appear on the left "2 disks unused".
    Now (step 3 page74 on the .pdf guide) I need to check the box "add drives to storage system" and click confirm to activate the news disks, so I do, but I have this message:
    "Vous devez supprimer les données existantes pour pouvoir modifier la configuration du disque.
    Cochez cette case pour continuer."
    (in english "You must erase existing data for change the disk configuration" or something like that)
     I don't want to loose all the data on my first hdd already in use.. ..and the 2 others news disks are empty.
    So, there is my question:
    if I check the box and click continue what "existing data" will be erase??
    existing data on all hdd?? Or just on the new one??
    nb: Sorry for "my english" but there is no french section in the forum, and the assistance don't answer me by email, and on the phone there is an answerphone tells me "for help if you don't have the error number code, you must go on the forum, bye.."  .. ..  I hope my question is understandable. 
    Thanks 

    Hello tictictac
    Sorry that you experienced data loss, however it was preventable if a backup had been made as recommended.   
    From the screen shot you sent it looks like the drives were already added to the existing array after the first drive overwrite request.  With the array being made up of mixed disk models and none of the disks showing any green stipes indicating overwrite selection,  I can not say for certain what caused all the disks to be wiped.  I suspect that is was taken as a RAID change and all disks were wiped from there. 
    For future reference please check the device support page to see the guides, FAQ's, and download the full user manual( in French here ) and check with LenovoEMC support in your region.  The Europe support region has several languages available to choose from including the France number +33 17048 0388.  The full list of Europe numbers can be found here.
    LenovoEMC Contact Information is region specific. Please select the correct link then access the Contact Us at the top right:
    US and Canada: https://lenovo-na-en.custhelp.com/
    Latin America and Mexico: https://lenovo-la-es.custhelp.com/
    EU: https://lenovo-eu-en.custhelp.com/
    India/Asia Pacific: https://lenovo-ap-en.custhelp.com/
    http://support.lenovoemc.com/

  • Cannot update to Firmware version 4.1.108.32627 on ix4-300d

    Just bought an ix4-300d with 4-3Tb drives.  I cannot update Firmware to the latest version.  After uploading to the NAS, when I click 'Apply' or 'Apply all pending updates", I see a message that says "The update file is being decompressed".  After several seconds, I then receive dialog box that says, "Error – The software could not be updated."
    Any ideas what the issue could be?  Are there any log files to look at?
    Current Version:         4.1.102.29716
    Upgrade to:                 4.1.108.32627

    Hello dcsantis
    Check the event log for any abnormal storage alerts such as degraded storage, recoverable errors, missing drive alerts, etc.  Those sort of alerts could contribute to the firmware update issue.
    Some basic steps to try for the issue:
    Re-download the update file again and check the md5 checksum from the download page.  If the checksum fails, try downloading from a different browser or computer and check it again.
    Try uploading and applying the file using a different browser or computer.
    Try re-seating all disks with the unit off, then try uploading and applying the update file again.
    Try swapping disks 1 and 4 to opposite bays, then try uploading and applying the file again after booting.
    LenovoEMC support should be contacted to create an incident if the above steps do not work.
    LenovoEMC Contact Information is region specific. Please select the correct link then access the Contact Us at the top right:
    US and Canada: https://lenovo-na-en.custhelp.com/
    Latin America and Mexico: https://lenovo-la-es.custhelp.com/
    EU: https://lenovo-eu-en.custhelp.com/
    India/Asia Pacific: https://lenovo-ap-en.custhelp.com/
    http://support.lenovoemc.com/

  • IX4-300d I/O error, check file system, now stuck at software restart

    Good morning!
    I have a brand new IX4-300d. Was uploading files with sftp yesterday, which kept giving me errors, so I enable support access and checked the logs while uploading. Got a lot of:
    end_request: I/O error, dev sde, sector 16384
    sd 16:0:0:0: [sde] Unhandled error code
    sd 16:0:0:0: [sde]  Result: hostbyte=0x07 driverbyte=0x00
    sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 01 00
    end_request: I/O error, dev sde, sector 0
    sd 16:0:0:0: [sde] Unhandled error code
    sd 16:0:0:0: [sde]  Result: hostbyte=0x07 driverbyte=0x00
    sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 3a 38 17 c0 00 00 01 00
    end_request: I/O error, dev sde, sector 7814036992
    sd 16:0:0:0: [sde] Unhandled error code
    sd 16:0:0:0: [sde]  Result: hostbyte=0x07 driverbyte=0x00
    sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 3a 38 17 d3 00 00 01 00
    end_request: I/O error, dev sde, sector 7814037144
    sd 16:0:0:0: [sde] Unhandled error code
    sd 16:0:0:0: [sde]  Result: hostbyte=0x07 driverbyte=0x00
    sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 01 00
    end_request: I/O error, dev sde, sector 0
    sd 16:0:0:0: [sde] Unhandled error code
    sd 16:0:0:0: [sde]  Result: hostbyte=0x07 driverbyte=0x00
    sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 00 01 00 00 01 00
    end_request: I/O error, dev sde, sector 8
    sd 16:0:0:0: [sde] Unhandled error code
    sd 16:0:0:0: [sde]  Result: hostbyte=0x07 driverbyte=0x00
    sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 01 00
    end_request: I/O error, dev sde, sector 0
    sd 16:0:0:0: [sde] Unhandled error code
    sd 16:0:0:0: [sde]  Result: hostbyte=0x07 driverbyte=0x00
    sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 3a 38 17 c0 00 00 01 00
    end_request: I/O error, dev sde, sector 7814036992
    sd 16:0:0:0: [sde] Unhandled error code
    sd 16:0:0:0: [sde]  Result: hostbyte=0x07 driverbyte=0x00
    sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 3a 38 17 d3 00 00 01 00
    end_request: I/O error, dev sde, sector 7814037144
    So I requested a offline file system check from diagnose page. That was as off now 23 hours ago, from what I can see, the fs check did not take long, but has been stuck at DEvice software restarting for at least 22 hourse. I use less then 200Gig on it, setup as raid 10.
    This device is not 1 month old. I had it freeze on my once already, not while restarting, just froze up. So that is the second time.
    Status in the web console said all is fine, I had to go in through ssh and look at the os logs to find out what is happening.
    What should I do?
    Solved!
    Go to Solution.

    Hello CollegeMathieu
    Please contact support using the below support links so we can have the issue properly diagnosed.  There is a good chance that the unit may have shipped with a defective drive (if it is a diskless model one of your hard disks may be defective).  This could be causing the strange firmware behavior. 
    A couple of things to try :
    -power down the unit and re-seat all disks then try booting again to see if there is any change.
    -If the above does not work, try swapping disk 1 with any of the other hard disks while powered off and then try booting again.
    LenovoEMC Contact Information is region specific. Please select the correct link then access the Contact Us at the top right:
    US and Canada: https://lenovo-na-en.custhelp.com/
    Latin America and Mexico: https://lenovo-la-es.custhelp.com/
    EU: https://lenovo-eu-en.custhelp.com/
    India/Asia Pacific: https://lenovo-ap-en.custhelp.com/
    http://support.lenovoemc.com/

  • OVS servers restart when iSCSI target restarts

    Long story short, I've been working on my new lab at home off and on.  Tonight I was working on my lab to get to the point where I would have OVMM as a virtual machine as the dedicated host I have for temporary measures only has two gigs of ram vs the recommended 8 gigs of ram.
    More to the point:  I was working on the storage portion of my setup and I got my iSCSI target discovered (FreeNAS 9.3) and I was able to build my cluster of OVSs.  I noticed earlier that my FreeNAS server had some pending updates and I figured it would be a good idea to perform these updates before I started using the iSCSI storage for active virtual machines.  Naturally, when the updates are done on my FreeNAS server, it reboots.
    What I don't understand is why both of my OVSs restarted at the same time after the FreeNAS server went down for a reboot.  Was there a hidden gotcha?  Did I overlook something in the documentation?
    A side effect of the unexpected reboot is the fact that my OVS(2) did not come back online with OVMM and I could not ping my management interface for that OVS.  I did several Google searches and tried some manual up/downs of the interfaces and tried one effort to manually configure bond0 to an IP address to try and get some sort of response.  Needless to say, none of those were good ideas and didn't help.  Therefore, I'm re-installing OVS on server 2 now.
    If anyone has any ideas as to how I could have fixed OVS(2) I'm more than willing to take notes in case this happens again.
    Thank you for any and all help,
    Brendan
    P.S. If this has any influence with my situation, I am running LACP bonds and all IP addresses are configured on the VLAN interfaces.  I have not had any issues configuring my switch and with the exception of OVS(2) not wanting to reply after the unexpected restart I had everything working.  An added gotcha is that the storage VLAN interface on OVS(2) continued to reply after the restart.

    Hi Brendan,
    the situation you encountered is expected for a single-headed iSCSI target. If you present OVM with a LUN - regardless if it's iSCSI or FC, OVM creates an OCFS2 volume on it, when you choose that LUN to be used as a storage repository. This is, since OCFS2 is a cluster-aware file system and thus is the only supported fs to use for a cluster setup. Now, although OVFS2 is really easy to setup - compared to other cluster file systems - it has some mechanics that will cause your nodes to fence (or reboot) in case the node looses "contact" with the OCFS2. Each node writes little keep-alive fragments onto the OCSF2 and if you reboot your iSCSI target, then this will cease and OCFS2 will fence itself, hoping for some minor glitch that may be gone after a reboot.
    There are a couple of ways to achieve this with iSCSI, but their resp. setup is not easy, and the hoops to jump through are probably to many for a lab setup. E.g. I am running a two RAC nodes as iSCST targets, which in turn do have high-redundancy disk setup behind them, consiting of 3 seperate storage servers. So, in my setup I am able to survive:
    - two storage node failures
    - one RAC node failure (which provides the iSCSI target for my OVS)
    Regarding your OVS2, as you have already re-installed OVS2, there will be now way, to tell, what went wrong with it, as you'd need access to the console to poke around a bit, while OVS2 is in that situation, where it doesn't respond to pings on it's management interface.
    Cheers,
    budy

  • IX4-300D frozen at 69% during filesystem repair

    My Lenovo/Iomega IX4-300D had the filesystem error, so I did the offline repair, but it's been stuck all night att 69%, and neither web nor SSH nor the lcd on the front respond to anything...
    I obviously have no choice than restarting the thing, but I *am* curious if others have seen the same, and whether a cause is known?
    Solved!
    Go to Solution.

    NM! Looking at DMESG gives me the info I need:
    sd 0:0:0:0: [sda] Unhandled sense code
    sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
    sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
    sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
    sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 19 f3 a8 00 00 04 00 00
    end_request: I/O error, dev sda, sector 435399328
    md/raid:md1: read error not correctable (sector 393388704 on sda2).
    md/raid:md1: Disk failure on sda2, disabling device.
    md/raid:md1: read error not correctable (sector 393388712 on sda2).
    md/raid:md1: read error not correctable (sector 393388720 on sda2).
    md/raid:md1: read error not correctable (sector 393388728 on sda2).
    md/raid:md1: read error not correctable (sector 393388736 on sda2).
    md/raid:md1: read error not correctable (sector 393388744 on sda2).
    md/raid:md1: read error not correctable (sector 393388752 on sda2).
    md/raid:md1: read error not correctable (sector 393388760 on sda2).
    md/raid:md1: read error not correctable (sector 393388768 on sda2).
    sd 0:0:0:0: [sda] Unhandled sense code
    sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
    sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
    sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
    sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 19 f3 a0 00 00 04 00 00
    end_request: I/O error, dev sda, sector 435396608
    disk 0, o:0, dev:sda2
    disk 1, o:1, dev:sdb2
    disk 2, o:1, dev:sdc2
    disk 3, o:1, dev:sdd2
    disk 1, o:1, dev:sdb2
    disk 2, o:1, dev:sdc2
    disk 3, o:1, dev:sdd2
    md: unbind<sda2>
    md: export_rdev(sda2)
    md: bind<sda2>
    (Taken from DMESG just after I saw md recovery start over!)

  • ISCSI target performance

    Hello!
    There're a lot of iSCSI targets with one or two 1Gbps nics on market today but I have serious doubts about their performance: 1Gbps(or 2Gbps) compared to 6 Gbps in raw SAS/SATA make me think their network speed will be the bottleneck in any setup (for example,
    two node cluster with an iscsi target). Can anybody please tell me what performance issues may arise, for example, if I place a VM with SQL server on such target?
    Thank you in advance,
    Michael

    "To have fault tolerance you have to have either dual hardware controllers (storage virtualization
    creating LU from ultiple physical spindles) or use distributed software controllers (DRBD, HAST, Clustered Storage Spaces etc). " - I don't agree: fault tolerance can be provided by the single RAID 5 controller - of cause it's better to have two controllers
    but it's just one more level of fault tolerance. Many (or even all of them) iSCSI targets have RAID controllers that allow them to be fault tolerant and I can't understand why this is not the case with DAS: "If RAID capable, HBAs must be in non-RAID
    mode with all RAID functionality disabled".
    To make a long story short I'd like to know why I can use RAID with iSCSI and can't with DAS/SAS.
    Regards,
    Michael
    Because Clustered Storage Spaces don't handle LU reservations in software (unlike other Software Defined Storage solutions like VSAN for example) and rely on a hardware mechanism inside single dual pot SAS drive for that. So either you use dumb SAS controllers
    providing raw access to SAS spindles or use Clustered RAID controller who handle distributed lock on it's own (LSI Syncro for example) and in this case you *CAN* RAID disks and them pass them to CSS.
    StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Maybe you are looking for

  • Organizer not showing photos in thumbnails...only getting grey square w/hour glass

    The organizer is only showing a blank grey square as the thumbnail and not the actual photo.  However, once I click on the thumbnail, the photo pops up and is veiwable.  This is a problem that just recently started.  All of my other photos, in other

  • Transfering files between macs

    I am trying to transfer files between my G4 powerbook and new macbook. For some reason the powerbook will not reboot if I hold the "T" down after I clicked restart. Any Suggestions?

  • Update MDM Import Map

    Hello... I am a PI consultant who inherited MDM recently. MDM 5.5, SP06 My issue is that I have an existing map that works fine, but the source schema is changing to add a few new fields.  I need to map the new fields to my existing catalog repositor

  • No space in the volume db not starting

    Version : 10.2.0.3 Os : Linux rhl 4 Problem : the volume /u02 is 100% full and db is down. The volume consists of dbf, log, ctl files other than that no other files in the volume to create space. To rename the data files to another volume I need to p

  • Preloader Problem in Flash MX

    Ok, welcome back again... I must first say... this site is perfect... Solving my day-2-day Flash mess ups! Ahh, but let us begin! I've just created a site (more of an Intro to the site), using Flash and I also created a preloader because of the long