Jump to content

Burn ISO Image to Micro SD Card


zbinsimen
 Share

Recommended Posts

On 7/6/2018 at 10:11 AM, Terblanche said:

I have used the following free USB creator tools for years:

https://rufus.akeo.ie/

https://www.recoverywindowspassword.com/burn-iso-image-to-usb-drive.html

 

It's worth a try!

I tested Rufus before , the Rufus program is complicated , and i don't think it works for people who don't have the experience .

 

Edited by bamksever
Link to comment
Share on other sites

Search Before Posting!

On 7/6/2018 at 9:58 AM, tkaiser said:

This is 100% irrelevant just like some people reporting they never had trouble with Win32DiskImager or dd!

 

It's about the average user and expectations. And the average user runs Windows for whatever reasons and has no clue about Windows being crippled by design when it's about handling removable media and 'foreign' filesystems.

 

And the average user also has the naive assumption that burning to SD cards always works, that crappy/counterfeit SD cards do not exist and that 'transmission problems' caused by card readers or USB ports also do not exist. That's why it's so important to ONLY RECOMMEND ETCHER all the time.

 

Completely agree...

 

Etcher does a great job - and the verification ensures that one has a good write to the card...

 

When in doubt - one can use the SDCard Formatter Util (Win/Mac) to "refresh" the card prior to writing...

 

https://www.sdcard.org/downloads/formatter_4/

 

If it fails, then check either the card, or the reader...

Link to comment
Share on other sites

On 8/22/2018 at 2:55 PM, bamksever said:

I tested Rufus before , the Rufus program is complicated , and i don't think it works for people who don't have the experience .

 

As i tried , the Rufus is very unstable ,sometime it works on Windows 7 computer , but sometime it doesn't work on Windows 10 computer .

I prefer this one : https://www.iseepassword.com/how-to-burn-iso-to-usb-drive.html

Link to comment
Share on other sites

4 hours ago, Emailleray said:

As i tried , the Rufus is very unstable ,sometime it works on Windows 7 computer , but sometime it doesn't work on Windows 10 computer .

Did you use the newest version?: 

Version 3.3 (2018.09.17) [BUGFIX RELEASE]

 

I used the portable version without problems under Windows 10:
https://github.com/pbatard/rufus/releases/download/v3.3/rufus-3.3p.exe

Link to comment
Share on other sites

On 11/23/2018 at 7:49 AM, Emailleray said:

you mean Method 2: How to Burn ISO Image to USB Drive Using RMPrepUSB

Quote

Files are often corrupted or not burned properly many times.

 

sounds exactly what people want... :thumbup:

 

or Method 1: Burn ISO Image to USB Drive with WizISO?

which doesn't mention disk verification anywhere? Doesn't make sense too.

Link to comment
Share on other sites

I used for a longer time not Samsung ProEndurance SD cards and the quality looks a lot higher. Not even 1 Samsung card is broken instead of a few Sandisk cards... :) I read on another Raspi forum that Samsung cards functions the best. So it looks it does! Maybe a tip when you doubt to choose a SD brand.

Link to comment
Share on other sites

16 hours ago, haajee said:

instead of a few Sandisk cards

 

I have mainly Samsung EVO and Sandisks Extreme A1 around. Due to the nature of our work I am doing nasty stuff to them and they also (Samsung) eventually break ;)


Until you don't go out with extensive testing with few hundred pcs and you are 100% sure they are not fake, its hard to say anything. Fakes come in the same package sold by renown sellers ... this whole SD card saga is more related to the luck then anything. In last few years I already throw away a pile of them.

Link to comment
Share on other sites

The issue with burning images and getting the panic throw out from Raspberry Pi images is because the SD-CARD used and the image size do not match they differ by a small amount usually just a few megabytes on an 4, 8 or 16GB SDcard.  Does not matter which image software you use  and if you verify it or not unless they software fixes the partition up to match the card size it will throw a panic.

 

The latest version of Win32DiskImager will warn you the image size is different to the card size and allows you to continue but the produced image will panic.

 

The only way around the issue is using a partitioning tool to shorten the last partition back by say 500Mb so that the image size is guaranteed to be smaller than any card of the supposed size. Then image that card and it will work on any card of the supposed GB size.

Link to comment
Share on other sites

On 8/5/2019 at 8:28 AM, Igor said:

 

I have mainly Samsung EVO and Sandisks Extreme A1 around. Due to the nature of our work I am doing nasty stuff to them and they also (Samsung) eventually break ;)


Until you don't go out with extensive testing with few hundred pcs and you are 100% sure they are not fake, its hard to say anything. Fakes come in the same package sold by renown sellers ... this whole SD card saga is more related to the luck then anything. In last few years I already throw away a pile of them.

 

Oh i think you use the SD cards indeed al little bit (mean a lot!!) more intensive then i should do. Otherwise is in the dashcam's my idea also that the Samsung's has a longer lifetime than the Sandisk.

 

But i agree with you: the only correct way to check it is to buy a lot and do all the same things and see how long the SD cards live. Offcourse with originals. But even then could there be a bad batch of a brand... 'SD cards are consumable items' do i read somewhere on the internet. And i think we should agree. :)

 

Btw: is the lifetime of a onboard eMMC better than a SD card?

Link to comment
Share on other sites

Hi all,

 

newbee to Armbian here.

 

Have anyone burned img on MacOS and boot OPI4 LTS successfully?

 

My situation is when I burned the img on MacOS (tried using dd, elenaecther, or RPI4 imager), once the write and verify is completed, the sdcard cannot be read by MacOS. When it is used to boot OPI4, nothing came up.

 

I have a few sdcards lying around which works fine for RPI4. I can basically read the sdcard when it is imaged with RPI img file but not the same case after burning the Armbian or OPI4 stocked img files. Could this be specific to these img files on macOS? I do not have windows to try out. The img sha and asc verified.

 

This is what is shown on the diskutil command eventhough macOS cannot read it:

 

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *15.9 GB    disk3
   1:                      Linux ⁨⁩                        1.6 GB     disk3s1
                    (free space)                         14.3 GB    -

 

I tried a serial connection to OPI4 but what I seen is garbage output ... tried many different baud rate also same. So basically I have no clue what could be wrong.

 

This is what I see from the CoolTerm output.

 

..ˇk.Ÿ®Û¡™ˇüùˇœ¯Úˇˇ˘flüü∫Ú˛ÂüˇÈ±
ºˇˇ˛ˇˇÙÛˇˇí˝œˇ¸ˇˇ\ˇx„˘¸ˇn√.˚z∑∞˛≠ˇˇı˙Óˇ8fløÔøˇ=ʘo]”˛ıˇˇˇ˛Òˇ˛ˇ˛¸ˇÙ_^ν3˙ˇ˛ôˇÓ˚ˇ˝ˇ~øØÙˇˇ£·˚–≤Îtˇˇ˛¸ˇˇ˛˛ˇˇfl..Sˇùdˇˇg®ˇˇƒÙˆ¸~ø˛è˛˛ˇˇ‘ˇ¬ê∂˝ˇ¸ˇ¸ˇ˛ˇˆ˛¬o‘üΩÂÆ˛ˇø˛Ëˇyzøˇœ~ˆ˝˛Ê˙˚œ˛∫>ˇˇˇ˛˛ÒˇÁ˛˛Û˛˛¸Á˛˝ˇc¯⁄.¯Ùˇ7}¶∫€?˛Ωˇˇˇ¸˚˙ˡúøflæˇ≥Ú¸˛IÁÛÎÔÇ\˛˛¸ˆˇˇÛa¸ˇŒˇ˛¸ˇ¸Ì˚ˆ¸„ˇˇÌ¸ÿβ≈6˛ºˇ¸˙ı¸ˇ˛~flˇfi˙ˇˇ.Ú˛Àß¡8ˇ˛˛˛¸ˇ˛ˇ¸¸fl˙ˇˇ˛˛¸˝¸ˇÜ¯Ú¸¸¸˜flv~ˇ∑ˇÓæ!˝‹˙ˇˇÁ˛œø˛ˇ¸˛ƒ˘fiˇ˚Ùˇˇ˛ÛˇÚ˛˛ˇ$ˇˇÔ˛ˇ˝ˇ‚¿.˘ˇ¯˛¥ˆˆ«.Îø˛ÎͲ˛˘¸ˇæûøˇñ˛ˇˇä¯˘¿.z˛ˇ˙¯ı˛¸˚.˙˛ˇÛˇ˛¸¸¥˘.˘ˇˇ˛ˇß‹{Õflˇ§ˇ˝ˇ‰Œœû˛.€ˇ˛ˇ&˜˝√õà˝ˇˇˇ˛ˇˇˇ˛˚¸]˛ˇˇˇˇ¸˜˛.éˆˇˇˇ˜˚fl≠ù.œÀ˛Ù˙˙ˇ˝wfl˛flˇΩ˛x˚ÛrflÛu˛ˇ¯¯ˇ˛ˇ˛ˆ\˚ˇ„ˇˇ¸˛¸.˛v‰Ò˚ˇˇˇ?.ªÙ«q∫ˆˇˆflˇˇ˛ı˘ˇ˝˛üœfl+˛Ï˙ü§ó˝ˇ¸˛ˇ¯ˇˇˇ˛˘¸é˛˛˛¸ˇ-¯A‰˛¸ˇ
Baudrate: 1500000
Data bits: 8
Parity: none
Stop Bits: 1
Flow Control: off 

 

I also try to mount the img file in macOS but seems got problem. This same situation happens to focal version.

 

sudo hdiutil mount Armbian_22.02.1_Orangepi4_bullseye_current_5.15.25.img
hdiutil: mount failed - no mountable file systems

 

Any idea?

 

please help and thank you very much.

Link to comment
Share on other sites

For writing on MacOS, is use usbimager

 

But read carefully these hints:

 

Quote

MacOSX: 10.14 an up: go to "System Preferences", "Security & Privacy" and "Privacy". Add USBImager to the list of "Full Disk Access". Alternatively run from a Terminal as sudo /Applications/USBImager.app/Contents/MacOS/usbimager (this latter is the only way under 10.13).

 

and it works..

 

Markus

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...