Can't *write* to a hard disk, problem related to GEOM(4)?

From: Julien Gabel (jpeg_at_thilelli.net)
Date: 04/15/04

  • Next message: Paul Seniura: "I Found What The Real Problem Is... (you're gonna hate me) (re: I *really* need help PLEASE - buildworld failing on mkdep libstdc++ can't find unwind.h but it *is* there)" 
    Date: Thu, 15 Apr 2004 20:46:01 +0200 (CEST)
To: freebsd-current@freebsd.org

    Hello,

    I post to current@, since the problem *seems* to be related to GEOM.

    The first thread for this subject begin from question@, you can read it
    here:
     http://lists.freebsd.org/mailman/htdig/freebsd-questions/2004-April/\
     thread.html#43212

    I can resume my problem like that:
     - My OS release is FreeBSD 5.2.1-RELEASE-p4;
     - The disk is a 120Go/8Mo from Maxtor (UDMA133);
     - What dmesg(8) says about it:
        # grep ad10 /var/run/dmesg.boot
        GEOM: create disk ad10 dp=0xc6ab2660
        ad10: 117246MB <Maxtor 6Y120P0> [238216/16/63] at ata5-master UDMA133
     - But when I tried to create a slice on it, I get:
        # fdisk -BI ad10
        ******* Working on device /dev/ad10 *******
        fdisk: can't write fdisk partition table: Operation not permitted

    /dev/ad10 was previously part of a hardware miror (ar(4) device with a
    HighPoint HPT374 (channel 2+3) UDMA133 controller), but since it was
    broken for an unknown reason, thid drive is no more usable, even alone.
    For example, I am not be able to create a new slice on it.

    1/ I try to set the sysctl "kern.geom.debugflags" to 16, in order to
       write to it... without success.

    2/ I succeed to write on it under the 4.9 bootable CDROM (fdisk, bsdlabel,
       etc.) but when I reboot under the installed FreeBSD-5.2.1 I cannot
       access it any more again.

    It seems that 'Joan Picanyol i Puig' was in the right direction arguing
    to play with "kern.geom.debugflags", but it didn't work for me. If someone
    has an other idea to try to recover this drive...

    Thanks, 

    -- 
-jpeg.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: Paul Seniura: "I Found What The Real Problem Is... (you're gonna hate me) (re: I *really* need help PLEASE - buildworld failing on mkdep libstdc++ can't find unwind.h but it *is* there)"

    Relevant Pages

    • twe driver, 1+ terabyte array, fdisk and disklabel
      ... mention of any of these problems on the mailing lists (web ... sectors (again, as reported by fdisk). ... the field for the size of the slice I want to create. ...
      (freebsd-current)
    • nanobsd fdisk layout broken
      ... fdisk: ... Fdisk wants things to be aligned at cylinder or track boundaries ... the MBR and reserves a whole track for this, so the first slice ... normally starts at the second track of the first cylinder. ...
      (freebsd-current)
    • how to mark a slice bootable using command line
      ... to partition my da0 disk into four even-sized slices, ... Everything goes fine, except, I cannot boot from any slice other then the ... Now if I launch sysinstall and choose Configure, Fdisk, da0, I can set the ...
      (freebsd-questions)
    • Re: missing ad0p2 device while GEOM sees GPT
      ... create a new partition/slice, it'll create the device nodes right away. ... GEOM when partitions are mounted. ... > always sets the boot flag to any slice, so if you add (or define two ...
      (freebsd-current)
    • GEOM topology still+more output/USB Crashes
      ... I did appreciate the chance to review GEOM sources and the GEOM ... I did change the mbr to be at offset 0 instead of 63 which drastically ... reduced the radical/loopy slice entries. ... USB crashes both on disconnect of flash ...
      (freebsd-current)