Page 5 of 13
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 11:23
by Badwolf
exxos wrote: 16 Apr 2024 11:09
Thanks @Badwolf will give it a try after lunch :)
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
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 11:28
by exxos
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.
It be fine. I'm doing my offsite backups today and that's taking hours. I can rest my hands a bit :)
Still not maxing out my Ryzen 7 5700X :lol: :roll:
Capture.PNG
EDIT:
Dammit!
Capture.PNG
:threadjacked:
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 14:18
by exxos
Here we go then, 2nd attempt lucky I guess.
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
:ball:
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 14:38
by Badwolf
exxos wrote: 16 Apr 2024 14:18
Here we go then, 2nd attempt lucky I guess.
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
:ball:
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.
BW
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 14:50
by exxos
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.
Thats what it said in DISKS.
ksnip_20240416-144811.png
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.
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 14:56
by Badwolf
exxos wrote: 16 Apr 2024 14:50
Thats what it said in DISKS.
ksnip_20240416-144811.png
At the top: /dev/sdd
The first partition is /dev/sdd1
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 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.
Anyway, I'm pretty sure that should be /dev/sdd. Perhaps that's where your previous image restore attempt was going wrong?
BW
PS: screenie also says is's mounted. You don't want it mounted when you're writing to it at the block level.
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 15:01
by exxos
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?
I was using the pi imager thing in windows before.
PS: screenie also says is's mounted. You don't want it mounted when you're writing to it at the block level.
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 .
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 15:09
by stephen_usher
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.
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.
My advice would be to decrypt the drive before any attempt at a Linux installation as otherwise things will break and break badly. You can always re-encrypt later. Never encrypt the hidden boot partition. :-)
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 15:11
by Steve
@exxos Press the eject button in the top-bar of DISKS to unmount it. Or press unmount/eject in the file manager.
Re: Exxos's PiStorm blog
Posted: 16 Apr 2024 16:12
by exxos
I've found the option to restore images in Paragon now. Was easier before they totally changed the GUI !
Not sure what will happen when the SD runs out of sectors. I guess it will just moan and fail. But at that point, its probably blank sectors on the SD image anyway. I can set the stop sectors, but CBA to work it out.
Capture.PNG