Re: Using a hard drive without partitions

From: Gary W. Swearingen (garys_at_opusnet.com)
Date: 07/30/05

  • Next message: Gary W. Swearingen: "Re: bsdlabel question.."
    To: Nikolas Britton <nikolas.britton@gmail.com>
    Date: Sat, 30 Jul 2005 14:27:28 -0700
    
    

    Nikolas Britton <nikolas.britton@gmail.com> writes:

    > But in FreeBSD your disk needs a slice otherwise it's not compatable
    > with fdisk / bsdlabel / growfs... I think.

    One of the main reasons for using a DD disk is so you don't have to
    mess with those things; they are of no use on a DD disk (assuming that
    you cover the whole disk with the file system).

    You haven't said how you plan to use this disk. If you're going to
    use it for raw data, you don't need disk labels or file systems or
    anything, you just write (eg, >) and read (eg, <) from it, or tell
    your custom driver about it. Do you want to mount it for files?

    >> You've got a standard partition table with the s1 entry in use, which
    >> is not "dangerous". The FAQ has an entry on DD disks.
    >
    > But it is "dangerous" because it starts at sector 0. I've read that
    > FAQ as well as greg's book, Lucas's book, unix power tools, the man
    > pages, handbook, etc. I will reread them again.

    WHAT is dangerous? Yes, a DD disk is (more) dangerous, but you don't
    have a DD disk. Your s1 doesn't start at sector 0 and so it isn't
    considered dangerous. Your s1 probably starts at the 64th sector.
    And I'll take a guess that your "newfs /dev/ad0s1" (if it works at
    all) is starting the new filesystem at least 16 sectors further on,
    after the disk label area (which it probably assumes is there). The
    newfs manpage says that the disk must first be labeled.

    > I'm going to be working on this server today and I'll post some of the
    > details of fdisk, bsdlabel, etc. to see if I can help clarify things.

    Yeah, I'd like to see your "bsdlabel ad0s1"; I'm wondering if you have
    a disk label with "c" when you think you have no disk label. Can you
    mount /dev/ad0s1c? Can you mount dev/ad0s1?

    Seems to me you'd either want to be safe and use "ad0s1a" or live
    dangerously and use "ad0a" or even "ad0" if it seems to work.
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: Gary W. Swearingen: "Re: bsdlabel question.."

    Relevant Pages

    • Trying to mount CF card
      ... to mount it, the mount fails. ... Checking we can access the last sector of the filesystem ... Checking for unused clusters. ... oddly formatted disk or no--though it comes up fine under Windows. ...
      (Debian-User)
    • SUMMARY: Cant Read Disk Label (Thanks Mike!)
      ... Thanks to Mike David Chanslor for helping me to fix my "Can't Read Disk ... We now stick to Seagate IDE drives ... Subject: Can't read disk label. ... I am trying to install Solaris 8 on a Sun Ultra 10 Sparc ...
      (SunManagers)
    • Re: newfs and mount vs. half-baked disks
      ... > examine to recover a crashed disk), and any overaul by GEOM would have ... > somewhere outside the superblocks. ... unllikely that it will be the disk label as FreeBSD is looking to go to ... a sector size of 16K are not unreasonable and this is sufficent ...
      (freebsd-arch)
    • Re: Path syntax in VBA
      ... the path at all -- Windows doesn't "understand" disk labels in paths ... then use the corresponding drive letter in the save path. ... >Jonathan West - Word MVP ... >> The question is can I use the disk label in the path instead of the drive ...
      (microsoft.public.word.vba.general)
    • Re: newfs and mount vs. half-baked disks
      ... > where the disk contents is disposable and you re-newfs it a lot. ... > metadata newfs does when it starts. ... > newfs should erase all the primary metadata for the old filesystem ... You cannot depend on the disk label as the disklabel is going away ...
      (freebsd-arch)