Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: ext3 partition screwed up :(

  1. #1
    Join Date
    Aug 2007
    Beans
    6

    ext3 partition screwed up :(

    So i need some help BADLY. i've got 5 hard drives in my linux box. it's set as a file server and each hard drive is full of data (i know i need some redundancy ). so one of the hard drives, named hdd1, is a 500 gig drive holding all of my music and a bunch of movies. i was using a windows program called fixtune to rename all the id3 tags of the mp3's until half way through it errored out and said that it couldn't see the drive anymore. so i checked the linux box and sure enough, i couldn't get into the drive either. so i restarted the box, and tried remounting the drive. it gave this error:

    Cannot Mount Volume.
    Unable to mount the volume
    Details
    mount: wrong fs type, bad option, bad superblock on /dev/hdd1, missing codepage or helper program, or other error in some cases useful info is found in syslog -try dmesg | tail or so

    i'm too afraid to use fsck or e2fsck, since i don't want to LOSE the data at all. any suggestions would be very much appreciated. just so you guys already have it, i have my fdisk and dmesg | tail output below:

    shhtephe@shhtephe-fileserver:~$ sudo fdisk -l
    Disk /dev/hdc: 250.0 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x0a77f3c8

    Device Boot Start End Blocks Id System
    /dev/hdc1 * 1 30401 244196001 83 Linux

    Disk /dev/hdd: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x000098ec

    Device Boot Start End Blocks Id System
    /dev/hdd1 1 60801 488384001 83 Linux

    Disk /dev/sda: 400.0 GB, 400088457216 bytes
    255 heads, 63 sectors/track, 48641 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x2052474d

    This doesn't look like a partition table
    Probably you selected the wrong device.

    Device Boot Start End Blocks Id System
    /dev/sda1 ? 410 119791 958924038+ 7 HPFS/NTFS
    Partition 1 does not end on cylinder boundary.
    /dev/sda2 ? 121585 234786 909287957+ 43 Unknown
    Partition 2 does not end on cylinder boundary.
    /dev/sda3 ? 14052 14052 5 72 Unknown
    Partition 3 does not end on cylinder boundary.
    /dev/sda4 164483 164486 25945 0 Empty
    Partition 4 does not end on cylinder boundary.

    Partition table entries are not in disk order

    Disk /dev/sdb: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x158aa0f9

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 60802 488384512 7 HPFS/NTFS

    Disk /dev/sdc: 40.0 GB, 40000000000 bytes
    255 heads, 63 sectors/track, 4863 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x8a9a8a9a

    Device Boot Start End Blocks Id System
    /dev/sdc1 * 1 4658 37415353+ 83 Linux
    /dev/sdc2 4659 4863 1646662+ 5 Extended
    /dev/sdc5 4659 4863 1646631 82 Linux swap / Solaris


    shhtephe@shhtephe-fileserver:~$ dmesg | tail
    [122456.050042] [drm] Initialized drm 1.1.0 20060810
    [122456.066434] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
    [122456.066759] [drm] Initialized i915 1.6.0 20060119 on minor 0
    [122456.068128] set status page addr 0x00033000
    [122473.690791] UDF-fs: No VRS found
    [122602.737482] kjournald starting. Commit interval 5 seconds
    [122602.737489] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
    [122602.748450] EXT3 FS on hdc1, internal journal
    [122602.748460] EXT3-fs: mounted filesystem with ordered data mode.
    [225813.097422] ext3: No journal on filesystem on hdd1


    --
    -Stephen Bailey

    p.s. if there's anything specific you'd like me to do, or run, let me know what it is, and i'll be sure to do it, and get back to this thread asap.


    p.p.s. i sure hope all the hardy heron business doesn't take the steam out of my thread/question!

  2. #2
    Join Date
    Apr 2008
    Beans
    23

    Re: ext3 partition screwed up :(

    Quote Originally Posted by xpingux View Post
    So i need some help BADLY. i've got 5 hard drives in my linux box. it's set as a file server and each hard drive is full of data (i know i need some redundancy ). so one of the hard drives, named hdd1, is a 500 gig drive holding all of my music and a bunch of movies. i was using a windows program called fixtune to rename all the id3 tags of the mp3's until half way through it errored out and said that it couldn't see the drive anymore. so i checked the linux box and sure enough, i couldn't get into the drive either. so i restarted the box, and tried remounting the drive. it gave this error:

    Cannot Mount Volume.
    Unable to mount the volume
    Details
    mount: wrong fs type, bad option, bad superblock on /dev/hdd1, missing codepage or helper program, or other error in some cases useful info is found in syslog -try dmesg | tail or so

    i'm too afraid to use fsck or e2fsck, since i don't want to LOSE the data at all. any suggestions would be very much appreciated. just so you guys already have it, i have my fdisk and dmesg | tail output below:

    shhtephe@shhtephe-fileserver:~$ sudo fdisk -l
    Disk /dev/hdc: 250.0 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x0a77f3c8

    Device Boot Start End Blocks Id System
    /dev/hdc1 * 1 30401 244196001 83 Linux

    Disk /dev/hdd: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x000098ec

    Device Boot Start End Blocks Id System
    /dev/hdd1 1 60801 488384001 83 Linux

    Disk /dev/sda: 400.0 GB, 400088457216 bytes
    255 heads, 63 sectors/track, 48641 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x2052474d

    This doesn't look like a partition table
    Probably you selected the wrong device.

    Device Boot Start End Blocks Id System
    /dev/sda1 ? 410 119791 958924038+ 7 HPFS/NTFS
    Partition 1 does not end on cylinder boundary.
    /dev/sda2 ? 121585 234786 909287957+ 43 Unknown
    Partition 2 does not end on cylinder boundary.
    /dev/sda3 ? 14052 14052 5 72 Unknown
    Partition 3 does not end on cylinder boundary.
    /dev/sda4 164483 164486 25945 0 Empty
    Partition 4 does not end on cylinder boundary.

    Partition table entries are not in disk order

    Disk /dev/sdb: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x158aa0f9

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 60802 488384512 7 HPFS/NTFS

    Disk /dev/sdc: 40.0 GB, 40000000000 bytes
    255 heads, 63 sectors/track, 4863 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x8a9a8a9a

    Device Boot Start End Blocks Id System
    /dev/sdc1 * 1 4658 37415353+ 83 Linux
    /dev/sdc2 4659 4863 1646662+ 5 Extended
    /dev/sdc5 4659 4863 1646631 82 Linux swap / Solaris


    shhtephe@shhtephe-fileserver:~$ dmesg | tail
    [122456.050042] [drm] Initialized drm 1.1.0 20060810
    [122456.066434] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
    [122456.066759] [drm] Initialized i915 1.6.0 20060119 on minor 0
    [122456.068128] set status page addr 0x00033000
    [122473.690791] UDF-fs: No VRS found
    [122602.737482] kjournald starting. Commit interval 5 seconds
    [122602.737489] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
    [122602.748450] EXT3 FS on hdc1, internal journal
    [122602.748460] EXT3-fs: mounted filesystem with ordered data mode.
    [225813.097422] ext3: No journal on filesystem on hdd1


    --
    -Stephen Bailey

    p.s. if there's anything specific you'd like me to do, or run, let me know what it is, and i'll be sure to do it, and get back to this thread asap.


    p.p.s. i sure hope all the hardy heron business doesn't take the steam out of my thread/question!


    Just trying to understand....

    How were you editing the files in Windows? Over samba? With a Windows program that mounts ext2/3?


    What does this show? (man tune2fs for explanation)
    tune2fs -l /dev/hdd1

  3. #3
    Join Date
    Aug 2007
    Beans
    6

    Re: ext3 partition screwed up :(

    Yes i have the linux box set up as a fileserver with samba. the drives are shared.all my other drives are running perfectly fine in the same environment.


    i ran tune2fs, and got this:

    Code:
    tune2fs 1.40.2 (12-Jul-2007)
    tune2fs: Permission denied while trying to open /dev/hdd1
    Couldn't find valid filesystem superblock.
    
    i then tried it with sudo and got a lot more: 
    
    shhtephe@shhtephe-fileserver:~$ sudo tune2fs -l /dev/hdd1
    [sudo] password for shhtephe:
    tune2fs 1.40.2 (12-Jul-2007)
    Filesystem volume name:   <none>
    Last mounted on:          <not available>
    Filesystem UUID:          3b5faca6-f648-46ba-a8fc-4504ec35c8e2
    Filesystem magic number:  0xEF53
    Filesystem revision #:    1 (dynamic)
    Filesystem features:      resize_inode dir_index filetype sparse_super large_file
    Filesystem flags:         signed directory hash
    Default mount options:    (none)
    Filesystem state:         not clean with errors
    Errors behavior:          Continue
    Filesystem OS type:       Linux
    Inode count:              61063168
    Block count:              122096000
    Reserved block count:     6104800
    Free blocks:              120129064
    Free inodes:              61063157
    First block:              0
    Block size:               4096
    Fragment size:            4096
    Reserved GDT blocks:      994
    Blocks per group:         32768
    Fragments per group:      32768
    Inodes per group:         16384
    Inode blocks per group:   512
    Filesystem created:       Sun Sep 30 13:15:19 2007
    Last mount time:          n/a
    Last write time:          Thu Apr 17 17:39:17 2008
    Mount count:              0
    Maximum mount count:      34
    Last checked:             Sun Sep 30 13:15:19 2007
    Check interval:           15552000 (6 months)
    Next check after:         Fri Mar 28 13:15:19 2008
    Reserved blocks uid:      0 (user root)
    Reserved blocks gid:      0 (group root)
    First inode:              11
    Inode size:               128
    Default directory hash:   tea
    Directory Hash Seed:      94aca0af-394b-4bc3-a3e2-26f745b87656
    Journal backup:           inode blocks
    boy that's a lot. does this help at all?

  4. #4
    Join Date
    Jun 2006
    Location
    Solihull, UK
    Beans
    1,413

    Re: ext3 partition screwed up :(

    This immediately jumps out:
    Code:
    Filesystem state:         not clean with errors
    I'm afraid you're going to have to run fsck on this volume. Just make sure it is completely unmounted first (which will probably be the case, as you can't mount it anyway).

  5. #5
    Join Date
    Aug 2007
    Beans
    6

    Re: ext3 partition screwed up :(

    well i'm seeing a ton of this:

    Inode 5147898, i_size is 6444458803776527079, should be 0. Fix<y>? yes

    which makes me nervous because from what i know about hard drive file allocation, that means i'm deleting stuff.



    am i wrong? is this doing good things to fix my file system?

  6. #6
    Join Date
    Jun 2006
    Location
    Solihull, UK
    Beans
    1,413

    Re: ext3 partition screwed up :(

    Your filesystem is already broken, so I'm not sure what other choice you have to be honest

  7. #7
    Join Date
    Aug 2007
    Beans
    6

    Re: ext3 partition screwed up :(

    so i cleaned the drive, and this is the new output of tunefs


    Code:
    shhtephe@shhtephe-fileserver:~$ sudo tune2fs -l /dev/hdd1
    tune2fs 1.40.2 (12-Jul-2007)
    Filesystem volume name:   <none>
    Last mounted on:          <not available>
    Filesystem UUID:          3b5faca6-f648-46ba-a8fc-4504ec35c8e2
    Filesystem magic number:  0xEF53
    Filesystem revision #:    1 (dynamic)
    Filesystem features:      resize_inode dir_index filetype sparse_super large_file
    Filesystem flags:         signed directory hash
    Default mount options:    (none)
    Filesystem state:         clean
    Errors behavior:          Continue
    Filesystem OS type:       Linux
    Inode count:              61063168
    Block count:              122096000
    Reserved block count:     6104800
    Free blocks:              11959694
    Free inodes:              61052666
    First block:              0
    Block size:               4096
    Fragment size:            4096
    Reserved GDT blocks:      994
    Blocks per group:         32768
    Fragments per group:      32768
    Inodes per group:         16384
    Inode blocks per group:   512
    Filesystem created:       Sun Sep 30 13:15:19 2007
    Last mount time:          n/a
    Last write time:          Fri Apr 25 12:54:23 2008
    Mount count:              0
    Maximum mount count:      34
    Last checked:             Fri Apr 25 12:54:23 2008
    Check interval:           15552000 (6 months)
    Next check after:         Wed Oct 22 12:54:23 2008
    Reserved blocks uid:      0 (user root)
    Reserved blocks gid:      0 (group root)
    First inode:              11
    Inode size:               128
    Default directory hash:   tea
    Directory Hash Seed:      94aca0af-394b-4bc3-a3e2-26f745b87656
    Journal backup:           inode blocks
    as you can see, it's "clean" now. which might or might not be a good thing, since it still won't mount :S

    so i dmesg | tail'd and here's the new output

    shhtephe@shhtephe-fileserver:~$ dmesg | tail
    [122602.737482] kjournald starting. Commit interval 5 seconds
    [122602.737489] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
    [122602.748450] EXT3 FS on hdc1, internal journal
    [122602.748460] EXT3-fs: mounted filesystem with ordered data mode.
    [225813.097422] ext3: No journal on filesystem on hdd1
    [225901.442891] ext3: No journal on filesystem on hdd1
    [348532.633932] ext3: No journal on filesystem on hdd1
    [439217.233931] ext3: No journal on filesystem on hdd1
    [439265.746406] ext3: No journal on filesystem on hdd1
    [439733.201098] ext3: No journal on filesystem on hdd1

    are we getting anywhere?

  8. #8
    Join Date
    Jun 2006
    Location
    Solihull, UK
    Beans
    1,413

    Re: ext3 partition screwed up :(

    Try:
    Code:
    sudo tune2fs -j /dev/hdd1
    ...then try mounting it again

    Out of interest, how are you mounting the drive? Is it using a line in your fstab? If so, could you post it here? what error do you get now when you try to mount?
    Last edited by chrisccoulson; April 26th, 2008 at 10:21 AM.

  9. #9
    Join Date
    Aug 2007
    Beans
    6

    Re: ext3 partition screwed up :(

    everything has been recovered.



    i owe you a friggin coke, dude.



    thanks a ton.

  10. #10
    Join Date
    Apr 2007
    Location
    Leura, Australia
    Beans
    Hidden!
    Distro
    Ubuntu Gnome 13.10 Saucy Salamander

    Angry Re: ext3 partition screwed up :(

    Hi, I'm having a similar problem.

    - Trying to mount /dev/sdb1 (which is a ext3 external hard drive partition, connected by firewire).
    - Has always mounted with no problems in the past.
    - Getting same error as above "Cannot mount volume..." etc.
    - Rebooted with no success
    - Have checked out https://bugs.launchpad.net/ubuntu/+bug/226215 which is a similar issue, and posted a call for help there too
    -
    Code:
    tune2fs -l
    shows:
    Last mounted on: <not available>
    Filesystem state: clean
    Last write time: Sun May 4 13:53:39 2008
    ...among other things
    -
    Code:
    sudo tune2fs -j /dev/sdb1
    gives the following:
    tune2fs 1.40.8 (13-Mar-2008)
    The filesystem already has a journal.

    Is there a solution - the files are EXTREMELY important to me.

    Thanks.

Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •