Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: [SOLVED] problem mounting partition after data recovery

  1. #1
    Join Date
    Sep 2007
    Beans
    183

    Question [SOLVED] problem mounting partition after data recovery

    Hi,
    I had problems with a faulty hard disk, after data recovery on a new HD it does not mount the ex3 filesystem with this error message:
    Code:
    mount: wrong fs type, bad option, bad superblock on dev/sdb1, missing codepage or other helper program, or other errors ........
    The dmesg gives me this:
    Code:
    [  304.704000] journal_bmap: journal block not found at offset 0 on sdb1
    [  304.704000] journal_init_inode: Cannnot locate journal superblock
    [  304.704000] EXT3-fs: Could not load journal inode
    I did cat /etc/mtab to make sure that it is not mounted on somewhere else:
    Code:
    /dev/sda9 / ext3 rw,errors=remount-ro 0 0
    proc /proc proc rw,noexec,nosuid,nodev 0 0
    /sys /sys sysfs rw,noexec,nosuid,nodev 0 0
    varrun /var/run tmpfs rw,noexec,nosuid,nodev,mode=0755 0 0
    varlock /var/lock tmpfs rw,noexec,nosuid,nodev,mode=1777 0 0
    udev /dev tmpfs rw,mode=0755 0 0
    devshm /dev/shm tmpfs rw 0 0
    devpts /dev/pts devpts rw,gid=5,mode=620 0 0
    lrm /lib/modules/2.6.22-15-generic/volatile tmpfs rw 0 0
    /dev/sda8 /home reiserfs rw 0 0
    /dev/sda1 /media/sda1 fuseblk rw,nosuid,nodev,allow_other,default_permissions,blksize=4096 0 0
    /dev/sda5 /media/sda5 fuseblk rw,nosuid,nodev,allow_other,default_permissions,blksize=4096 0 0
    /dev/sda6 /media/sda6 fuseblk rw,nosuid,nodev,allow_other,default_permissions,blksize=4096 0 0
    /dev/sda7 /media/sda7 ext3 rw 0 0
    securityfs /sys/kernel/security securityfs rw 0 0
    binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
    The first lines shows the error, do not know what is wrong with it!

    And here is the output of the vol_id /dev/sdb1:
    Code:
    ID_FS_USAGE=filesystem
    ID_FS_TYPE=ext3
    ID_FS_VERSION=1.0
    ID_FS_UUID=4fce5b0b-5ef2-4e58-9aaf-28fa5575e67c
    ID_FS_UUID_ENC=4fce5b0b-5ef2-4e58-9aaf-28fa5575e67c
    ID_FS_LABEL=
    ID_FS_LABEL_ENC=
    ID_FS_LABEL_SAFE=
    Any helps would be greatly appreciated.
    Last edited by pooyaplus; July 19th, 2008 at 07:38 AM.

  2. #2
    Join Date
    Sep 2007
    Beans
    183

    Re: problem mounting partition after data recovery

    Bump

  3. #3
    Join Date
    Sep 2007
    Beans
    183

    Re: problem mounting partition after data recovery

    Bump... Any body?

  4. #4
    Join Date
    Sep 2007
    Beans
    183

    Unhappy Re: problem mounting partition after data recovery


  5. #5
    Join Date
    Jun 2006
    Beans
    7,419
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: problem mounting partition after data recovery

    why are you trying to mount a partition on a faulty drive? You've recovered the data, so I don't understand...maybe I've misunderstood...

  6. #6
    Join Date
    Sep 2007
    Beans
    183

    Re: problem mounting partition after data recovery

    Hi,
    Thanks for the reply. But it is not a faulty HD. I have recovered them on a new hard disk. But the problem is that I can not have access to the data!! Funny (sad) but true. The only way I can see them is by a windows app called Diskintervals that browses the ext3/ext2 partition in windows.

  7. #7
    Join Date
    Jun 2006
    Beans
    7,419
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: problem mounting partition after data recovery

    Let me get this straight: you copied the files and folders from the partition on the faulty drive to an ext3 partition (sdb1?) on the new drive, but get errors mounting it, and the only way to access the files is by 'DiskIntervals' app? Or did you clone/make an image of the whole partition and copy it to sdb1?

  8. #8
    Join Date
    Sep 2007
    Beans
    183

    Question Re: problem mounting partition after data recovery

    Actually the recovery process has been done by someone else and I do not exactly what has happened in between. But here is the whole story:
    The data was on an old ext3 partitioned HD, and it got serious bad sectors after a power cut. Data was recovered on a new HD.

    Ubuntu can not mount the partition but Diskintervals in windows knows it as an ext3 file system and shows the data.

    The question is why I can not mount it here in ubuntu and how I can do it?

    Thanks.

  9. #9
    Join Date
    Mar 2008
    Beans
    4,715
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: problem mounting partition after data recovery

    This is just a guess, but perhaps sdb1 is an ext2 partition instead of ext3. The only difference between ext2 and ext3 is the lack of a journal in ext2.
    dmesg complains, "journal_bmap: journal block not found at offset 0 on sdb1" which is consistent with this guess.

    Perhaps try opening a terminal and typing

    Code:
    sudo mkdir /media/sdb1
    sudo mount /dev/sdb1 /media/sdb1
    and if that does not work

    Code:
    sudo mount -t ext2 /dev/sdb1 /media/sdb1
    If it works, the next step would be to edit /etc/fstab to make the change permanent. If it doesn't work, it might be helpful to take a look at /etc/fstab. So, in any case, please post
    Code:
    cat /etc/fstab

  10. #10
    Join Date
    Sep 2007
    Beans
    183

    Lightbulb Re: problem mounting partition after data recovery

    Quote Originally Posted by unutbu View Post
    This is just a guess, but perhaps sdb1 is an ext2 partition instead of ext3. The only difference between ext2 and ext3 is the lack of a journal in ext2.
    dmesg complains, "journal_bmap: journal block not found at offset 0 on sdb1" which is consistent with this guess.

    Perhaps try opening a terminal and typing

    Code:
    sudo mkdir /media/sdb1
    sudo mount /dev/sdb1 /media/sdb1
    and if that does not work

    Code:
    sudo mount -t ext2 /dev/sdb1 /media/sdb1
    If it works, the next step would be to edit /etc/fstab to make the change permanent. If it doesn't work, it might be helpful to take a look at /etc/fstab. So, in any case, please post
    Code:
    cat /etc/fstab
    Hey, nice shot buddy. Thanks that worked.

    But there is one more thing. How I can set it permanently as you pointed out? I have connected the hard disk to another PC running ubuntu. Can I keep the ext2 (!) partition and have a clean new install of ubuntu on the rest of the hard space?

    Here is the fstab:

    Code:
    # /etc/fstab: static file system information.
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    # /dev/sda9
    UUID=d271ff7f-ed90-4a84-9d85-92771e89054b /               ext3    defaults,errors=remount-ro 0       1
    # /dev/sda8
    UUID=7815bda6-3732-44fd-87b7-8302a72394c9 /home           reiserfs defaults        0       2
    # /dev/sda1
    UUID=245C76165C75E2CA /media/sda1     ntfs    defaults,nls=utf8,umask=007,gid=46 0       1
    # /dev/sda5
    UUID=9AB41CCBB41CABAF /media/sda5     ntfs    defaults,nls=utf8,umask=007,gid=46 0       1
    # /dev/sda6
    UUID=D228234928232BC3 /media/sda6     ntfs    defaults,nls=utf8,umask=007,gid=46 0       1
    # /dev/sda7
    UUID=37db42bc-f81b-4c51-a814-3f059df3ae6c /media/sda7     ext3    defaults        0       2
    # /dev/sda10
    UUID=68365cb6-6524-463b-9ac4-62a69a8d94c7 none            swap    sw              0       0
    /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
    /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
    Thanks again.

Page 1 of 3 123 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
  •