![]() Nobody on the entire internet had this solve for my dell. ![]() This was a serious pain in the bum as some of the steps were obviously omitted. "Dell diagnostic deployment package" follow instructions to create bootable usb using this program. Reflashing my bios without a hard drive was next to impossible but with 5 days work with no sleep and 1000 restarts, I finally hacked my bios via dddpm boot usb by dropping the new downloaded bios exe directly into the dddpm boot files. Please advise computer users to update their bios, before their old hardrive dies! This is the main issue. ![]() So I had my dell computer with no working hard drive to boot from, and my ssd, although perfectly formatted on another computer via usb sata using disk management, it was not being seen at all when trying to install windows 7 or 10 with disk or iso boot usb. I know the drives are OK because I extensively tested them outside of this configuration.įor my dell latitude e6530, my win 10 hdd died and I was not able to clone due to 270 bad sectors. This happens for any drive I connect through SATA/eSATA on my XPS 8100. PS - same thing happens when using the software from Seagate or Western Digital on the INTERNAL SATA drive - SMART test fails because it cannot read it from the drive. Either there is something odd about the XPS eSATA connection or I have some malfunction. ![]() I find it weird that sw cannot seem to access the drive via eSATA for the SMART test even though I am able to perform other operations like browse and move files from the connected drives. I tried two docks, various cables and various drives and diagnostication sw - SMART short test always shows as failed but it is because somehow the sw cannot read the SMART data from the drives. On a separate topic, since we share the same underlying computer guts, I wonder if you have experienced the same oddity when hooking up external eSATA docks. thought about getting a controller card supporting SATAIII and RAID 1 to stripe and use for some video editing but I think the PC will still have bottlenecks so may just rely on a single fast drive for video. Planning on also getting a SATA III controller card so at least my data drives can get 6Gb speed. Planning on getting Samsung 840 Pro, top of the line (better than 840 EVO) and maybe overkill without SATAIII but maybe worthwhile given the higher supposed reliability and warranty. Correct? Any further advice before I start doing the same? So: SDD as OS drive, kept data using cloning sw (assumed provided by Samsung), no OS reinstall required, no need to get ACHI (as our XPS 8100 does not support) and all working well and you're getting faster PC. Wildly, so found this post with what seems to be theway you end up moving ahead. And adding a SATA3 PCIe card will not magically make an AHCI setting appear in BIOS. Also, no need to buy a SATA3 card as you wont likely see much of a boost from the on-board SATA2 (3gb/s) interface in normal use. So there is no fault or issue to worry about by not having AHCI setting in BIOS and really you don't need to force any driver to be used via registry settings as some seem to like to do. The friendly name shown for the SSD/HDD/ODD includes "SCSI disk device" which is due to the version of Intel RST drivers that i am using, it seems that pre version 11.4 the friendly name was a little more logical and didn't reference ATA or SCSI in the string. Hereis what mine looks like.Īs you can see, my Intel SSD is listed as "ATA Intel SSDSC2CW12 SCSI Disk device" while my 2x HDD in RAID 1 is listed as "Intel Raid 1 Volume SCSI Disk Device". You can see where your HDD/SSD is actually connected using the device manager and setting the "view" to "device by connection". When in RAID mode, this means that your HDD will be shown as connected to the Storage Controller (in my case Intel Desktop/Workstation/Server Chipset SATA RAID Controller) within the device manager and will use the "iaStorA.sys" driver which (like "msahci.sys") will support SSD and their TRIM functionality while also supporting RAID 0 connection. Now when in ATA mode, this means that your HDD will be shown as connected to the IDE ATA/ATAPI Controller within the device manager and the device will use the "atapi.sys" driver which is not ideal for SSD's as TRIM is not passed with this driver. What this means is that the chipset will be presented to the OS either as devices under "IDE ATA/ATAPI controllers" or as device under "Storage controllers" within the device manager itself. ![]() Willdloy, while i'm not familiar with your XPS 8100 it's likely you have an Intel chipset supporting RAID and your BIOS settings allow for either ATA or RAID configuration. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |