HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Kernel Questions (http://www.howtoforge.com/forums/forumdisplay.php?f=6)
-   -   Problems with harddisc (http://www.howtoforge.com/forums/showthread.php?t=44150)

Jürgen 16th March 2010 20:41

Problems with harddisc
 
Hey,

yesterday my filesystem of my server was read-only. I restarted the server and the problem was gone. However, today I had the same problem again.

So I checked the harddisc with fsck. That's the result:
Code:

fsck /dev/sda
fsck 1.41.3 (12-Oct-2008)
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Furthermore I had a look into the file /var/log/system.log and found this:
Code:

Mar 16 17:37:12 server7 kernel: ata1.00: exception Emask 0x50 SAct 0x3f SErr 0x400800 action 0x2 frozen
Mar 16 17:37:12 server7 kernel: ata1.00: (irq_stat 0x08000000, interface fatal error)
Mar 16 17:37:12 server7 kernel: ata1.00: tag 0 cmd 0x61 Emask 0x50 stat 0x40 err 0x0 (ATA bus error)
Mar 16 17:37:12 server7 kernel: ata1.00: tag 1 cmd 0x61 Emask 0x50 stat 0x40 err 0x0 (ATA bus error)
Mar 16 17:37:12 server7 kernel: ata1.00: tag 2 cmd 0x61 Emask 0x50 stat 0x40 err 0x0 (ATA bus error)
Mar 16 17:37:12 server7 kernel: ata1.00: tag 3 cmd 0x61 Emask 0x50 stat 0x40 err 0x0 (ATA bus error)
Mar 16 17:37:12 server7 kernel: ata1.00: tag 4 cmd 0x61 Emask 0x50 stat 0x40 err 0x0 (ATA bus error)
Mar 16 17:37:12 server7 kernel: ata1.00: tag 5 cmd 0x61 Emask 0x50 stat 0x40 err 0x0 (ATA bus error)
Mar 16 17:37:12 server7 kernel: ata1: soft resetting port
Mar 16 17:37:13 server7 kernel: ata1: softreset failed (1st FIS failed)
Mar 16 17:37:13 server7 kernel: ata1: softreset failed, retrying in 5 secs
Mar 16 17:37:18 server7 kernel: ata1: hard resetting port
Mar 16 17:37:18 server7 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 16 17:37:18 server7 kernel: ata1.00: configured for UDMA/133
Mar 16 17:37:18 server7 kernel: ata1: EH complete
Mar 16 17:37:18 server7 kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
Mar 16 17:37:18 server7 kernel: sda: Write Protect is off
Mar 16 17:37:18 server7 kernel: ata1.00: limiting speed to UDMA/100
Mar 16 17:37:18 server7 kernel: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x400800 action 0x2 frozen
Mar 16 17:37:18 server7 kernel: ata1.00: (irq_stat 0x08000000, interface fatal error)
Mar 16 17:37:18 server7 kernel: ata1.00: tag 0 cmd 0x61 Emask 0x50 stat 0x40 err 0x0 (ATA bus error)
Mar 16 17:37:18 server7 kernel: sda: Mode Sense: 00 3a 00 00
Mar 16 17:37:19 server7 kernel: ata1: soft resetting port
Mar 16 17:37:19 server7 kernel: ata1: softreset failed (1st FIS failed)
Mar 16 17:37:19 server7 kernel: ata1: softreset failed, retrying in 5 secs
Mar 16 17:37:24 server7 kernel: ata1: hard resetting port
Mar 16 17:37:24 server7 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 16 17:37:24 server7 kernel: ata1.00: configured for UDMA/100
Mar 16 17:37:24 server7 kernel: ata1: EH complete
Mar 16 17:37:25 server7 kernel: SCSI device sda: drive cache: write back
Mar 16 17:37:25 server7 kernel: SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB)
Mar 16 17:37:25 server7 kernel: sda: Write Protect is off
Mar 16 17:37:25 server7 kernel: sda: Mode Sense: 00 3a 00 00
Mar 16 17:37:25 server7 kernel: SCSI device sda: drive cache: write back

Do you have an idea what's the problem and how I can solve it?

Thank you very much

falko 17th March 2010 14:39

Do you really use ext2, or maybe ext3 or ext4? What's the output of
Code:

fdisk -l
?

amonaraize 1st June 2010 13:55

Problems with harddisc
 
Buy a new drive A.S.A.P. and transfer the data.! The old drive is failing. You are correct in that the actuator arm and the control mechanism that tells the arm what to do are damaged. This is the first sign of a failing drive. You can have a specialist recover the data (at a very high price) after the drive stops working but get a new drive NOW and try to transfer what you can...

Rapid2214 8th August 2010 11:52

Did you run the fsck via the live disc?
Otherwise /dev/sda would have the mounted partition of /dev/sda1...

Try run the same command from the recovery option in the installation disc (if you have ubuntu)..


All times are GMT +2. The time now is 01:12.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.