Problem burning image in linux

[Die-go GarGon]

Hello.

 

I have a annoying problem each time i burn with 'dd' a armbian*raw image (custom) in linux my orange pi lite not boot, i must  format and write in windows (write32...) then works.

 

any idea?

[  998.313215] usb 3-7: new high-speed USB device number 6 using xhci_hcd
[  998.443018] usb 3-7: New USB device found, idVendor=058f, idProduct=6331
[  998.443026] usb 3-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  998.443030] usb 3-7: Product: Mass Storage Device
[  998.443033] usb 3-7: Manufacturer: Generic
[  998.443036] usb 3-7: SerialNumber: 058F091111B
[  998.443733] usb-storage 3-7:1.0: USB Mass Storage device detected
[  998.446321] scsi host7: usb-storage 3-7:1.0
[  999.445719] scsi 7:0:0:0: Direct-Access     Multi    Flash Reader     1.00 PQ: 0 ANSI: 0
[  999.446157] sd 7:0:0:0: Attached scsi generic sg4 type 0
[  999.959293] sd 7:0:0:0: [sde] 15548416 512-byte logical blocks: (7.96 GB/7.41 GiB)
[  999.959733] sd 7:0:0:0: [sde] Write Protect is off
[  999.959739] sd 7:0:0:0: [sde] Mode Sense: 03 00 00 00
[  999.960115] sd 7:0:0:0: [sde] No Caching mode page found
[  999.960119] sd 7:0:0:0: [sde] Assuming drive cache: write through
[  999.964855]  sde: sde1
[  999.967051] sd 7:0:0:0: [sde] Attached SCSI removable disk
root@diego-trantor:~/Armbian/output/images# 

[  996.770245] usb 3-8: reset high-speed USB device number 4 using xhci_hcd
[  997.311523] sd 6:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  997.311533] sd 6:0:0:0: [sde] tag#0 Sense Key : Unit Attention [current] 
[  997.311540] sd 6:0:0:0: [sde] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[  997.311546] sd 6:0:0:0: [sde] tag#0 CDB: Write(10) 2a 00 00 00 a4 90 00 00 f0 00
[  997.311551] blk_update_request: I/O error, dev sde, sector 42128
[  997.311557] Buffer I/O error on dev sde1, logical block 5010, lost async page write
[  997.311567] Buffer I/O error on dev sde1, logical block 5011, lost async page write
[  997.311571] Buffer I/O error on dev sde1, logical block 5012, lost async page write
[  997.311576] Buffer I/O error on dev sde1, logical block 5013, lost async page write
[  997.311580] Buffer I/O error on dev sde1, logical block 5014, lost async page write
[  997.311584] Buffer I/O error on dev sde1, logical block 5015, lost async page write
[  997.311594] Buffer I/O error on dev sde1, logical block 5016, lost async page write
[  997.311599] Buffer I/O error on dev sde1, logical block 5017, lost async page write
[  997.311603] Buffer I/O error on dev sde1, logical block 5018, lost async page write
[  997.311607] Buffer I/O error on dev sde1, logical block 5019, lost async page write
[  997.684441] VFS: Dirty inode writeback failed for block device sde1 (err=-5).
[  997.688937]  sde: sde1
[  998.085631] usb 3-8: reset high-speed USB device number 4 using xhci_hcd
[  998.635907]  sde: sde1
[  999.317134] usb 3-8: reset high-speed USB device number 4 using xhci_hcd
[  999.862662] sd 6:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  999.862672] sd 6:0:0:0: [sde] tag#0 Sense Key : Unit Attention [current] 
[  999.862679] sd 6:0:0:0: [sde] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[  999.862686] sd 6:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 00 00 08 18 00 00 08 00
[  999.862690] blk_update_request: I/O error, dev sde, sector 2072
[  999.871627]  sde: sde1
[ 1000.096850] usb 3-8: reset high-speed USB device number 4 using xhci_hcd
[ 1000.642201] sd 6:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1000.642206] sd 6:0:0:0: [sde] tag#0 Sense Key : Unit Attention [current] 
[ 1000.642209] sd 6:0:0:0: [sde] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[ 1000.642212] sd 6:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 00 00 02 00 00 00 f0 00
[ 1000.642214] blk_update_request: I/O error, dev sde, sector 512
[ 1000.649077]  sde: sde1

[lanefu]

what is your dd command? is an automounter attaching the card you're working on? what sd card?

 

Tapatalk thinks its important to tell you im using tapatalk from a phone.

[tkaiser]

There's no need to 'format' an SD card when you want to burn an OS image to it (since you overwrite the whole device and therefore the partition table also).

 

I would assume the output above is from a x86 Linux host where you try to burn the image to the SD card? If so obviously the burn process is corrupting data (quite normal behaviour, some USB card readers simply suck and start overheating, then you get different behaviour when connecting card readers to USB front ports -- connected with cables most probably lacking protection -- while doing the same on the back ports directly soldered to the mainboard works flawlessly and so on).

 

There's a reason we recommend always testing card (or let's better say 'burn process') first: http://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-sd-card

[Die-go GarGon]

i format only in windows, anyway try too with and without  formating in linux.

 

I try dd with:

dd bs=1M  if=... of=.../dev/sde1 (and sde...)

dd bs=4M if=... of=.../dev/sde1

 

bs=512...

 

sd card umounted of course...

 

uname -a

Linux diego-trantor 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

 

Problem its in Front/Back ports. I try two working (in windows) sd cards (two brands)

 

Like i say works fine if i write the image in windows (same machine),  but its annoying restart for write the image.

 

its clearly a linux thing.

 

 

thanks.

[lanefu]

you're writing to a partition instead of the top of the card. use sde instead of sde1

 

Tapatalk thinks its important to tell you im using tapatalk from a phone.

[Die-go GarGon]

I try first time write to block devices, and try again now:

root@diego-trantor:~/Armbian/output/images# dd bs=1M if=Armbian_5.17_Orangepilite_Debian_jessie_3.4.112.raw  of=/dev/sde
1208+0 registros leídos
1208+0 registros escritos
1266679808 bytes (1,3 GB, 1,2 GiB) copied, 188,9 s, 6,7 MB/s
root@diego-trantor:~/Armbian/output/images# dmesg
[32423.474238]  sde: sde1
[32622.612644] usb 3-8: reset high-speed USB device number 24 using xhci_hcd
[32623.272931] sd 12:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[32623.272942] sd 12:0:0:0: [sde] tag#0 Sense Key : Unit Attention [current] 
[32623.272949] sd 12:0:0:0: [sde] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[32623.272956] sd 12:0:0:0: [sde] tag#0 CDB: Write(10) 2a 00 00 1a da f0 00 00 f0 00
[32623.272961] blk_update_request: I/O error, dev sde, sector 1759984
[32623.272967] Buffer I/O error on dev sde, logical block 219998, lost async page write
[32623.272977] Buffer I/O error on dev sde, logical block 219999, lost async page write
[32623.272981] Buffer I/O error on dev sde, logical block 220000, lost async page write
[32623.272985] Buffer I/O error on dev sde, logical block 220001, lost async page write
[32623.272989] Buffer I/O error on dev sde, logical block 220002, lost async page write
[32623.272993] Buffer I/O error on dev sde, logical block 220003, lost async page write
[32623.272997] Buffer I/O error on dev sde, logical block 220004, lost async page write
[32623.273001] Buffer I/O error on dev sde, logical block 220005, lost async page write
[32623.273006] Buffer I/O error on dev sde, logical block 220006, lost async page write
[32623.273010] Buffer I/O error on dev sde, logical block 220007, lost async page write
[32623.567892]  sde: sde1

[Die-go GarGon]

well... sh*t,  finally i can write a image on linux,

 

Seems when i try bs=512 i try only using sde1 since 512 seems work if write to block device ( /dev/sde)

 

i imagine its my card reader perhaps? i will try got other for try if i can write more fast.

 

thanks!

[tkaiser]

bs=512

 

Writing only 512 byte chunks will slow things down and maybe this helps with your card reader. It's really a well known problem with many of them that they start to overheat when used on USB3 ports and silently corrupt data. So maybe it works in Windows since there lower transfer speeds are negotiated or your burning program uses smaller block sizes and therefore the reader/writer doesn't corrupt data (did you check in device manager how the card reader is listed?)

 

Anyway: It's a simple hardware problem that could be solved by using a slower USB connection if possible (pulling the old USB2 hub out of the drawer and using it between reader and USB3 ports for example).

[Die-go GarGon]

i will check the speed in windows and try another card reader. thx.