SSD immediately becomes unallocated/Not Initialized after starting flash

balenaEtcher
1

Hi,

I just received a new 240 Kingston SSD, I initialized it and it shows up as healthy along with my other two SSD’s. With the Disk Managment tab open I can see that the second I begin a flash on Balena Etcher my SSD I am flashing to becomes unallocated and not initialized, secondly, it does not show up in my file explorer.

3

This is happening to me as well…I’ve un/reinstalled Etcher, tried doing a quick & non quick format and it always unallocates my SSD when I engage the etcher program.

I’ve used it before and had no problems but suddenly I cant get it to work. Lmk if something works for you, I’ll try almost anything at this point!

4

I just tried it with a non quick format in hopes that would change anything but I am running into the exact same error.

5

already tried that, wasted two of my hours waiting for it to allocate then failed the same way. so now we play the waiting game

1 Like
6

After completing the flash I unplugged my SSD from the USB to Sata adapter, waited a few seconds and then plugged it back into my computer. Even though it un initialized in the disk manager the drive still appeared after waiting a few seconds.

8

Hello

@alldom can you please confirm which operating system you are on and which balenaEtcher version you are using?

@JTP12018 i see you mentioned here you are using v1.5.120 for windows.
This was working for you previously. Can you confirm which version of balenaEtcher you were using?

Are you able to open the etcher console and see if there are any errors? You can do so by pressing Ctrl + Shift + I .

Would be grateful if either or both of you can try an older version of balenaEtcher so we can identify if this was a regression. You can find previous releases here and going download the respective one for your os from the download page of a particular release.

Thanks for reporting this.

12

Hi @alldom @jtp12018

Just checking in to ask whether you have perhaps been able to try out Rahul’s suggestion of testing previous releases of Etcher?

Kind regards
Alida

14

Yeah I tried, no success. Waiting on some next steps because I can’t find anything that’s worked.

16

Can you tell us what image you’re flashing?

21

Hello @jtp12018

Are you still having issues? If so, please provide the following information:
a) the version of Etcher that you are using.
b) details of the image that you are trying to flash.
c) the console output from Etcher when any problems occur (press Ctrl-Shift-I in Etcher to access the console output).

Thanks
Mark

24

Also seeing this flash failed, uninitialized disk error.

Etcher: balenaEtcher-Portable-1.5.120.exe
Image: 2021-05-07-raspios-buster-armhf-full.img
Results:

{
  "image": {
    "size": 8602517504,
    "name": "2021-05-07-raspios-buster-armhf-full.img",
    "hasMBR": true,
    "partitions": [
      {
        "offset": 4194304,
        "size": 268435456,
        "type": 12,
        "index": 1
      },
      {
        "offset": 272629760,
        "size": 8329887744,
        "type": 131,
        "index": 2
      }
    ],
    "extension": "img",
    "path": "C:\\Users\\R\\Downloads\\2021-05-07-raspios-buster-armhf-full.img"
  },
  "drives": [
    {
      "size": 500107862016,
      "isVirtual": false,
      "enumerator": "SCSI",
      "logicalBlockSize": 512,
      "raw": "\\\\.\\PhysicalDrive0",
      "error": null,
      "isReadOnly": false,
      "displayName": "G:\\",
      "blockSize": 512,
      "isSCSI": true,
      "isRemovable": false,
      "device": "\\\\.\\PhysicalDrive0",
      "busVersion": "2.0",
      "isSystem": true,
      "busType": "SATA",
      "isCard": false,
      "isUSB": false,
      "devicePath": null,
      "mountpoints": [
        {
          "path": "G:\\"
        }
      ],
      "description": "HFS500G32TND-3112A",
      "isUAS": false,
      "partitionTableType": "gpt"
    }
  ],
  "driveCount": 1,
  "uuid": "f965fb4d-6524-47d9-af43-a6a426214469",
  "flashInstanceUuid": "f965fb4d-6524-47d9-af43-a6a426214469",
  "error": {
    "name": "Error",
    "message": "Unmount failed",
    "stack": "Error: Unmount failed"
  },
  "sample": 0.1,
  "applicationSessionUuid": "87c5174b-56d3-4632-919b-e4e2d88829e7",
  "flashingWorkflowUuid": "2d78175b-328e-44e5-8600-e5173cce1943"
}

Hope this helps.

EDIT: I worked around this by using Raspberry Pi imager to burn to a USB stick, booting the Pi from that, and then using the built in tool in Raspbian to clone the USB stick over to the SSD.

25

Hi @iamauser

I see that you have replied to 2 threads with the same issue. Let’s focus on this in the other thread instead of this one.

1 Like
27

I don’t require help now because I used a different method, but FWIW, I did experience the same unmount failed issue trying to burn a W10 ISO to a USB stick too. Will leave the others in the thread to post back if they still need help.