you could not access the drive - whilst i want to create a rescue stick ...

Hi there - good day.

while creating a Rescue-USB-Stick i downloaded the opensuse leap image

then i continued

dd if=openSUSE-Leap-15.2-DVD-x86_64.iso of=/dev/sdX bs=32k
where sdX=sdb or sdc is the USB stick

but it stuck

$ dd if=openSUSE-Leap-15.2-DVD-x86_64.iso of=/dev/sdb bs=32k
dd: konnte '/dev/sdb' nicht öffnen: Keine Berechtigung
(base) martin@mx:~/Downloads
$ dd if=openSUSE-Leap-15.2-DVD-x86_64.iso of=/dev/sdc bs=32k
dd: konnte '/dev/sdc' nicht öffnen: Keine Berechtigung
(base) martin@mx:~/Downloads

how to go arond - what to do !?

btw: i currently work on MX-Linux…

Direct access to devices (as you do with /dev/sdX) is only allowed for root.
Imagine that each and every user could overwrite all disks with some data of his/her choice.

And when a tool says that there is no permission to access a file, the first thing you should do is of course check what the permissions of the file are.

hello and good day dear Henk

many many thanks for the quick answer - and yes: it is convincing.

i will redo this as root


If you’re using MXLinux, why are you posting on the Opensuse forum? You’ve been working with Linux a good while now, and know about using dd from some of your past threads, and about permissions regarding sudo. You’ve also posted this on several other forums as well. Folks are happy to help, but you will have to show some effort to apply what you’ve learned and been told as well. Also, using DD isn’t the best way to burn an image; again, you are familiar with imagewriter, rufus, etcher, and other ISO burning utilities, as you’ve used them numerous times in the past.

All of those tools will also tell you that you need admin rights, even on Windows, to burn an image.

What is wrong with dd (not DD)?

Yes, it is lowercase, didn’t mean to be misleading.

Personally, dd can be too dangerous when you don’t use it correctly. putting in “dd … /dev/sda” versus the /dev/sdX (where sdX is the USB stick), can nuke your machine. Using something like Imagewriter (my personal preference), or another purpose-built burning tool is much “safer”. I know for Imagewriter it will pop up the hardware information of the stick, so it’s VERY obvious that you’re using your Sandisk Whatever stick, versus writing an image to your hard drive. I’ve had varying results with dd for such things; it’s a great utility, but in this instance not the right one (in my opinion).

Past that, the OP has been burning USB sticks for years, along with having much experience with dd, and 15 years experience with Linux. Weird that they can’t use something they’ve used for that long. Just frustrating when you try to help someone for that long.

For me the good thing about dd is that I know what it is doing, while all sorts of newfangled tools may do things I am not aware of. They may be innocent, but why should I use them where I have good old dd? Yes, I know I am a bit old.

Oh, I don’t disagree at all. dd is a great command and is hugely versatile, but it is easy to make a mistake. If I’ve got 10 things to do, a GUI can make things easier to use. I still think Imagewriter is the best of the bunch…can’t get much simpler, interface is simple, and I’ve never had it default to anything but the USB stick I have in…my ‘important’ drives are at the bottom of the list.