Just a warning, it'll take a long time (perhaps up to an hour) and you'll get no feedback on the command line until it's finished.
There are ways to get feedback, but they're non-trivial to explain or require extra software.
BW

Just a warning, it'll take a long time (perhaps up to an hour) and you'll get no feedback on the command line until it's finished.

It be fine. I'm doing my offsite backups today and that's taking hours. I can rest my hands a bit :)Badwolf wrote: 16 Apr 2024 11:23 Just a warning, it'll take a long time (perhaps up to an hour) and you'll get no feedback on the command line until it's finished.

Code: Select all
sudo dd bs=4M if=H5 Pistorm (2024-04-14 1835).img of=/dev/sdd1 oflag=direct
bash: syntax error near unexpected token `('
$ sudo dd bs=4M if=steve.img of=/dev/sdd1 oflag=direct

I don't think that'll work -- that's /dev/sdd1 -- first partiion on sdd.exxos wrote: 16 Apr 2024 14:18 Here we go then, 2nd attempt lucky I guess.
:ball:Code: Select all
sudo dd bs=4M if=H5 Pistorm (2024-04-14 1835).img of=/dev/sdd1 oflag=direct bash: syntax error near unexpected token `(' $ sudo dd bs=4M if=steve.img of=/dev/sdd1 oflag=direct

Thats what it said in DISKS.Badwolf wrote: 16 Apr 2024 14:38 I don't think that'll work -- that's /dev/sdd1 -- first partiion on sdd.
You'll likely want (I'm guessing, but seems reasonable from the size of the image) the whole block device -- /dev/sdd in this case (without the 1).
Don't nuke your main hard disc, BTW. That's possibly /dev/sda or similar.

At the top: /dev/sdd
I don't know what passworded means in this case, but unless something at a very low level (bios level) is stopping linux writing to it, trashing is perfectly possible if you choose the wrong device.Indeed I don't want to kill my main drive, but nothing would surprise me. But my windows drives are all passworded.. so I hope it wont trash those.

I was using the pi imager thing in windows before.Badwolf wrote: 16 Apr 2024 14:56 Anyway, I'm pretty sure that should be /dev/sdd. Perhaps that's where your previous image restore attempt was going wrong?
Well, I don't know how to do that. All just seems way to over complicated to me. Think I am just better sticking to windows stuff .PS: screenie also says is's mounted. You don't want it mounted when you're writing to it at the block level.

He's encrypted the drive. This will mean that it is unable to be resized without destroying it or accessed in any way other than from Windows. Just changing the partition table can screw up BitLocker.Badwolf wrote: 16 Apr 2024 14:56 I don't know what passworded means in this case, but unless something at a very low level (bios level) is stopping linux writing to it, trashing is perfectly possible if you choose the wrong device.

Users browsing this forum: apple [bot], ClaudeBot, petal [bot] and 18 guests