(no subject)

itetcu_at_tecnik93.com
Date: 11/07/03

  • Next message: itetcu_at_tecnik93.com: "fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)"
    Date: Fri,  7 Nov 2003 08:28:23 +0200
    To: current@freebsd.org
    
    

    [please keep the itetcu@... cc and excuse formatting --> webmail, and
    also the typos]

    Hi,

    The quick story: after a change of the MB from a GA-7VT600 1393
    to a GA-7VT600-L, both with VIA Apollo KT600 / 8237 cipset, my
    system's preen fsck can't find the superblock on partitions other that
    / As far as I can say the fs where clean (note however that / was
    mounted read-only AFAIR).

    I've googled around half a day and the hole night with no luck. The
    system was first on a KT400/8235 mobo and i've moved it with no
    problem. What is different now ? It has been installed with the
    defaults newfs options.

    Questions:
    1. "in-core disklabel" means what is read from the disk ?
    2. The sizes are OK, the root slice is OK and I can use it, the first
    FAT32 XP partition is OK and I can boot XP, what makes the diference
    between / and the others ?
    3. If the slightly different BIOS is to blame, how to make the newfs
    when installing so that I will not have this problem again in the
    future ?
    4. Besides McKusick's paper from 44doc what other sources of
    information on ufs are there ?
    5. And, of course :-/ , how to get my data back ?

    I can provide a dumpfs and/or ffsinfo, if someone cares to see them
    (btw, they still are in 5.1 ? as in the on-line man pages thy are not)

    #fsck -p
    /dev/ad0s2a: FILESYSTEM CLEAN; SKIPPING CHECKS
    /dev/ad0s2a: clean, 89827 free (715 frags, 11139 blocks, 0.6%
    fragmentation)
    Cannot find file system superblock
    /dev/ad0s2e: CAN'T CHECK FILE SYSTEM.
    /dev/ad0s2e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    /dev/ad0s2e: CANNOT SEEK BLK: -1
    /dev/ad0s2e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    Cannot find file system superblock
    /dev/ad0s2f: CAN'T CHECK FILE SYSTEM.
    /dev/ad0s2f: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    /dev/ad0s2f: CANNOT SEEK BLK: -1
    /dev/ad0s2f: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    Cannot find file system superblock
    /dev/ad0s2d: CAN'T CHECK FILE SYSTEM.
    /dev/ad0s2d: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    Cannot find file system superblock
    /dev/ad0s2g: CAN'T CHECK FILE SYSTEM.
    /dev/ad0s2g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    /dev/ad0s2g: CANNOT SEEK BLK: -1
    /dev/ad0s2g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

    A fsck -t ufs ad0s2d gives:
    ** /dev/ad0s2d
    Cannot find file system superblock
    /dev/ad0s2d: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0,
    size 1048576

    and fsck_ffs -b 32 isn't of much help either.

    ******* Working on device /dev/ad0 *******
    parameters extracted from in-core disklabel are:
    cylinders=232578 heads=16 sectors/track=63 (1008 blks/cyl)
    Figures below won't work with BIOS for partitions not in cyl 1
    parameters to be used for BIOS calculations are:
    cylinders=232578 heads=16 sectors/track=63 (1008 blks/cyl)
    Media sector size is 512
    Warning: BIOS sector numbering starts with sector 1
    Information from DOS bootblock is:
    The data for partition 1 is:
    sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
        start 63, size 61432497 (29996 Meg), flag 0
    beg: cyl 0/ head 1/ sector 1;
    end: cyl 1023/ head 254/ sector 63
    The data for partition 2 is:
    sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
        start 61432560, size 173003985 (84474 Meg), flag 80 (active)
    beg: cyl 1023/ head 255/ sector 63;
    end: cyl 1023/ head 254/ sector 63
    The data for partition 3 is:
    <UNUSED>
    The data for partition 4 is:
    <UNUSED>
    # /dev/ad0s2:
    8 partitions:
    # size offset fstype [fsize bsize bps/cpg]
      a: 524288 0 4.2BSD 0 0 0
      b: 4194304 524288 swap
      c: 173003985 0 unused 0 0 # "raw" part,
    don't edit
      d: 1048576 4718592 4.2BSD 0 0 0
      e: 1048576 5767168 4.2BSD 0 0 0
      f: 104857600 6815744 4.2BSD 0 0 0
      g: 61330641 111673344 4.2BSD 0 0 0

    The BIOS -> LBA reads 14593/255/63 and in dmesg, next to ad0 it is
    232578/16/63.
    If I'm booting with the live CD I get:
    Offset Size(ST) End
           0.................63...............1
          63...........61432497........61432559 ad0s1
    61462560..........173003985.........23443644 ad0s2
    234436545..............2990........234439543 unused
    and the geometry 14593/255/63

    Bellow is the tail of boot -v.

    ata0: pre reset mask=03 ostat0=50 ostat2=00
    ata0-master: ATAPI 00 00
    ata0-slave: ATAPI 00 00
    ata0: after reset mask=03 stat0=50 stat1=00
    ata0-master: ATA 01 a5
    ata0: devices=01
    ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0
    ata1: pre reset mask=03 ostat0=50 ostat2=50
    ata1-master: ATAPI 14 eb
    ata1-slave: ATAPI 00 00
    ata1: after reset mask=03 stat0=00 stat1=50
    ata1-slave: ATA 01 a5
    ata1: devices=06
    ata1 at port 0x376,0x170-0x177 irq 15 on isa0
    bt0: not probed (disabled)
    cs0: not probed (disabled)
    ed0: not probed (disabled)
    fe0: not probed (disabled)
    ie0: not probed (disabled)
    le0: not probed (disabled)
    lnc0: not probed (disabled)
    pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0
    pcic1: not probed (disabled)
    sio2: not probed (disabled)
    sio3: not probed (disabled)
    sn0: not probed (disabled)
    vt0: not probed (disabled)
    isa_probe_children: probing PnP devices
    Device configuration finished.
    procfs registered
    Timecounters tick every 10.000 msec
    ipfw2 initialized, divert enabled, rule-based forwarding enabled,
    default to deny, logging limited to 100 packets/entry by default
    lo0: bpf attached
    ad0: <ST3120023A/3.33> ATA-6 disk at ata0-master
    ad0: 114472MB (234439535 sectors), 232578 C, 16 H, 63 S, 512 B
    ad0: 16 secs/int, 1 depth queue, PIO4
    ad0: piomode=12 dmamode=34 udmamode=69 cblid=1
    GEOM: new disk ad0
    ar: FreeBSD check1 failed
    ad3: <ST340016A/3.10> ATA-5 disk at ata1-slave
    ad3: 38166MB (78165360 sectors), 77545 C, 16 H, 63 S, 512 B
    ad3: 16 secs/int, 1 depth queue, PIO4
    ad3: piomode=12 dmamode=34 udmamode=69 cblid=1
    ar: FreeBSD check1 failed
    ata1-master: piomode=12 dmamode=34 udmamode=-1 dmaflag=1
    acd0: <SONY CD-RW CRX1611/TYS7> CD-RW drive at ata1 as master
    acd0: read 6890KB/s (36026KB/s) write 2755KB/s (2755KB/s), 2048KB
    buffer, PIO4
    acd0: Reads: CD-R, CD-RW, CD-DA stream, packet
    acd0: Writes: CD-R, CD-RW, test write, burnproof
    acd0: Audio: play, 256 volume levels
    acd0: Mechanism: ejectable tray, unlocked
    acd0: Medium: no/blank disc
    [0] f:00 typ:12 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:61432497
    [1] f:80 typ:165 s(CHS):1023/255/63 e(CHS):1023/254/63 s:61432560 l:
    173003985
    [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    GEOM: Configure ad0s1, start 32256 length 31453438464 end 31453470719
    GEOM: Configure ad0s2, start 31453470720 length 88578040320 end
    120031511039
    GEOM: new disk ad3
    GEOM: Configure ad0s2a, start 0 length 268435456 end 268435455
    GEOM: Configure ad0s2b, start 268435456 length 2147483648 end
    2415919103
    GEOM: Configure ad0s2c, start 0 length 88578040320 end 88578040319
    GEOM: Configure ad0s2d, start 2415919104 length 536870912 end
    2952790015
    GEOM: Configure ad0s2e, start 2952790016 length 536870912 end
    3489660927
    GEOM: Configure ad0s2f, start 3489660928 length 53687091200 end
    57176752127
    GEOM: Configure ad0s2g, start 57176752128 length 31401288192 end
    88578040319
    [0] f:80 typ:12 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:61432497
    [1] f:00 typ:12 s(CHS):1023/0/1 e(CHS):1023/254/63 s:61432560 l:
    16723665
    [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
    GEOM: Configure ad3s1, start 32256 length 31453438464 end 31453470719
    GEOM: Configure ad3s2, start 31453470720 length 8562516480 end
    40015987199
    Mounting root from ufs:/dev/ad0s2a
    start_init: trying /sbin/init

    Many Thanks,
    IOnut

    PS. for rofug - scuzati engleza de balta, da' nu mai am energie sa mai
    scriu o data in romana; e alt system fata de ala cu probl. cu md0

    _______________________________________________
    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: itetcu_at_tecnik93.com: "fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)"

    Relevant Pages

    • fsck: CANNOT SEEK BLK: -1 (after changing the mainboard)
      ... FAT32 XP partition is OK and I can boot XP, ... Cannot find file system superblock ... /dev/ad0s2e: CAN'T CHECK FILE SYSTEM. ... GEOM: new disk ad0 ...
      (freebsd-current)
    • fsck: CANNOT SEEK BLK: -1 (Cannot find file system superblock)
      ... Cannot find file system superblock ... /dev/ad0s2e: CAN'T CHECK FILE SYSTEM. ... UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. ... The data for partition 1 is: ...
      (freebsd-questions)
    • Re: Writing File System Driver & Creating Virtual Disk Drive in Windows XP [Question by a Novice
      ... strange partition it should be safe, but having a backup of it would be a ... virtual disk, but this is quite dodgy - if you make a mistake here (and ... He needs a file system. ... ***How to show partitions in windows explorer? ...
      (microsoft.public.win32.programmer.kernel)
    • Re: Is FAT32 format gone?
      ... is nolimit> to partition size re FAT32-formatted partitions. ... FAT32 file system in a WinXPenvironment,> he or she can do ... Disk> Management utility, ...
      (microsoft.public.windowsxp.general)
    • Re: interesting drive problem
      ... >>another computer's CD drive or by getting the install files from the ... >>Keep in mind that the file system you select may be an issue. ... I, too, have had issues with Red Hat's partition program, and I ... In the wake of the controversy over Red Hat Fedora, ...
      (alt.linux)