Reference Dell MD3000 virtual disk

Similar Questions

• Reference Dell MD3220 virtual disk - hot spare in use

  We have a Dell MD3220.  one of the hard drives was taken out by an end-user trying to exchange a defective disc. Then after that the good player has replaced the old drive was placed back into the appropriate slot. Now we have a hot spare (enclosure 0, slot 23) in lieu of an another hot spare (attachment 2, slot 22). The hot spare that is subbed for has been replaced by two new hard drives now and the hot spare in use has still not disappeared. any suggestions on what to do next?

  Virtual disk - hot spare in use

  Storage array: MD3220
  Disk group: 2
    Physical disk failure in the: attachment 2, slot 22
       Action (deletion) enabled service:  NO. 
         LED of action on service component:  NO.
    Replaced with a physical disk to: enclosure 0, slot 23
    Virtual disks: 3
       RAID level: 5
       Status:  Gradient

  Hello, GalaxyTechService.

  It is perhaps not as complicated as it may seem, in fact. There is a wizard that you can use to return the disk to the raid set. Right-click the affected virtual disk and select 'Replace physical disk' and use the wizard that opens.

  In the upper area will be "missing disks", and in the lower field will be options available to replace them.

  Then just follow the steps.

  Let me know how it goes.

• Max MD3000 virtual disk size

  Can how big I grow a virtual disk?  As above, I have two servers Dell PE in a cluster failover with Windows 2008R2 Ent. The MD300 contains two Virtual disks 1 x 50 GB of disk as a cluster quorum and 1 x 4TB which holds virtual machines. I would add 2 TB for the largest virtual disk; that would be appropriate?

  The only limit to the size of the virtual disk on a series of Dell's MD3k is the maximum number of physical drives in a single group. For raid 5, it's 30, RAID 10, is 44 and for raid 0 is 45.

  When you configure a cluster, I usually use a Quorum GB 2. If it is an installation of hyper-v I then use 2 disks or more virtual to spread the i/o load. If not for hyper-v, then the structure of the virtual disk depends on the needs of the application and storage.

• Reference Dell HDS - recommended VMware virtual disk - drives provided - basic and dynamic thin and thick.

  Can someone point me to the literature on best practices for guest disc formats?

  I know all the Compellent thin-provisions. However, in VMware 5.5, when you set up a virtual disk in the comments you have several choices:

  • Lazy provisioned to zero thickness
  • Eager provisioned to zero thickness
  • Provision of thin

  And then, at the level of the OS, you have the choice of:

  • Base
  • Dynamics

  I would like a pointer to the technical document explaining the advantages/disadvantages of each choice and recommended best practices.

  Kind regards

  Kath

  I would like to either thin or thick lazy to zero.  The two will take the same amount of data on the HDS.  The main decision is where you want to manage your storage space?  If dilute you on thin you need to make sure that you make no provision in both places.  If you have thick lazy to zero, then you can only on commissioning on one side.

  Say that I always thin on thin.  Recovery of the space at the level of the virtual computer is not officially supported immediately, but maybe someday.

  In a virtualized environment, always keep it simple.  There is no dynamic performance with virtualization

• Reference Dell R610 RAID, virtual disk more problems of 1800 GB

  Hello community,

  I was frustrated by my attempt at installing VSphere 4.0 Update 2 (or 1) on a virtual disk on a SAS Perc 6, which is more than 1 800 GB in size and I was wondering if any of you have had similar experiences and how you have handled THIS.

  Unfortunately this system will use internal to the storage drive as it will be in a remote location.

  Any help is greatly appreciated

  Thank you

  Brian Wing

  Calix

  Break your table into smaller pieces. ESX requires a minimum of about 10 GB, even if you can make bigger it. ESXi requires only 1 GB. Data warehouses may not be less than 2 TB. You may be able to use virtual disks raid based to break the table.

• MD3000 cannot change virtual disk ownership / preffered path - ERROR 29

  Current configuration

  PowerVault MD3000 (deleted by the moderator) - attached to two servers PowerEdge R610 using Dell SAS 5/e card in each r610. The R610s act as a host ESX VMWare ESXi 5.5.0

  We have created multiple LUNS on the storage array and noticed that traffice all happening through a RAID controller or another module (and it seems to me not change without prompting when you look at the storage Bay). I turned off a two different virtual machines to try to change the path and had an error with a certain delay - I stuck this error below. I also tried to redistribute virtual disks tab the MDSM software nothing works support.

  By reading, it seems that the LUN should be attributed to a particular raid controller before all I / 0, but I still feel like're missing us something as to why we cannot distribute the traffic properly.

  According to some records for a MD3200 -.

  "If the host has a path of data unique to the MD, the virtual disk storage array.
  must be owned by the controller to which the host is connected.
  That's what we're trying to accomplish. I don't know if the hosts are to be physically detached from the SAN, or if there is a bit of software to fail us.
  Thank you in advance! If I failed to provide all the details, please let me know and I'll try to gather the information.
  Here's the error output:

  OPERATING ENVIRONMENT DATA

  Name of the client system: FLMGMT01
  Client OS: Windows Server 2008 R2

  Application version: 03.35.G6.88
  Storage management of version table: 03.35.G6.88
  Name of storage array: VAB-NAS-01
  Firmware version: 07.35.39.64
  Management class: devmgr.v1035api01.Manager

  **************************************************

  DATA ERROR

  Command sent to the RAID controller module to the location: 0
  Host name: 192.168.19.233
  IP address: 192.168.19.233

  Return code: error 29 - this operation cannot complete because there was a failure of authentication of security on a parameter in the command sent to the RAID controller module.

  Try the operation again. If this message persists, contact your Technical Support representative.
  Operation when the error occurred: PROC_assignVolumeOwnership
  Timestamp: August 25, 2014 16:18:59

  DATA BATTERY

  devmgr.v1035api01.Sam.JAL.ManagementOperationFailedException:
  at devmgr.v1035api01.sam.jal.SYMbolClient.dispatchOperation (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.issueCommand (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommandCommon (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommand (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.assignVolumeOwnership (unknown Source)
  at devmgr.v1035api01.sam.configuration.controller.ChangeControllerOwnershipDialogPanel.performCommitAction (unknown Source)
  to devmgr.v1035api01.shared.wizard.DialogPanel$ NotifyBackgroundTaskAdapter.performOp (unknown Source)
  at devmgr.v1035api01.shared.AbstractTaskAdapter.run (unknown Source)

  THREAD DATA

  Thread [reference Manager 10, System]
  Thread [finalizer, 8, System]
  Thread [dispatcher Signal, 9, System]
  Thread [attach auditor, 5, System]
  Thread [Java2D grinder, 10, System]
  Thread [TimerQueue, 5, System]
  Thread [Swing-Shell, 6, System]
  Thread [AWT-closure, 5, main]
  Thread [AWT-Windows, 6, main]
  Thread [EventQueueMonitor-ComponentEvtDispatch, 5, main]
  Thread [Thread-3, 5, main]
  Thread [AWT-EventQueue-0, 6, main]
  Thread [DestroyJavaVM, 5, main]
  Thread [SwingWorker-pool-2-wire-1, 5, main]
  Thread [ChangeDetector, 6, main]
  Thread [PreferenceStoreChangeDetector, 6, main]
  Thread [LogMsgThread, 6, main]
  Thread [Np_Link_Monitor0, 6, main]
  Thread [DMVGarbageCollectorThread, 6, main]
  Thread [RecoveryProfile-27, 6, main]
  Thread [NEA-28, 6, main]
  Thread [RecoveryProfile-30, 6, main]
  Thread [NEA-31, 6, main]
  Thread [Timer 0, 6, main]
  Thread [RecoveryProfile-35, 6, main]
  Thread [NEA-36, 6, main]
  Thread [RecoveryProfile-38, 6, main]
  Thread [NEA-39, 6, main]
  Thread [Timer 1, 6, main]
  Thread [Timer 2, 6, main]
  Thread [Timer-3 6, main]

  
  Thread [RecoveryProfile-48, 6, main]
  Thread [NEA-49, 6, main]
  Thread [Timer-4 6, main]
  Thread [RecoveryProfile-53, 6, main]
  Thread [NEA-54, 6, main]
  Thread [Timer-5 6, main]
  Thread [SwingWorker-pool-2-wire-2, 5, main]
  Thread [RecoveryProfile-69, 6, main]
  Thread [NEA-70, 6, main]
  Thread [Timer-14, 6, main]
  Thread [Timer-91, 6, main]
  Thread [host 2.3, principal of the Image]

  Hello MrRedPants,

  Since you are using a configuration not redundant you will have problems trying to modify the paths between the controllers since the two hosts have only a single connection to the MD3000.  What you could do if possible is to get 2 more SAS cables & connect ports second on the MD to RAID opposite that the host is currently connected to.

  Now, if this isn't an option so that you can make is to have 2 disk groups and assign the virtual disks / LUNS that are connected to each host in their own disk group.  If you go to each host their own groups of disks, then you will need to stop the e/s as you move the Ramdisk to the new group of disks so that you want to discard any data loss.

  Please let us know if you have any other questions.

• MD1000 attached to MD3000. Virtual disk not on the preferred path

  Hello

  I have a MD3000i box connected to 2 boxes of MD1000, these are connected to a Dell Power Vault Storage server 2003 running.

  Last night I connected the 2nd MD1000 and added in 25 TB of drives worth. I had initially hurt mapping the new virtual disk after 20 minutes or so, I noticed that I had shot the Ethernet cable plugged into the Module Raid 0 by mistake. I plugged it back in and was able to map the drive and started the initialization of disks.

  I came this morning to check how everything is done and found an error on the table. Disk not on favorite virtual path, preferred owner: at location 0 RAID Controller Module. Current owner: Module to slot 1 RAID controller. Group MD1000_2 of disc. Ramdisk: Virtual4.

  Now, it seems that influence the new virtual disk that I created. I checked the path virtual disk property and all the other virtual disks are using path 1 and try that I created to use channel 0.

  The virtual disk seems to be working for the moment it is detectable and to initialize itself in the area of operations of MDSM. I'm under pressure to get the space of storage as soon as possible, so I can't really afford to have to blow the virtual disk and restart the initialization. I'm hoping a simple reboot of the storage array will cure the problem, but I guess I can't do so until the end of the initialization of the disks. I could also remap the path to the virtual disk, but I saw online that it does not solve the problem, and I always have to wait until the initialization is complete.

  Any help would be appreciated.

  Hello

  I deleted the disk group and created a new one that even once, did not help even after that I tried to change the path. I deleted again and created a new and then changed to RAID 1 controller quickly while he was still on the controller 0 (before it came with the failure of the path) as the preferred path that has cleared the error. There must be a mistake with the controller or the wiring to it.

  Thank you

• Reference Dell poweredge r530 - increase the disk space

  Hello

  We currently have a Dell Server poweredge R530, with installed 5 hot swappable drives with RAID 5 configured. I need to increase disk space for our virtual machines, bought an x 2 extra 1.2 TB SAS drives to install. What is the correct process to add 2 new readers to the table and increase the space available in the 2012 R2 windows server? Could someone sanity check process below please:

  1. install the 2 new drives while the server is powered and operating normally. (What I have to install 1 player and wait a while, or two disks can be installed directly after the other?)

  2. go in dell iDRAC and confirm the visibility of 2 new readers.

  3. wait until the readers successfully have been added to the State through iDRAC Tracker

  4. go in the management of the storage within the 2012 R2 server to allocate new space for the virtual machine partitions.

  Is more correct? It feels like I'm missing an essential step, it cannot be that simple that it allocate the additional storage space on a live production server?

  Any advice appreciated

  Thank you

  1. the two drives can be added at the same time.

  2 iDRAC is not the best way to do it. Unless this is your only access to the server, use OMSA leave within the OS.

  3. the process is not automatic. Once readers show up in a State of PREPARATION, you will need to go to OMSA, PERC, storage, virtual disks and select Reconfigure in the drop-down list of tasks available for RAID 5. (In fact make the statement reconfigures / expansion was the 'crucial step' you left on your list of ;).))

  4. Yes.

  Are your 1.2 to existing disks SAS drives?

• Dell virtual disk are larger. You want to increase the size of the data store.

  Hello

  I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

  I tried to follow the article here that explains how to do this via the CLI.

  Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

  Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

  I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

  ---

  I use that as a guide:

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461

  
  

  1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

  This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)

  
  

  2. open a console to the ESXi host.

  Pretty simple.

  
  

  3. get the DeviceID for the data store to change.

  ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

  System file VMFS-5, 60 extending on 1 partition.

  File system label (if applicable): datastore1

  Mode: public

  Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

  UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

  Partitions split (on 'lvm'):

  NAA.6c81f660ef0d23001ad809071096d28a:4

  
  

  A couple of things to note:

  a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

  b. the number of Partition on the disk is: 4 ' [...]: 4 "»

  c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

  4. Enter the amount of disk space available on the data store.

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1

  
  

  5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  ~ #

  
  

  According to the table in article KB

  4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

  | |        |          |   |

  | |        |          |   \---attribut

  | |        |          \---type

  | |        \---se finishing sector

  | \---a starting from sector

  partition \---Numero

  
  

  Also note how the number of section start the old end sector number is + 1.

  
  

  6 identify the partitions that need to be resized and the size of the space to use.

  We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.

  
  

  7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

  ESXi 5.x has a command to do this:

  ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

  1 5854986239

  This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

  13711360 - 5854986239 (i.e. the end of the disc)

  
  

  8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

  Using the above information, our command is:

  resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239

  
  

  9 step 8, the partedUtil command can report the warning:

  He did not. Displacement.

  
  

  10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.

  
  

  11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

  Fact.

  
  

  12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

  vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.

  
  

  It did not work. I got an error:

  / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

  23001ad809071096d28a:4 ".

  Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information

  
  

  Also the partition was very different to what I asked:

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 1560018942 251 0

  
  

  I fixed it by running these commands:

  ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

  ~ # vmkfstools v

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  Update:

  Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

  Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

• PowerEdge 2950 advanced settings recommended virtual disk group

  Hey guys, I was hoping that someone out there has had some information about the nature best practices or the best settings for these two configurations of a Dell 2950 with PERC 5 controller / i.

  Senario 1

  Reference Dell 2950 Windows Server 2003 Enterprise Edition 32-BIT

  RAID 5 (5 TB) hardware RAID & Windows dynamic disk Configuration

  PERC 5 / i with battery

  Group of virtual disk current avancΘs

  Virtual disk 0 - Adaptive Read Ahead and Write Back

  Virtual disk 1 - Adaptive Read Ahead and Write Back

  Senario 2

  Reference Dell 2950 Windows Server 2003 Enterprise Edition 32-BIT

  RAID 5 (5 TB) hardware RAID & Windows dynamic disk Configuration

  PERC 5 / i with battery

  Group of virtual disk current avancΘs

  Virtual disk 0 - Adaptive Read Ahead & direct writing

  Virtual disk 1 - Adaptive Read Ahead & direct writing

  The second server now has a battery that has failed and we are on the way. I want to add that I just found out that a bad or dead battery kills performance on the server reading and the writing speed. After replacing the battery on the first server, I saw performance increase by at least 300% if it is longer. So this lead me to read a lot of posts by others, but I couldn't find a solid peg that indicates what should be the best configuration. So my questions are... What is the best configuration for Virtual Disk Group advanced settings for MY servers above WITH a controller battery? Finally, what happens if I didn't use the battery which is recommended then? Is it better to use a battery or be without one? Bottom line is that I best performance of reading and writing, thank you to you all!

  300% is too much of a performance increase to attribute entirely to the write cache is enabled, even if it makes a significant difference.  When the battery goes bad, the controller disables the write cache, and it is the source of the performance difference.  Unless you have a specific reason to disable the cache (and I see no good reason), it must be enabled.  You can not force the controller to use memory cache without battery, not to mention that it's dangerous for your data to use the cache without battery.

  "Bottom line is that I the highest performance for reading and writing, thank you to you all!

  Bottom line... turn write cache (write back) and replace the batteries when needed (which should not be often).

• Reference Dell MD3620F

  Hi we have a MD3620f storage array, we have 12 hard drives in the system with two different Raid configurations for the disks.

  I would like to add a few additional hard drives in the system, I can do this when the system is powered and once added can I add them to one of the additional Raid 5 arrays without causing problems to the data already contained on existing drives?

  Thank you

  Andy

  Hello Andy,

  Yes, you can add drives when the system is powered. You can also add new space to your current virtual disk with the direct system as well. Now, I would recommend that you get a backup copy of your data in case where something bad, but in the majority of cases nothing happens no. Also, when you add the new space to any virtual disk it is a process very slow for the MD finish due to the expansion of the virtual disk is a low priority, I have seen in some cases where it may take a few days to sometimes several weeks or months, so I just wanted you to be aware of this before you start. Here is a link to the Administrator's guide, and if you look at page 91, he explains how to add the free space on your virtual drive. FTP://FTP.Dell.com/manuals/common/PowerVault-md3200_Administrator%20Guide_en-us.PDF

  Please let us know if you have any other questions.

• Utility RAIDCFG to slow initialize virtual disks

  I use RAIDCFG. EXE from DTK to configure a Raid of H700 on a R910 controller.

  I would like to start slow initialization of a virtual disk. Documentation, the command is:

  raidcfg - vd - c = X - vd = Y - ac = sli

  I get a message of successful immediately command.

  How do I know what the State of the initialization?

  Thanks for any help.

  For more information on init, slow and fast, please visit NOTE from the ADMIN: broken link has been removed from this post by Dell >

• Problem creating virtual disk MD3600i

  I add a MD3600i (with extension MD1200) to a Cluster of servers Windows 2012 new file.  I have connected and configured to the point table to create virtual disks.  When I try to create a disc, the 'Work' spinner appears, then disappears almost instantly.  The wizard never loads.

  -J' tried MDSM from versions of resource disc, 4, 5 and 6 - no change.

  -J' removed and added the table several times.

  -J' updated the firmware newest controller.

  -J' tried both In-Band and Out-of-Band management connections.

  -J' tried with two pools and groups.

  -Out-of-band management stations have been Windows 7 and 8.1

  When running create it a Wizard of the pool, I can create virtual disks even size at the end of the process, but I can't create the readers in the free space remaining (more than enough available for a player)...  I need to be able to create readers as needed, please help!

  I spoke with Dell Support, and the solution was to delete and re-create the host in MDSM.

• Reference Dell VRTX Drive Configuration

  I'm trying to configure a Dell VRTX to 3 blades with R2 2012 Windows failover

  I followed the instructions from Dell to create a Quorum disk (RAID 1) and a shared disk of the cluster (CSV) - Raid 50.

  The issue is, in each Windows host, Disk Manager sees each virtual disk twice.

  What did I miss?

  

  I answered my own question.

  The Microsoft MPIO's feature must be installed as well

• Reference Dell E6420 randomly not SSD detection at startup

  Specifications of the computer:

  Dell Latitude E6420, Intel Core i5 2520 M, 2 x 4 GB = 8 GB of RAM, Nvidia NVS 4200 M, 250GB HDD, Win 7 Pro 64, Bios A23

  The value of operation SATA AHCI and not quick start. I have 3 of these computers. They are all out of warranty.

  I replaced the original 7mm Hitachi 250 GB for the Intel 535 240 GB SSD HARD drive.

  I used Acronis True Image 2016 to clone the hard disk SSD. Cloning process is very much like on any other computer.

  The problem is that each cold 4 or 5 boots the computer cannot find the SSD drive. Restarting the computer solves the problem of that time. I have to find a solution. I want to sell them with a SSD and not with a HARD drive.

  I tried the things:

  Update the Bios of the A14 to A23.

  Put a spacer of 2mm on the SSD and of course the resettlement of the SSD.

  Exchange for another Intel 535 120 and 240 GB.

  Clean install of windows I knew was a waste of time because it does not affect the BIOS does not detect not things.

  Googling the problem for hours.

  Call dell?

  Use another brand of SSD? He probobly won't make any difference to look at other threads.

  Use a HARD drive? Last resort. I can't stand slow hard disks regularly.

  Reference Dell E6420 seems to work with a Samsung 850 Evo 250 GB instead of the Intel 535 very well. Tested over a period of 3 months with no problems. Threw 535 readers intel in the desktop instead.