terminal flashing causing sd card to be unreadable












0














I am currently trying to flash my SD card, but keeps getting this error that the sd cards unreadable, I tried using etcher and dd, and it keeps doing it?



I am trying to flash https://www.home-assistant.io/hassio/installation/
to an SD card so I can use it on my RPI, but why can't i open the sd card after a normal flash?



I am able to reformat, and then add files to it, but its only when I flash it breaks?



the SD card works fine, I can without any problem open it using my linux machine or Windows machine, so it is only this macbook - the one i prefer to work with, that seem to be buggy here.



Why? Format issue?



Flashing:



sudo dd if=hassos_rpi3-1.13.img of=/dev/disk8 bs=2m
Password:
dd: /dev/disk8: Resource busy
MacBook-Pro:Downloads$ dd
dd ddns-confgen
MacBook-Pro:Downloads$ dd
dd ddns-confgen
MacBook-Pro:Downloads$ diskutil unmountdisk /dev/disk8
Unmount of all volumes on disk8 was successful
MacBook-Pro:Downloads$ sudo dd if=hassos_rpi3-1.13.img of=/dev/disk8 bs=2m
1024+0 records in
1024+0 records out
2147483648 bytes transferred in 487.625960 secs (4403957 bytes/sec)


enter image description here



Computer can not read the disk you've connected.










share|improve this question




















  • 1




    Can you post the actual error? Does the error occur during image writing or during boot attempts of the written SD card?
    – RubberStamp
    12 hours ago










  • It happens after the flash has completed, and every time I re insert it
    – neq
    12 hours ago










  • dd writes without checking, or even caring, about what type of data, partition, or any filesystem it is reading and writing. It's possible that the Mac you are using can't read the partition information that dd wrote to the card. So, what happens when you try to boot the card in your RPI? .... The image file seems to contain a GPT partition table with a Microsoft Reserved partition as the first partition. I don't have a Mac handy to check readable of the written partition information.
    – RubberStamp
    12 hours ago






  • 2




    When you write a rPi image to the SD card then you're writing a Linux filesystem (probably ext4) to it. MacOS doesn't understand this filesystem and so is reporting the error. Does diskutil list show the drive and possibly partitions? If so then the dd probably worked.
    – Stephen Harris
    10 hours ago










  • @StephenHarris What you say sounds plausible except that the card works on Windows, and as far as I know there isn't ext4 support on Windows.
    – kasperd
    7 hours ago
















0














I am currently trying to flash my SD card, but keeps getting this error that the sd cards unreadable, I tried using etcher and dd, and it keeps doing it?



I am trying to flash https://www.home-assistant.io/hassio/installation/
to an SD card so I can use it on my RPI, but why can't i open the sd card after a normal flash?



I am able to reformat, and then add files to it, but its only when I flash it breaks?



the SD card works fine, I can without any problem open it using my linux machine or Windows machine, so it is only this macbook - the one i prefer to work with, that seem to be buggy here.



Why? Format issue?



Flashing:



sudo dd if=hassos_rpi3-1.13.img of=/dev/disk8 bs=2m
Password:
dd: /dev/disk8: Resource busy
MacBook-Pro:Downloads$ dd
dd ddns-confgen
MacBook-Pro:Downloads$ dd
dd ddns-confgen
MacBook-Pro:Downloads$ diskutil unmountdisk /dev/disk8
Unmount of all volumes on disk8 was successful
MacBook-Pro:Downloads$ sudo dd if=hassos_rpi3-1.13.img of=/dev/disk8 bs=2m
1024+0 records in
1024+0 records out
2147483648 bytes transferred in 487.625960 secs (4403957 bytes/sec)


enter image description here



Computer can not read the disk you've connected.










share|improve this question




















  • 1




    Can you post the actual error? Does the error occur during image writing or during boot attempts of the written SD card?
    – RubberStamp
    12 hours ago










  • It happens after the flash has completed, and every time I re insert it
    – neq
    12 hours ago










  • dd writes without checking, or even caring, about what type of data, partition, or any filesystem it is reading and writing. It's possible that the Mac you are using can't read the partition information that dd wrote to the card. So, what happens when you try to boot the card in your RPI? .... The image file seems to contain a GPT partition table with a Microsoft Reserved partition as the first partition. I don't have a Mac handy to check readable of the written partition information.
    – RubberStamp
    12 hours ago






  • 2




    When you write a rPi image to the SD card then you're writing a Linux filesystem (probably ext4) to it. MacOS doesn't understand this filesystem and so is reporting the error. Does diskutil list show the drive and possibly partitions? If so then the dd probably worked.
    – Stephen Harris
    10 hours ago










  • @StephenHarris What you say sounds plausible except that the card works on Windows, and as far as I know there isn't ext4 support on Windows.
    – kasperd
    7 hours ago














0












0








0







I am currently trying to flash my SD card, but keeps getting this error that the sd cards unreadable, I tried using etcher and dd, and it keeps doing it?



I am trying to flash https://www.home-assistant.io/hassio/installation/
to an SD card so I can use it on my RPI, but why can't i open the sd card after a normal flash?



I am able to reformat, and then add files to it, but its only when I flash it breaks?



the SD card works fine, I can without any problem open it using my linux machine or Windows machine, so it is only this macbook - the one i prefer to work with, that seem to be buggy here.



Why? Format issue?



Flashing:



sudo dd if=hassos_rpi3-1.13.img of=/dev/disk8 bs=2m
Password:
dd: /dev/disk8: Resource busy
MacBook-Pro:Downloads$ dd
dd ddns-confgen
MacBook-Pro:Downloads$ dd
dd ddns-confgen
MacBook-Pro:Downloads$ diskutil unmountdisk /dev/disk8
Unmount of all volumes on disk8 was successful
MacBook-Pro:Downloads$ sudo dd if=hassos_rpi3-1.13.img of=/dev/disk8 bs=2m
1024+0 records in
1024+0 records out
2147483648 bytes transferred in 487.625960 secs (4403957 bytes/sec)


enter image description here



Computer can not read the disk you've connected.










share|improve this question















I am currently trying to flash my SD card, but keeps getting this error that the sd cards unreadable, I tried using etcher and dd, and it keeps doing it?



I am trying to flash https://www.home-assistant.io/hassio/installation/
to an SD card so I can use it on my RPI, but why can't i open the sd card after a normal flash?



I am able to reformat, and then add files to it, but its only when I flash it breaks?



the SD card works fine, I can without any problem open it using my linux machine or Windows machine, so it is only this macbook - the one i prefer to work with, that seem to be buggy here.



Why? Format issue?



Flashing:



sudo dd if=hassos_rpi3-1.13.img of=/dev/disk8 bs=2m
Password:
dd: /dev/disk8: Resource busy
MacBook-Pro:Downloads$ dd
dd ddns-confgen
MacBook-Pro:Downloads$ dd
dd ddns-confgen
MacBook-Pro:Downloads$ diskutil unmountdisk /dev/disk8
Unmount of all volumes on disk8 was successful
MacBook-Pro:Downloads$ sudo dd if=hassos_rpi3-1.13.img of=/dev/disk8 bs=2m
1024+0 records in
1024+0 records out
2147483648 bytes transferred in 487.625960 secs (4403957 bytes/sec)


enter image description here



Computer can not read the disk you've connected.







dd sd-card flash






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 12 hours ago

























asked 12 hours ago









neq

1033




1033








  • 1




    Can you post the actual error? Does the error occur during image writing or during boot attempts of the written SD card?
    – RubberStamp
    12 hours ago










  • It happens after the flash has completed, and every time I re insert it
    – neq
    12 hours ago










  • dd writes without checking, or even caring, about what type of data, partition, or any filesystem it is reading and writing. It's possible that the Mac you are using can't read the partition information that dd wrote to the card. So, what happens when you try to boot the card in your RPI? .... The image file seems to contain a GPT partition table with a Microsoft Reserved partition as the first partition. I don't have a Mac handy to check readable of the written partition information.
    – RubberStamp
    12 hours ago






  • 2




    When you write a rPi image to the SD card then you're writing a Linux filesystem (probably ext4) to it. MacOS doesn't understand this filesystem and so is reporting the error. Does diskutil list show the drive and possibly partitions? If so then the dd probably worked.
    – Stephen Harris
    10 hours ago










  • @StephenHarris What you say sounds plausible except that the card works on Windows, and as far as I know there isn't ext4 support on Windows.
    – kasperd
    7 hours ago














  • 1




    Can you post the actual error? Does the error occur during image writing or during boot attempts of the written SD card?
    – RubberStamp
    12 hours ago










  • It happens after the flash has completed, and every time I re insert it
    – neq
    12 hours ago










  • dd writes without checking, or even caring, about what type of data, partition, or any filesystem it is reading and writing. It's possible that the Mac you are using can't read the partition information that dd wrote to the card. So, what happens when you try to boot the card in your RPI? .... The image file seems to contain a GPT partition table with a Microsoft Reserved partition as the first partition. I don't have a Mac handy to check readable of the written partition information.
    – RubberStamp
    12 hours ago






  • 2




    When you write a rPi image to the SD card then you're writing a Linux filesystem (probably ext4) to it. MacOS doesn't understand this filesystem and so is reporting the error. Does diskutil list show the drive and possibly partitions? If so then the dd probably worked.
    – Stephen Harris
    10 hours ago










  • @StephenHarris What you say sounds plausible except that the card works on Windows, and as far as I know there isn't ext4 support on Windows.
    – kasperd
    7 hours ago








1




1




Can you post the actual error? Does the error occur during image writing or during boot attempts of the written SD card?
– RubberStamp
12 hours ago




Can you post the actual error? Does the error occur during image writing or during boot attempts of the written SD card?
– RubberStamp
12 hours ago












It happens after the flash has completed, and every time I re insert it
– neq
12 hours ago




It happens after the flash has completed, and every time I re insert it
– neq
12 hours ago












dd writes without checking, or even caring, about what type of data, partition, or any filesystem it is reading and writing. It's possible that the Mac you are using can't read the partition information that dd wrote to the card. So, what happens when you try to boot the card in your RPI? .... The image file seems to contain a GPT partition table with a Microsoft Reserved partition as the first partition. I don't have a Mac handy to check readable of the written partition information.
– RubberStamp
12 hours ago




dd writes without checking, or even caring, about what type of data, partition, or any filesystem it is reading and writing. It's possible that the Mac you are using can't read the partition information that dd wrote to the card. So, what happens when you try to boot the card in your RPI? .... The image file seems to contain a GPT partition table with a Microsoft Reserved partition as the first partition. I don't have a Mac handy to check readable of the written partition information.
– RubberStamp
12 hours ago




2




2




When you write a rPi image to the SD card then you're writing a Linux filesystem (probably ext4) to it. MacOS doesn't understand this filesystem and so is reporting the error. Does diskutil list show the drive and possibly partitions? If so then the dd probably worked.
– Stephen Harris
10 hours ago




When you write a rPi image to the SD card then you're writing a Linux filesystem (probably ext4) to it. MacOS doesn't understand this filesystem and so is reporting the error. Does diskutil list show the drive and possibly partitions? If so then the dd probably worked.
– Stephen Harris
10 hours ago












@StephenHarris What you say sounds plausible except that the card works on Windows, and as far as I know there isn't ext4 support on Windows.
– kasperd
7 hours ago




@StephenHarris What you say sounds plausible except that the card works on Windows, and as far as I know there isn't ext4 support on Windows.
– kasperd
7 hours ago















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490478%2fterminal-flashing-causing-sd-card-to-be-unreadable%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490478%2fterminal-flashing-causing-sd-card-to-be-unreadable%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Accessing regular linux commands in Huawei's Dopra Linux

Can't connect RFCOMM socket: Host is down

Kernel panic - not syncing: Fatal Exception in Interrupt