Page 1 of 4 123 ... LastLast
Results 1 to 10 of 35

Thread: large ext HDD problem

  1. #1
    Join Date
    Jun 2013
    Beans
    33

    Angry large ext HDD problem

    I've been through all kinds of forums for about a week now and I've found dozens of threats with similar problems but no one seems to have found a solution yet.

    Problem:
    I've been using my 3TB ext HDD for a couple of years now with absolutely no problem.
    Since it was formated in FAT32 from the day I bought it and I couldn't use it with files bigger than 4GB, I've decided to format it in NTFS.
    I wanted a one-partition disk since I only store media files on it.

    1st format and the disk wouldn't mount. After googling around I find out that I had to do a GPT format for partitions over 2TB.
    Ok. So I did that and formatted it as ext4. I started copying back my files and everything seemed ok.
    When I next booted my desktop, this message came up once again:
    Error mounting /dev/sdh1 at /media/george/3TB: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdh1" "/media/george/3TB"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdh1,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so
    The output of the dmesg | tail:
    george@george-MS-7091:~$ dmesg | tail
    [ 919.249043] sd 9:0:0:0: [sdd] 732566642 4096-byte logical blocks: (3.00 TB/2.72 TiB)
    [ 919.251026] sd 9:0:0:0: [sdd] No Caching mode page present
    [ 919.251036] sd 9:0:0:0: [sdd] Assuming drive cache: write through
    [ 919.295666] sdd: sdd1
    [ 919.297016] sd 9:0:0:0: [sdd] 732566642 4096-byte logical blocks: (3.00 TB/2.72 TiB)
    [ 919.299020] sd 9:0:0:0: [sdd] No Caching mode page present
    [ 919.299028] sd 9:0:0:0: [sdd] Assuming drive cache: write through
    [ 919.299034] sd 9:0:0:0: [sdd] Attached SCSI disk
    [ 919.665826] EXT4-fs (sdd1): ext4_check_descriptors: Checksum for group 3968 failed (44912!=0)
    [ 919.665833] EXT4-fs (sdd1): group descriptors corrupted!

    It's been really frustrading searching for about a week on the internet.
    Please don't redirect me to other threads if there isn't really a solution to THIS problem and not to "similar" problems. I've pretty much read everything I found this week and no one seems to be able to help.

    Additional info:
    - I use only ubuntu 13.04
    - I did a disk check with gparted which tried to fix any problems but it failed to do that
    - I use 3 other external disks with no problem for a long time now.
    One is 400GB formated in FAT32, 2nd is a 500GB NTFS formated and 2rd is a 120GB previously NTFS formated.
    These 3 were never manual mounted or unmounted and never had any problem. I just plug them in and they just work. So did the large 3TB HDD until now.
    I don't think I did anything wrong when formatting it since I've already formated the other 2 (NTFS formated disks) I mentioned above.

    - Here is the info from gparted when I double click on the disk. (Sorry for the Greek and sorry for not having uploaded the whole pic. I just could't move it up further or drag it...)
    Attached Images Attached Images

  2. #2
    Join Date
    Oct 2009
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: large ext HDD problem that nobody seems to be able to help?!

    What's with the "uhelper=udisks2,nodev,nosuid" part in the mount command?

    Have you already tried running fsck on the drive? Dmesg says the file system is damaged and that is used to repair ext file systems.

    Code:
    sudo fsck -fC /dev/sdXY
    Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide

    Tomorrow's an illusion and yesterday's a dream, today is a solution...

  3. #3
    Join Date
    Aug 2013
    Beans
    90

    Re: large ext HDD problem that nobody seems to be able to help?!

    First, I suggest reading the Wikipedia article http://en.wikipedia.org/wiki/GUID_Partition_Table

    Second, from reading the article, your options for mounting the GPT partitioned disk seem to be incorrect, which is resulting in the error.

  4. #4
    Join Date
    Jun 2013
    Beans
    33

    Re: large ext HDD problem that nobody seems to be able to help?!

    Don't know what's with the "uhelper=udisks2,nodev,nosuid" part in the mount command...

    I've already done sudo fsck -fC /dev/sdh1 sometime the past days with no luck as I can recall.
    Doing it right now once again. This is what came up so far:

    george@george-MS-7091:~$ sudo fsck -fC /dev/sdh1
    Code:
    [sudo] password for george: 
    fsck from util-linux 2.20.1
    e2fsck 1.42.5 (29-Jul-2012)
    ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
    fsck.ext4: Group descriptors look bad... trying backup blocks...
    Superblock has an invalid journal (inode 8).
    Clear<y>? yes
    *** ext3 journal has been deleted - filesystem is now ext2 only ***
    and then multiple of these: (Εκκαθάριση = clear, ναι = yes)
    Code:
    Error while reading over extent tree in inode 134233537: Corrupt extent header
    Clear inode<ν>? ναι
    Inode 134233537, i_blocks is 1606652, should be 0.  Διόρθωση<ν>? ναι
    Inode 134233553 was part of the orphaned inode list.  FIXED.
    Inode 134233553 has compression flag set on filesystem without compression support.  Εκκαθάριση<ν>? ναι
    and that: (Διόρθωση = Fix)
    Code:
    Error while reading over extent tree in inode 134233585: Corrupt extent header
    Clear inode<ν>? ναι
    Inode 134233585, i_blocks is 1606655, should be 0.  Διόρθωση<ν>? ναι
    Inode 134233601 was part of the orphaned inode list.  FIXED.
    Error while reading over extent tree in inode 134233601: Corrupt extent header
    Clear inode<ν>? ναι
    Inode 134233601, i_blocks is 1606656, should be 0.  Διόρθωση<ν>? ναι
    yyInode 134234135 has illegal block(s).  Εκκαθάριση<ν>? ναι
    Illegal block #397329 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #398353 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #399377 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #400401 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #401425 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #402449 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #403473 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #404497 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #405521 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #406545 (1378679529) in inode 134234135.  CLEARED.
    Illegal block #407569 (1378679529) in inode 134234135.  CLEARED.
    Too many illegal blocks in inode 134234135.
    Clear inode<ν>? ναι
    and now it's doing this:
    Code:
    Recreate journal<ν>? ναι                                                       
    Creating journal (32768 blocks):  Done.
    
    
    *** journal has been re-created - filesystem is now ext3 again ***
    Restarting e2fsck from the beginning...
    Resize inode not valid.  Αναδημιουργία<ν>? ναι
    Pass 1: Checking inodes, blocks, and sizes
    and now multiple of these:
    Code:
    Inode 19660804, i_blocks is 8388616, should be 0.  Διόρθωση<ν>? ναι
    Inode 19660805 has an invalid extent node (blk 615546881, lblk 0)
    Εκκαθάριση<ν>? ναι

  5. #5
    Join Date
    Jun 2013
    Beans
    33

    Re: large ext HDD problem that nobody seems to be able to help?!

    Quote Originally Posted by carlwsnyder View Post
    First, I suggest reading the Wikipedia article http://en.wikipedia.org/wiki/GUID_Partition_Table

    Second, from reading the article, your options for mounting the GPT partitioned disk seem to be incorrect, which is resulting in the error.
    Thanx for the article but I'm not a computer genius so I can find the solution to my problem by reading the whole article.
    By that I don't mean that I'm too lazy to read the whole article. I just don't understand everything it sais.
    You seem to spotted the problem. Can you help me with a solution?

  6. #6
    Join Date
    Oct 2009
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: large ext HDD problem that nobody seems to be able to help?!

    Either the drive is bad or something is going on with the file system that is causing the problems.

    The results of the fsck show that you deleted the journal, so it's not really a ext4 file system anymore. Do you have a backup of whatever data you copied to the drive?

    I would suggest running:

    Code:
    sudo badblocks -wsv /dev/sdXY
    After backing up whatever data you can.
    See here:
    https://wiki.archlinux.org/index.php/Badblocks
    Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide

    Tomorrow's an illusion and yesterday's a dream, today is a solution...

  7. #7
    Join Date
    Jun 2013
    Beans
    33

    Re: large ext HDD problem that nobody seems to be able to help?!

    Quote Originally Posted by CharlesA View Post
    Either the drive is bad or something is going on with the file system that is causing the problems.

    The results of the fsck show that you deleted the journal, so it's not really a ext4 file system anymore. Do you have a backup of whatever data you copied to the drive?

    I would suggest running:

    Code:
    sudo badblocks -wsv /dev/sdXY
    After backing up whatever data you can.
    See here:
    https://wiki.archlinux.org/index.php/Badblocks

    I don't think that the drive is bad cause til the format I was using it without any problems.
    When I did the fsck it asked me to clear the invalid journal I think. I don't know what it means but I guessed it would be the right thing to do since it asked me.
    (Keep in mind that after over 2 hours the fsck is still running!!!)

    I have a backup of all my data. I don't mind doing a new format to the disk. I just want it to work properly as it did.

  8. #8
    Join Date
    Oct 2009
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: large ext HDD problem that nobody seems to be able to help?!

    Quote Originally Posted by funked up View Post
    I don't think that the drive is bad cause til the format I was using it without any problems.
    When I did the fsck it asked me to clear the invalid journal I think. I don't know what it means but I guessed it would be the right thing to do since it asked me.
    (Keep in mind that after over 2 hours the fsck is still running!!!)

    I have a backup of all my data. I don't mind doing a new format to the disk. I just want it to work properly as it did.
    Cancel the fsck and run badblocks. It'll take a while, but it'll verify that the drive is ok. Then try creating the file system and see what happens.
    Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide

    Tomorrow's an illusion and yesterday's a dream, today is a solution...

  9. #9
    Join Date
    Jun 2013
    Beans
    33

    Re: large ext HDD problem that nobody seems to be able to help?!

    Quote Originally Posted by CharlesA View Post
    Cancel the fsck and run badblocks. It'll take a while, but it'll verify that the drive is ok. Then try creating the file system and see what happens.
    Ok but what file system should I use? As I told I want this 3TB external hard drive to work just as a USB stick with only one partition.
    Should I go for NTFS or ext4 (I only want it for Ubuntu). And what about GPT? And why do the other ones that I formated to NTFS just work?!

  10. #10
    Join Date
    Oct 2009
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: large ext HDD problem that nobody seems to be able to help?!

    I use ext4 on all my hard drives. GPT is just a special partition type, which allows partitions larger than 2TB (which is the limit of MBR partitions).

    You should be able to create the partitions in gparted with little problem.
    Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide

    Tomorrow's an illusion and yesterday's a dream, today is a solution...

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