LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   tune2fs: No such device or address while trying to open /dev/sda1 (https://www.linuxquestions.org/questions/linux-server-73/tune2fs-no-such-device-or-address-while-trying-to-open-dev-sda1-872790/)

quanta 04-03-2011 09:47 PM
tune2fs: No such device or address while trying to open /dev/sda1
 
Hi,

Last night, OSSEC sent me some warning emails related to bad hard disk:
Code:
Apr  3 20:26:58 207 kernel: sd 0:0:0:0: SCSI error: return code = 0x06000000
Code:
Apr  3 21:57:52 207 kernel: EXT3-fs error (device sda1): ext3_get_inode_loc: unable to read inode block - inode=299533439, block=599064613
and below is the result when I check from /var/log/messages:
Code:
Apr  3 20:26:48 207 kernel: aacraid: Host adapter abort request (0,0,0,0)
Apr  3 20:26:48 207 kernel: aacraid: Host adapter reset request. SCSI hang ?
Apr  3 20:26:58 207 kernel: sd 0:0:0:0: timing out command, waited 360s
Apr  3 20:26:58 207 kernel: sd 0:0:0:0: SCSI error: return code = 0x06000000
Apr  3 20:26:58 207 kernel: end_request: I/O error, dev sda, sector 4358861306
Apr  3 20:26:58 207 kernel: EXT3-fs error (device sda1): ext3_free_branches: Read failure, inode=246590279, block=544857659
Apr  3 20:26:58 207 kernel: Aborting journal on device sda1.
Code:
Apr  3 20:33:48 207 kernel: aacraid: Host adapter abort request (0,0,0,0)
Apr  3 20:33:48 207 kernel: aacraid: Host adapter reset request. SCSI hang ?
Apr  3 20:33:58 207 kernel: sd 0:0:0:0: timing out command, waited 360s
Apr  3 20:33:58 207 kernel: sd 0:0:0:0: SCSI error: return code = 0x06000000
Apr  3 20:33:58 207 kernel: end_request: I/O error, dev sda, sector 34
Apr  3 20:33:58 207 kernel: Buffer I/O error on device sda1, logical block 0
Apr  3 20:33:58 207 kernel: lost page write due to I/O error on sda1
Apr  3 20:33:58 207 kernel: EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has aborted
Code:
Apr  3 20:44:18 207 kernel: aacraid: Host adapter abort request (0,0,0,0)
Apr  3 20:44:18 207 kernel: aacraid: Host adapter reset request. SCSI hang ?
Apr  3 20:44:30 207 kernel: ext3_abort called.
Apr  3 20:44:30 207 kernel: EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
Apr  3 20:44:30 207 kernel: Remounting filesystem read-only
My /dev/sda1 mounted to /data. The system give me the "Input/Output error" when I `cd` to some folders.

I'm going to run `fsck` on this device follow the steps below:
Quote:
1. stop all services access to /data
2. unmount the /data
3. tune2fs -O ^has_journal /dev/sda1
4. e2fsck -fcy /dev/sda1
5. tune2fs -j /dev/sda1
but I got the following when run step 3:
Code:
# tune2fs -O ^has_journal /dev/sda1
tune2fs 1.39 (29-May-2006)
tune2fs: No such device or address while trying to open /dev/sda1
Couldn't find valid filesystem superblock.
I backed up some parts of data on this. What should I do now?

P/S: This disk has been used about for 1 year. My system requires high read/write intensity, should I change to SSD?

flakblas 04-04-2011 03:29 PM
It looks like the drive is pretty close to dead. An SSD will give you higher IO rates but it has a definite life span. Platter drives typically have a sort of bathtub curve for failure rates. A certain percentage die off in the first year (infant mortality), then for the next year the failure rate is low. But starting in the third year the failure rate starts climbing again. Anyway, it may be worth looking into a RAID setup since you know you'll be beating the drives up. Software RAID may be a good, cost-effective solution (mdadm). With RAID, at least when a drive fails you can just replace it and the array will rebuild without any real downtime.

Anyway, if you want to dig deeper into this particular drive failure, check out the smartctl command if you have it installed. But definitely try to back up as much as possible as this drive is toast.


All times are GMT -5. The time now is 12:55 AM.