Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"The disk you attached was not readable by this computer" / Debian 12 image / MacOS #198

Open
bjull001 opened this issue Dec 29, 2024 · 9 comments

Comments

@bjull001
Copy link

Hello everyone,
I have a problem where I can't find a solution.
I'm trying to flash the new image of the V3.0.0 image on a SD card using Pi Imager or BalenaEtcher, but after everything finishes and I reinsert the SD card, I get the error message mentioned above.
My process is as follows:

  • Insert SD Card (I tried two SD cards and two SD card readers)
  • Erase it using SD card formatter (5.0.3) or Pi imager ( I tried both)
  • Downloading the image ( Minimal or Klipper, both finished successfully, and I downloaded them several times. Also tried the armbian build.)
  • Use Pi imager (1.8.5) or BalenaEtcher (1.19.25) to flash the image on the SD card
  • Process finishes successfully and ejects the SD card.
  • Reinsert the SD card and get the error message mentioned above. (Options are eject, ignore or initialize. )

I'm using a 2019 Macbook Pro with Sonoma 14.6.1 and the CB1_V2.2 with the adatper board.

Also flashing the V2.3.4 image works just fine.

Is there anything I'm missing?
Thank you in advance for any help!

@shawnchr
Copy link

shawnchr commented Dec 29, 2024

I have not found an answer to the issue. Other than using a windows computer to edit the file. I have tried everything I am not sure what they are doing differently but balena etcher fails to even write the image do to some change in the compression they are using.

@toastfr35
Copy link

toastfr35 commented Dec 30, 2024

The sha256sum I get on the .img.xz file after downloading does not match the one in the repo ... damaged file?

@Pneumanifest
Copy link

The sha256sum I get on the .img.xz file after downloading does not match the one in the repo ... damaged file?

Unzip the file first.

@toastfr35
Copy link

Thanks, I didn't spot they change the sha256 to be on the .img instead of the .xz has it was on 2.3.4

@bjull001
Copy link
Author

bjull001 commented Jan 2, 2025

Hello again,
Thank you for the answers.
When checking the sha256 I get two different results, no matter if I check the img.xz or just the .img
Also, just trying to unpack the img. doesn't work either and gives me the same error as above.
I also tried to compile my own image but got the same error even though the compiling was successful.

Would love to know if this is a MacOS thing or if it persists on Windows or Linux.
Thanks.

@ecoinomist
Copy link

same issue here, I had the same problem 6 months ago when trying to install ArmBian, and gave up. Used the CB1 image without ArmBian. It must be something from ArmBian incompatible with MacOS

@bjull001
Copy link
Author

@ecoinomist Thank you for your answer. Could you describe how you used the CB1 image without armbian? What modifications have to be done? Thank you!

@dahenson54
Copy link

I'm having the same issue with the CB1 V1.0 on a Mac Mini M2.

@dahenson54
Copy link

Update: I was able to get mine to work. I unzipped the file and burned it to the card using Balena. I still got the message when it was complete, but I selected "Ignore" and ejected the card. It loaded into the CB1 and booted up without problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants