| 1 |
On Mon, Apr 3, 2017 at 2:11 PM, Harry Putnam <reader@×××××××.com> wrote: |
| 2 |
> I probably should know this, but off the top of my head I don't |
| 3 |
> remember ever running into anything like this. |
| 4 |
> |
| 5 |
> I'd like to do what ever is done to set a used disk back to the |
| 6 |
> state it was in when new... Not sure what that state is, but at least |
| 7 |
> no evidence of boot manager or fs having been installed. |
| 8 |
> |
| 9 |
> This if for something I'm doing on OS openindiana (a solaris offshoot) |
| 10 |
> and the disks are for that OS. |
| 11 |
> |
| 12 |
> The solaris milieu is somewhat behind linux in development of tools at |
| 13 |
> least in my opinion. That is why I'm asking here. |
| 14 |
> |
| 15 |
> I am a gentoo user as well, but expect I may have to boot the solaris |
| 16 |
> host with one or another linux boot ISO in order to have the tools |
| 17 |
> required. |
| 18 |
|
| 19 |
If you are not worried about securely removing all data and simply |
| 20 |
want to fool fdisk into thinking your drive is empty, use the wipefs |
| 21 |
utility. This will zero-out key bytes like the MBR, partition table, |
| 22 |
filesystem magic numbers, etc. |
| 23 |
|
| 24 |
You'll want to run it once for each partition, and then once for the |
| 25 |
whole device. |
| 26 |
|
| 27 |
wipefs -a /dev/sdx1 |
| 28 |
wipefs -a /dev/sdx2 |
| 29 |
wipefs -a /dev/sdx |
| 30 |
|
| 31 |
If you ARE worried about securely removing data, see the other replies |
| 32 |
in this thread for better options. |
Archives