Could Not Find A Hard Drive Attached To This Computer..SSD

  1. last year

    OKay, we just today got a shipment of laptops with 1TB SSD drives in them. I have WIndows 10 installed into them and set up the session. Below you will find the log. We are using the 4.4.3 kernel. I read somewhere that using a Bootable USB worked, which is what i will try next, however, I wanted to see if you had any other fixes so we can use PXE boot.

    Displaying Boot Arguments **

    BOOT_IMAGE=kernels\4.4.3 initrd=images\initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://192.168.0.2/clonedeploy/service/client.asmx/ USER_TOKEN=bac35671-b263-4882-8e8a-36c5edbfe278 task=ond consoleblank=0 MAC: 84:7b:eb:06:a2:75
    Linux client_console.localdomain 4.4.3 #2 SMP Mon Feb 29 15:18:42 EST 2016 i686 GNU/Linux

    Boot Image Version: 1.0.1

    ** On Demand Enabled **

    image_name=Precision_3510_Sysprep profile_id=8 server_ip=192.168.0.2 multicast=false pre_scripts= post_scripts= file_copy=False sysprep_tags= task_completed_action="Reboot" dp_id=1 image_type=Block compression_algorithm=lz4 compression_level=-1 task=pull

    ** Mounting SMB Share **

    ...... Success

    ** Looking For Hard Drive(s) **

    ...... Displaying Available Devices
    RO RA SSZ BSZ StartSec Size Device
    rw 256 512 1024 0 159744000 /dev/ram0
    Disk /dev/ram0: 152.4 MiB, 159744000 bytes, 312000 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    ...... Found Drive(s)

    ...... Drive(s):

    ** An Error Has Occurred **

    ...... Could Not Find A Hard Drive Attached To This Computer. Try A Different Kernel.

    Okay, I have figured out a work around / solution / [the only way...] to get this to work is to:

    To Upload Image:

    1. Go into Bios
    2. Disable Secure boot [if enabled]
    3. Enable Legacy Options
    4. Change boot mode from UEFI to Legacy
    5. Upload the Image

    To Deploy:

    1. Go into Bios
    2. Disable Secure boot [if enabled]
    3. Enable Legacy Options
    4. Change boot mode from UEFI to Legacy
    5. Deploy the Image

    However, Keep in mind, once you deploy the image or upload it, you need to change the Boot mode from Legacy back to UEFI or you will get a NO BOOT DEVICE AVAILABLE.

    Dell Precision 3510
    Using Kernel 4.4.3
    Windows 10 Pro
    1tb SSD

    Hope this helps someone.

  2. clonedeploy

    20 May 2016 Administrator

    Can you try the 4.5 kernel?
    https://sourceforge.net/projects/clonedeploy/files/kernels/4.5.0/

  3. Deleted last year by apshoupe
  4. Okay, I have figured out a work around / solution / [the only way...] to get this to work is to:

    To Upload Image:

    1. Go into Bios
    2. Disable Secure boot [if enabled]
    3. Enable Legacy Options
    4. Change boot mode from UEFI to Legacy
    5. Upload the Image

    To Deploy:

    1. Go into Bios
    2. Disable Secure boot [if enabled]
    3. Enable Legacy Options
    4. Change boot mode from UEFI to Legacy
    5. Deploy the Image

    However, Keep in mind, once you deploy the image or upload it, you need to change the Boot mode from Legacy back to UEFI or you will get a NO BOOT DEVICE AVAILABLE.

    Dell Precision 3510
    Using Kernel 4.4.3
    Windows 10 Pro
    1tb SSD

    Hope this helps someone.

  5. clonedeploy

    24 May 2016 Administrator

    This is interesting. I have never seen an instance were changing b/w legacy bios and efi changed the way a hard drive was detected. I wonder if the 64 bit kernel would have made a difference.

  6. 3 months ago

    I was reading over this and just for the good of the community, I am running 64-bit kernel 4.11 and I experienced the same thing. Putting everything into Legacy boot mode worked.

 

or Sign Up to reply!