Re: Corrupted OS

On Fri, Mar 16, 2007 at 01:33:42PM -0700, Drew Jenkins wrote:

I believe you misunderstand. I have 3 disks:
2 are SCSI RAID and are 80 GB each
1 is not and is 500 GB
I don't actually need the 500 GB now. I haven't even used up the 80 GB HD's.
So I can wipe the 500 GB clean. I don't have to keep data on it at all.
But...can I do that remotely, and run those commands remotely, with that
disk being unmounted, and if so...how?

You can do it remotely. Once everything on that disk is unmounted
and unreferenced, then fdisk and bsdlabel will be happy to work on it.

The best documentation for that is down in the examples of
the bsdlabel man page.

dd if=/dev/zero of=/dev/da0 bs=512 count=32
fdisk -BI da0
dd if=/dev/zero of=/dev/da0s1 bs=512 count=32
bsdlabel -w -B da0s1
bsdlabel -e da0s1

Change the device names to be what yours really are (da0 may be ad3
or something. I also upped the count on the dd, but it doesn't matter.

Follow this with a newfs for each partition except swap that you
create on this disk.


The problem *is* a corrupt OS. I currently don't have any data on
that 500 GB HD. And the problems persist. Sorry to have confused you.
Are things clearer now?

Well, it seems clear that there is no problem with the 500 GB disk.
You can just fdisk it. If you want, write a few blocks of zeros to
it first to make sure the system believes it clean if you want. Probably
shouldn't need to, though.
dd if=/dev/zero of=/dev/extra-drive-name bs=512 count=250

As for the corrupt OS, I don't understand what that is and why
you think that or whatever.

////jerry

TIA,
Drew2

Jerry McAllister <jerrymc@xxxxxxx> wrote: On Fri, Mar 16, 2007 at 09:12:02AM -0700, Drew Jenkins wrote:

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: seeking help on "adding a disk"
    ... partition and mount it on directory /images. ... fdisk: ... the last command is trying to write past the edge of the disk. ... It looks like things worked up to the bsdlabel which didn't do anything. ...
    (freebsd-questions)
  • Re: Corrupted OS
    ... Once everything on that disk is unmounted ... then fdisk and bsdlabel will be happy to work on it. ... The problem *is* a corrupt OS. ... Get your game face on with the latest PS3 news and previews at Yahoo! ...
    (freebsd-questions)
  • Re: Corrupted OS
    ... then fdisk and bsdlabel will be happy to work on it. ... bsdlabel -w -B da0s1 ... As for the corrupt OS, I don't understand what that is and why ...
    (freebsd-questions)
  • fdisk, bsdlabel and hidden tricks
    ... recently i was playing with fdisk and bsdlabel to create ... a new FreeBSD slice in the MBR on the same disk i ... create partitions on it on a second disk. ... could have saved the reboot) to let the bsdlabel do the work. ...
    (freebsd-stable)
  • Re: Error 16: Inconsistent filesystem structure
    ... My preference would be a /home partition to protect my data ... Here is a copy of the output of fdisk -l and fdisk /dev/sdb with x then ... I used the Negus Fedora 7 book's Live cd. ... Disk /dev/sdb: 200.0 GB, 200049647616 bytes ...
    (Fedora)