• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 465
  • Last Modified:

Corrupt hdd

Hi *,

I recently asked this question: http://www.experts-exchange.com/OS/Linux/Q_27295075.html. I have only just put the new hdd into my machine. It worked like a dream, all my stuff was there (apart from 888mb of corrupt stuff ddrescue couldn't get back).

I restarted my machine, and am now getting
Home: Inode 233069863 has an invalid extend node (blk 40746976, Iblk 0)

I am always getting:
ata_id[642]: HDIO_GET_IDENTITY failed for 'dev/sdb'
ata_id[643]: HDIO_GET_IDENTITY failed for 'dev/sdb'
Although i remember correctly I was always getting these errors when the machine was working fine.

Sometimes I boot up and it gives me the option to ignore/fix the errors. If I ignore I can boot into the machine.

Any thoughts? I am assuming the machine is somehow corrupting data on hdds! But it only happens on my home hdd, not the system one!

  • 3
1 Solution
Hugh McCurdyCommented:
The GET_IDENTITY error is likely a false positive from software expecting older technology when you have newer technology.  Unless someone disputes this, I'd ignore it.

The inode error should be addressed.  What I would do is boot from a Live CD (such as Ubuntu), mount the partition and run fsck.  If you aren't sure which partition, then fsck all Linux partitions on your computer.  You may need to use fsck -f in order to force a check.  Command would be something like

# fsck -f /dev/sda3    (for the 3rd partition of the first drive).
or perhaps
$ sudo fsck -f /dev/sda3    (If you are using Ubuntu, et al).

If you aren't sure which partitions are Linux, you can use fdisk
$ sudo fdisk /dev/sda
Hugh McCurdyCommented:
Oh, whatever you do, don't ever use the w(rite) command in fdisk unless you know what you are doing.
James_h1023Author Commented:
Apologies for the delay and thanks for your comments.

I realise I can do fdisk, as this was what I had to do to halfl fix the previous hdd (in my previous question). My question is more pointed towards why the disk is corrupting? and why only the home disk/partition!

Hugh McCurdyCommented:
Did you run fsck yet?  The most common cause for a bad inode is improper shutdown (power failure).  Other options are broken hardware, dirty electricity or even a defective driver.  
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Build your data science skills into a career

Are you ready to take your data science career to the next step, or break into data science? With Springboard’s Data Science Career Track, you’ll master data science topics, have personalized career guidance, weekly calls with a data science expert, and a job guarantee.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now