Thorsten Dunker

updated

10 years ago

TD

Thorsten Dunker

1 Rookie

•

6 Posts

1

20719

December 16th, 2016 05:00

[WARNING] XPS 13 9360/BIOS Rev. 1.2.3 - SAMSUNG 960 Pro does not work anymore

Hello,

I've upgraded my XPS 13 9360 with the SAMSUNG 960 Pro a few weeks ago. It worked well with BIOS Rev. 1.0.7 in AHCI-Mode. Yesterday, I performed an BIOS-update to version 1.2.3. The SSD stopped working immediately (no bootable device). Changes of the BIOS settings (No SATA, AHCI, RAID) do not change that behaviour at all. It is even not possible to reinstall the OS, the installer show the SSD but does not allow to reinstall Windows 10. Dell support recommends to install the original hardware. 

I think that is crazy. While looking for a solution for that problem I found that comparable problems happened with other BIOS upgrades for i.e. Dell XPS 13 9350 before. Dell has serious problems with NVMe SSDs.

Best regards,

Thorsten

  • Justin C

    6 Operator

    •

    783 Posts

    5457

    0

    Posted January 23rd, 2017 10:00

    @Community,

    I can now confirm for you that Dell is working on a new BIOS to resolve the boot issue caused by 1.2.3. I'm trying to get an ETA for the new BIOS version. I'll get back as soon as I know more.

    I don't have an official work around at this time but I'll try to get us one.

  • Justin C

    6 Operator

    •

    783 Posts

    4527

    0

    Posted January 26th, 2017 11:00

    @Community,

    I've had a couple of customers test 1.3.2 and it's solved the issue for them.

    Another note: If you're in urgent need of the new BIOS you can contact @DellCaresPro and mention SLN304879.

  • shoffmeister

    1 Rookie

    •

    53 Posts

    4527

    1

    Posted January 26th, 2017 12:00

    On top, <ADMIN NOTE: Broken link has been removed from this post by Dell>

  • Robert P (retired)

    6 Operator

    •

    9396 Posts

    7147

    0

    Posted December 16th, 2016 06:00

    Hi Thorsten Dunker,

    Thanks for posting.

    Here is some information you may find helpful:

    http://dell.to/2hOGrfx

    and this:

    http://dell.to/2hOFm7d


    Robert P (retired)

  • Giqles

    1 Rookie

    •

    11 Posts

    7147

    0

    Posted December 18th, 2016 13:00

    I'm using stock hardware for the XPS 9360, again in AHCI mode as I have dual boot with ubuntu. I installed the bios update today, and I also have 'no bootable device'. If I switch to RAID from AHCI I don't get 'no bootable device', but instead I get met with a windows 10 error of inaccessible boot device; because the windows partition is configured for AHCI.

    Any suggestions Dell?

  • tranterm

    1 Message

    7147

    0

    Posted December 19th, 2016 03:00

    Same just happen to me today I as in Australia

    I just sent the laptop back to Dell today.

    SAMSUNG 960 Pro all working on bios before update to 1.2.3 then stop working  no matter what bios is set too it will not boot.

    I did notice on 1.0.7 the Samsung pro 960 2tb did have a ip address type with in the bootable bios but in 1.2.3 it is missing and it still find it pro 960, but will not boot it under raid or the same settings as before.

    Done all of this also.

    I've upgraded my XPS 13 9360 with the SAMSUNG 960 Pro a few weeks ago. It worked well with BIOS Rev. 1.0.7 in AHCI-Mode. Yesterday, I performed an BIOS-update to version 1.2.3. The SSD stopped working immediately (no bootable device). Changes of the BIOS settings (No SATA, AHCI, RAID) do not change that behaviour at all. It is even not possible to reinstall the OS, the installer show the SSD but does not allow to reinstall Windows 10. Dell support recommends to install the original hardware.

    Dell need to patch this because it appears limited testing was done with m.2 Samsung pro 960 storage devices, they need to patch this issue quickly as not look good on Dell to not have a quick responses on this .

    I hope to here for them soon and will update on what Dell has as a fix.

  • 7147

    1

    Posted December 19th, 2016 05:00

    Both links are unhelpful since they don't address the issue at hand. It is serious regression introduced in BIOS 1.2.3.

    I upgraded the SSD in my 9360 to a Samsung 960 Evo 500GB to get OPAL encryption as it wasn't available with the previous BIOS 1.0.6 and the stock 256GB SSD. BIOS , nor does BIOS 1.0.6 allow OPAL on the Samsung 960 Evo, hence trying BIOS 1.2.3.

    Once I found the inability to boot any OS from the SSD despite numerous reinstalls in legacy and UEFI mode, both with Linux and Windows 10, I tried to downgrade, which, despite downgrade being enabled in the BIOS, is blocked, making the situation catastrophic. Interestingly the Samsung SM951 256GB from my XPS 15 9550 does boot fine though.

    Losing a lot of time on this, I eventually found I can enable SD card booting in the BIOS, and have reinstalled Ubuntu with the EFI partition and /boot on the SD card, keeping the other filesystems on the SSD for good performance and power consumption without losing USB ports or SSD capacity. Shame on Dell for two regressions while still not providing OPAL support on such a revered and expensive laptop!

  • Giqles

    1 Rookie

    •

    11 Posts

    7147

    0

    Posted December 19th, 2016 12:00

    danielblueman, could you go into the steps for your boot from SD card solution? Would that work with a dual boot set up?

    Currently I've managed to get the RAID setting back up and running, but I can only use Windows 10 on that. (Not to mention the many combinations of usb sticks, boot priorities and other junk I had to fiddle with to boot from a USB drive in UEFI mode). Switching to AHCI just refuses to boot any device. If I had done that before the BIOS update the boot would have initialised successfully, but then typically failed due to driver issues. Ie, the windows 10 'inaccessible_boot_device' error, rather than Dells 'boot device not found'.

    I agree this is a serious issue and I'm surprised no one from Dell has responded properly. Dell rep I spoke to earlier informed me they only had to get windows running on it... anything other than that was my problem!

  • 7147

    0

    Posted December 19th, 2016 19:00

    Sure, in the BIOS, enable:

    System Configuration -> Miscellaneous Devices -> Secure Digital (SD) Card Boot

    This should work for dual-booting, though I found for Linux, the /boot partition needs to be on the SD card also.

  • Thorsten Dunker

    1 Rookie

    •

    6 Posts

    7131

    0

    Posted December 20th, 2016 02:00

    I managed to get it working. My steps:

    - BIOS in RAID

    - USB Stick prepared for UEFI/GPT

    - Important: Windows 10 2016 does not work for me, only Windows 10 2016 LTSB!