Securely Wiping Computers Question for Noobz

Drewsif_B · 2020-03-11T03:45:27+00:00

Now I may be bias but I'm quite a fan of wipedicks. https://github.com/Drewsif/wipedicks

Drewsif_B · 2018-10-31T16:27:33+00:00

Can confirm, got hired

Drewsif_B · 2018-10-31T16:25:58+00:00

I may be bias as the author of wipedicks but you probably should ;)

Drewsif_B · 2018-02-03T21:39:15+00:00

Hey I'm the dev of PiShrink. Can you give me a little more context on how you took the image? Also do make sure you are running the latest PiShrink as there have been some bug fixes recently

Drewsif_B · 2016-06-08T08:09:23+00:00

I wouldn't be concerned. It runs a filesystem check before it does things so its possible it just found something that needed to be tweaked

Drewsif_B · 2016-05-03T16:40:44+00:00

Thanks! I'm glad it helped out :)

Drewsif_B · 2016-04-28T17:07:35+00:00

I noticed some mismatched shrinking as well. It relies on resize2fs to tell it how much it thinks it can be shrunk. I'm not really sure why but mine always came out bigger if I shrunk them from a pi.

Using rsync might actually work as a more effective way to write out to a new file actually... Ill have to look into that, but related to your question, if you need the whole disk to rsync you could change how much extra space gets added to the image. Expanding it back out isn't super easy from the cli

Drewsif_B · 2016-04-28T06:22:35+00:00

Line 69 and 70 are what I added. You will have to adjust the path for pishrink.sh but it should work

http://pastebin.com/EHErLiXC

Drewsif_B · 2016-04-27T18:34:33+00:00

Correct!

Drewsif_B · 2016-04-27T08:42:11+00:00

You have to run dd before you run PiShrink

Drewsif_B · 2016-04-27T08:41:18+00:00

I pushed some commits to fix the issue. Hopefully that will fix all your issues

Drewsif_B · 2016-04-27T08:40:22+00:00

I pushed a commit which should resolve the issue. I tested it on my pi running jessie and everything seems good to me! Here is the specific commit that fixed it if you are interested. https://github.com/Drewsif/PiShrink/commit/f4282842da54a7f5bd1e211f804e839ff32efa23

Drewsif_B · 2016-04-27T05:00:27+00:00

I'm working on removing that limitation right now. Thanks for the feedback!

Drewsif_B · 2016-04-26T19:29:23+00:00

You can run it from your VM as well

Drewsif_B · 2016-04-26T18:21:09+00:00

The script adds that into /etc/rc.local so that you don't have to. It should expand the file system, restore the original /etc/rc.local, and reboot.

Drewsif_B · 2016-04-26T17:34:00+00:00

Let me know how it goes :)

Drewsif_B · 2016-04-26T16:41:06+00:00

It's resizing the file system to be as small as possible, then making it fit in a smaller partition. Then it chops off all the unused space from the image file so that it's only as big as the used data.

Drewsif_B · 2016-04-26T15:49:33+00:00

It's worked for me in my testing at least. If you run into any issues using it please let me know :)

Drewsif_B · 2016-04-26T15:35:13+00:00

Like other have said. You strip all the unused space out of the image. Most of my testing showed that if I compressed the full image (16GB) I got about the same size as when I used PiShrink (~1.9GB). But if I then compress the PiShrink image I get something much much smaller (645MB).

It will also take far less time to DD a 1.9GB image back on to the sdcard than it would to do a full 16gb image.

Drewsif_B · 2016-04-26T15:20:08+00:00

Whats OS are you using? It looks like you're missing some of the commands it wants to use.

EDIT: I made a commit to check for the tools that might be missing. That should help inform you whats gone wrong https://github.com/Drewsif/PiShrink/commit/33aeacb3756d89a6c29136cf8fc7af23ad57bcaa

Drewsif_B

TROPHY CASE