partition weirdness

From: Aaron Dewell (acd_at_woods.net)
Date: 09/04/03

  • Next message: Mike Fedyk: "Re: [PATCH]O20int"
    Date:	Wed, 3 Sep 2003 18:07:52 -0600 (MDT)
    To: linux-kernel@vger.kernel.org
    
    

    Hi all,

    I'm having an odd problem with one of my disks. This disk has been through a lot
    in the last week and a half, including being re-written with dd repeatedly (from
    an image originally taken by dd), hexedited, etc. It started in an Ultrasparc,
    and now lives in a PC, has a sun disklabel, and has stuff on it that I want from
    when it was in the ultra. The ultra was running 2.4.19-rc1, the PC originally had
    the same, has since been upgraded to 2.4.22-ac1.

    The problem is this: the partition table is recognized, but the individual
    partitions (the ones I care about) are zero, that is to say, they contain the
    right size of zeros. The disk device itself, at the partition table boundaries,
    is not zero, and I can't explain this discrepency. On the disk, there seem to be
    correct and valid superblocks at the right places, they just don't exist in the
    partition devices.

    i.e. read from /dev/discs/disc2/part4 (or 6 or 7) is all zeros
    /dev/discs/disc2/part1 (/) is a valid ext3 filesystem, as is part3 and disc.
    part2 was swap, there is stuff in there, but I don't care about it.

    Of course, the ones I want the information from is 4, 6, and 7.

    A related question: If I have the dd image of the disk, shouldn't I be able to
    cut it at the right places, put that in a new file, and mount that? i.e. 'mount
    -o loop -r filename /mnt', but when I do that, e2fsck says bad magic number in
    superblock, however, e2dump -s can read it fine. (none of the other flags to
    e2dump works, however.) If I can slice up the disk into files and read those,
    that works too, so solving either problem is adequate.

    Any suggestions? I appreciate any help.

    Thanks!

    Aaron

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Mike Fedyk: "Re: [PATCH]O20int"

    Relevant Pages

    • Re: Linux community software-update-anarchy polemic
      ... Remember, I'm just a monkey. ... That implies that if you have one disk per partition, ... Trust the kernel or don't trust the kernel, but either way, both ...
      (comp.os.linux.misc)
    • SUMMARY: Moving /usr From Under Root "/" To Its Own Partition
      ... One of the reasons for doing this is to end up with a smaller root ... Install the boot block and boot off the new drive. ... " In order for the root partition to be fscked and remounted ... D> temporarily on the existing disk. ...
      (SunManagers)
    • Re: Two "expert" issues I must solve before upgading
      ... I think backups are different than the other fluff you suggest - more ... out there who had a disk crash and had to start from scratch. ... >image of your current Windows 98 OS partition. ... you can restore the disk image and get back quickly ...
      (microsoft.public.windowsxp.newusers)
    • Re: Found the chkdsk log [STOP error, data unviewable etc...]
      ... The type of the file system is NTFS. ... CHKDSK is recovering lost files. ... 33013543 KB total disk space. ... partition, etc. Oh well... ...
      (microsoft.public.win2000.file_system)
    • Re: Two "expert" issues I must solve before upgading
      ... > I need an imaging program for my full backups, ... No. Don't consider disk images as file backup. ... image of your current Windows 98 OS partition. ... changes then save a disk image. ...
      (microsoft.public.windowsxp.newusers)