UFS dd: /dev/da6: Invalid argument error while I try to dd the bootloaders to the sd card

ZioMario

ZioMario

Hello.

It's again me. Pardon moi for bothering you. I'm trying to write the bootloaders that I have generated after having installed the new port called "u-boot-khadas-edge-v" to the sd card,but I get a persistent error...

Code: 
marietto# dd if=idbloader.img of=/dev/da6 oflag=direct seek=64                
dd: /dev/da6: Invalid argument
322+1 records in
322+0 records out
164864 bytes transferred in 1.303706 secs (126458 bytes/sec)

marietto# dd if=u-boot.itb of=/dev/da6 oflag=direct seek=16384
dd: /dev/da6: Invalid argument
1833+1 records in
1833+0 records out
938496 bytes transferred in 7.378362 secs (127196 bytes/sec)

What I would like to know is :

1) why I get the error
2) if the error prevents me from writing correctly the bootloaders to the sd card.

This is important because I need to know if some change I add to the defconfig file sticks or not.
 
Maybe it is mounted? Maybe the device name is invalid? Maybe your usb to micro SD adapter is acting up.

What happens when you probe the device? Remember this command for checking microSD for rockchip u-boot?
dd if=/dev/da6 | hexdump -C | grep RK

It would work good to check your device 'da6' with right?
Make sure you flashing the correct device.

Your pkg-descr file for the port has the exact command to use but you chart your own path. That is for sure.
 
Phishfry said:
Maybe it is mounted? Maybe the device name is invalid? Maybe your usb to micro SD adapter is acting up.
Click to expand...

Correct.

Yes, there are flags/bits one can use to override this but unless a person knows absolutely what they're doing they will invariably post another thread saying, "one of my filesystems/partitions is corrupted beyond repair, what should I do?"

There are still limitations even with the flag/bits set. Probably because of IMO an incorrect placement of the comparison in the geom code. I do have a local patch that allows me to override every restriction, even those placed on the flag/bits one can naturally select on any FreeBSD system. Again, a person needs to a) know what they're doing and b) accept the risk of losing all the data on the machine.

It's best not to discuss how to circumvent the protections unless a person is willing to lose some or all the data on their storage device(s). The limitation is there for a purpose.

The other alternative is to boot from install media. There are no restrictions because none of the partitions or filesystems would be in use. But, again I hesitate to discuss this for the same reason. The risk is too great.
 
You must log in or register to reply here.
Back
Top