Unsolved
1 Message
0
1550
February 24th, 2021 14:00
USB stick being seen as disk 0
Hi all,
We use Microsoft deployment toolkit to build our laptops and it was running fine up until we just received a batch of new latitude 5520s. MDT is now failing. I've narrowed down the issue though.
We boot MDT from bootable USB sticks and in every other model of machine, the local HDD is disk 0 and USB is disk 1. However, on the 5520s, the USB stick is being seen as disk 0 and the local HDD as disk 1. So MDT is wiping the USB stick and then trying to deploy the image to it. Which is obviously failing.
How can I get it back to the local being disk 0 regardless of the USB being inserted?
Thanks
No Events found!
jphughan
11 Legend
•
14K Posts
•
79.9K Points
0
February 24th, 2021 17:00
@Obarton Disk numbers are assigned in the order the disks appear to the OS. I've never seen a case where internal storage was enumerated after USB storage, but my guess as to underlying cause is that if the systems are in RAID mode rather than AHCI mode, then the Intel RST drivers may be taking longer to load. It seems that they've become rather more complex, although if your systems are using Intel Optane storage, then you have to use RAID mode. In terms of a fix, I'm not sure you can delay the enumeration of USB storage or make internal storage enumerate faster. I haven't personally used MDT in quite a while, but isn't there some other way to select the target disk besides disk ID? I work in an environment that uses SCCM, and in our case we have a PowerShell script that checks all local disks looking for certain conditions to determine which one should store the OS -- if it's a VMware virtual disk, it's always disk 0; if it's a PowerEdge server with a BOSS, then it's whichever disk number corresponds to the BOSS, and so on. Then the script that disk, cleans it, initializes it, and sets up partitions, and assigns the OS partition drive letter W (to avoid conflicts with other drive letters that may already have been assigned). And then the SCCM task sequence says, "Install the OS on whichever volume is assigned letter W". I don't know if that would be feasible within MDT and your particular use case, but I have to imagine there's some way to target a different disk rather than only being able to target disk 0.
ConnorB
1 Rookie
•
5 Posts
0
March 5th, 2021 02:00
I would agree with the Intel RST drivers taking longer to load. In theory, if you had a task sequence in MDT, you can change the target drive. Changing the disk number in the below example would target the correct disk.
Not the ideal solution but it should work.
@Obarton out of interest, where did you get your drivers for MDT. We have some Latitude 5520s but are struggling to get MDT to see the local drive at all. Did you make any changes to BIOS etc?