You are not logged in.

#1 2013-01-23 16:03:31

gromlok
Member
Registered: 2010-04-19
Posts: 154

Every boot requires fsck. Makes file system read-only

Suddenly when I booted my Arch I got a message saying that there was a corruption in my /home and /var directories. The same message suggested to pass fsck as solution. The booting process hanged there without entering to the emergency login. I took a live cd an executed a fsck in all my ext4 file system and “repaired” the problem.

When I could log into the system if, for example, I want to write a file o do any operation (sudo for example) I get the message:

sudo: unable to open /var/db/sudo/lola/0: Read-only file system

If I reboot the PC again, the cycle begins again, this is: errors, asking for fsck, then, read-only FS.

Some info that you may find useful:

fstab

/dev/sda3 / ext4 defaults 0 1
/dev/sda5 /var ext4 defaults 0 1
/dev/sda6 swap swap defaults 0 0
/dev/sda7 /home ext4 defaults,user_xattr 0 1

df -h

Filesystem      Size  Used Avail Use% Mounted on
rootfs           15G  7.2G  6.6G  52% /
dev             1.9G     0  1.9G   0% /dev
run             1.9G  740K  1.9G   1% /run
/dev/sda3        15G  7.2G  6.6G  52% /
tmpfs           1.9G  536K  1.9G   1% /dev/shm
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
tmpfs           1.9G   80K  1.9G   1% /tmp
/dev/sda7        80G   39G   37G  52% /home
/dev/sda5       6.8G  3.7G  2.8G  58% /var
/dev/sda2       358G  334G   25G  94% /media/windows

systemctl

UNIT                                             LOAD   ACTIVE SUB       DESCRIPTION
proc-sys-fs-binfmt_misc.automount                loaded active running   Arbitrary Executable File Formats File System Au
sys-devices-pci...000:00:1b.0-sound-card0.device loaded active plugged   /sys/devices/pci0000:00/0000:00:1b.0/sound/card0
sys-devices-pci...0-0000:02:00.0-net-eth0.device loaded active plugged   /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.
sys-devices-pci...-0000:03:00.0-net-wlan0.device loaded active plugged   /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.
sys-devices-pci...-1:0:0:0-block-sda-sda1.device loaded active plugged   TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda2.device loaded active plugged   TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda3.device loaded active plugged   TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda4.device loaded active plugged   TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda5.device loaded active plugged   TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda6.device loaded active plugged   TOSHIBA_MK5055GSX
sys-devices-pci...-1:0:0:0-block-sda-sda7.device loaded active plugged   TOSHIBA_MK5055GSX
sys-devices-pci...1:0:0-1:0:0:0-block-sda.device loaded active plugged   TOSHIBA_MK5055GSX
sys-devices-pci...5:0:0-5:0:0:0-block-sr0.device loaded active plugged   TSSTcorp_CDDVDW_TS-L633C
sys-devices-platform-serial8250-tty-ttyS0.device loaded active plugged   /sys/devices/platform/serial8250/tty/ttyS0
sys-devices-platform-serial8250-tty-ttyS1.device loaded active plugged   /sys/devices/platform/serial8250/tty/ttyS1

tail -100 /var/log/errors.log

Jan 23 14:43:52 localhost kernel: [  283.449542] ata2.00: error: { UNC }
Jan 23 14:43:52 localhost kernel: [  283.451224] end_request: I/O error, dev sda, sector 513442820
Jan 23 14:43:52 localhost kernel: [  283.451228] Buffer I/O error on device sda2, logical block 63796096
Jan 23 14:43:56 localhost kernel: [  287.394421] ata2.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x0
Jan 23 14:43:56 localhost kernel: [  287.394426] ata2.00: irq_stat 0x40000001
Jan 23 14:43:56 localhost kernel: [  287.394430] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [  287.394435] ata2.00: cmd 60/08:00:00:84:9a/00:00:1e:00:00/40 tag 0 ncq 4096 in
Jan 23 14:43:56 localhost kernel: [  287.394435]          res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 14:43:56 localhost kernel: [  287.394438] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [  287.394440] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [  287.394442] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [  287.394447] ata2.00: cmd 60/00:08:1f:53:4d/01:00:2d:00:00/40 tag 1 ncq 131072 in
Jan 23 14:43:56 localhost kernel: [  287.394447]          res 41/40:02:04:84:9a/00:00:1e:00:00/4e Emask 0x9 (media error)
Jan 23 14:43:56 localhost kernel: [  287.394449] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [  287.394451] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [  287.394453] ata2.00: failed command: WRITE FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [  287.394458] ata2.00: cmd 61/08:10:7f:6e:b7/00:00:30:00:00/40 tag 2 ncq 4096 out
Jan 23 14:43:56 localhost kernel: [  287.394458]          res 41/40:02:04:84:9a/00:00:1e:00:00/4e Emask 0x9 (media error)
Jan 23 14:43:56 localhost kernel: [  287.394460] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [  287.394462] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [  287.394464] ata2.00: failed command: WRITE FPDMA QUEUED
Jan 23 14:43:56 localhost kernel: [  287.394468] ata2.00: cmd 61/90:18:37:42:31/00:00:35:00:00/40 tag 3 ncq 73728 out
Jan 23 14:43:56 localhost kernel: [  287.394468]          res 41/40:02:04:84:9a/00:00:1e:00:00/4e Emask 0x9 (media error)
Jan 23 14:43:56 localhost kernel: [  287.394471] ata2.00: status: { DRDY ERR }
Jan 23 14:43:56 localhost kernel: [  287.394472] ata2.00: error: { UNC }
Jan 23 14:43:56 localhost kernel: [  287.396122] end_request: I/O error, dev sda, sector 513442820
Jan 23 14:43:56 localhost kernel: [  287.396125] Buffer I/O error on device sda2, logical block 63796096
Jan 23 14:43:56 localhost kernel: [  287.396179] end_request: I/O error, dev sda, sector 760042271
Jan 23 14:43:56 localhost kernel: [  287.396232] end_request: I/O error, dev sda, sector 817327743
Jan 23 14:43:56 localhost kernel: [  287.396235] Buffer I/O error on device sda7, logical block 1133175
Jan 23 14:43:56 localhost kernel: [  287.396282] end_request: I/O error, dev sda, sector 892420663
Jan 23 14:44:01 localhost kernel: [  291.317005] ata2.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
Jan 23 14:44:01 localhost kernel: [  291.317010] ata2.00: irq_stat 0x40000008
Jan 23 14:44:01 localhost kernel: [  291.317014] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 14:44:01 localhost kernel: [  291.317019] ata2.00: cmd 60/08:08:00:84:9a/00:00:1e:00:00/40 tag 1 ncq 4096 in
Jan 23 14:44:01 localhost kernel: [  291.317019]          res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 14:44:01 localhost kernel: [  291.317022] ata2.00: status: { DRDY ERR }
Jan 23 14:44:01 localhost kernel: [  291.317024] ata2.00: error: { UNC }
Jan 23 14:44:01 localhost kernel: [  291.318643] end_request: I/O error, dev sda, sector 513442820
Jan 23 14:44:01 localhost kernel: [  291.318647] Buffer I/O error on device sda2, logical block 63796096
Jan 23 14:44:01 localhost kernel: [  291.546162] Aborting journal on device sda7-8.
Jan 23 14:54:20 localhost [    7.837917] systemd[1]: Socket service syslog.service not loaded, refusing.
Jan 23 14:54:20 localhost [    7.838515] systemd[1]: Failed to listen on Syslog Socket.
Jan 23 14:54:21 localhost kernel: [   10.930157] [drm:intel_panel_setup_backlight] *ERROR* Failed to get maximum backlight value
Jan 23 14:54:34 localhost dhcpcd[564]: dhcpcd not running
Jan 23 14:54:35 localhost dhcpcd[649]: dhcpcd not running
Jan 23 14:54:35 localhost dhcpcd[662]: dhcpcd not running
Jan 23 14:58:04 localhost su: pam_unix(su:auth): conversation failed
Jan 23 17:00:38 localhost systemd[1]: Failed to start Netcfg multi-profile daemon.
Jan 23 17:00:39 localhost [    7.790297] systemd[1]: Socket service syslog.service not loaded, refusing.
Jan 23 17:00:39 localhost [    7.790891] systemd[1]: Failed to listen on Syslog Socket.
Jan 23 17:00:39 localhost kernel: [   11.363432] [drm:intel_panel_setup_backlight] *ERROR* Failed to get maximum backlight value
Jan 23 17:00:55 localhost dhcpcd[612]: dhcpcd not running
Jan 23 17:00:55 localhost dhcpcd[618]: dhcpcd not running
Jan 23 17:00:55 localhost dhcpcd[626]: dhcpcd not running
Jan 23 17:01:23 localhost su: pam_unix(su:auth): conversation failed
Jan 23 17:04:55 localhost kernel: [  274.346016] ata2.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x0
Jan 23 17:04:55 localhost kernel: [  274.346022] ata2.00: irq_stat 0x40000008
Jan 23 17:04:55 localhost kernel: [  274.346025] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:04:55 localhost kernel: [  274.346031] ata2.00: cmd 60/70:08:e8:83:9a/00:00:1e:00:00/40 tag 1 ncq 57344 in
Jan 23 17:04:55 localhost kernel: [  274.346031]          res 41/40:70:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:04:55 localhost kernel: [  274.346034] ata2.00: status: { DRDY ERR }
Jan 23 17:04:55 localhost kernel: [  274.346035] ata2.00: error: { UNC }
Jan 23 17:04:55 localhost kernel: [  274.348151] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:04:55 localhost kernel: [  274.348154] Buffer I/O error on device sda2, logical block 63796096
Jan 23 17:04:55 localhost kernel: [  274.348159] Buffer I/O error on device sda2, logical block 63796097
Jan 23 17:04:55 localhost kernel: [  274.348162] Buffer I/O error on device sda2, logical block 63796098
Jan 23 17:04:55 localhost kernel: [  274.348164] Buffer I/O error on device sda2, logical block 63796099
Jan 23 17:04:55 localhost kernel: [  274.348166] Buffer I/O error on device sda2, logical block 63796100
Jan 23 17:04:55 localhost kernel: [  274.348168] Buffer I/O error on device sda2, logical block 63796101
Jan 23 17:04:55 localhost kernel: [  274.348171] Buffer I/O error on device sda2, logical block 63796102
Jan 23 17:04:55 localhost kernel: [  274.348173] Buffer I/O error on device sda2, logical block 63796103
Jan 23 17:04:55 localhost kernel: [  274.348176] Buffer I/O error on device sda2, logical block 63796104
Jan 23 17:04:55 localhost kernel: [  274.348178] Buffer I/O error on device sda2, logical block 63796105
Jan 23 17:04:59 localhost kernel: [  278.257533] ata2.00: exception Emask 0x0 SAct 0x84 SErr 0x0 action 0x0
Jan 23 17:04:59 localhost kernel: [  278.257539] ata2.00: irq_stat 0x40000008
Jan 23 17:04:59 localhost kernel: [  278.257543] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:04:59 localhost kernel: [  278.257549] ata2.00: cmd 60/08:38:00:84:9a/00:00:1e:00:00/40 tag 7 ncq 4096 in
Jan 23 17:04:59 localhost kernel: [  278.257549]          res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:04:59 localhost kernel: [  278.257551] ata2.00: status: { DRDY ERR }
Jan 23 17:04:59 localhost kernel: [  278.257553] ata2.00: error: { UNC }
Jan 23 17:04:59 localhost kernel: [  278.259233] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:05:03 localhost kernel: [  282.157929] ata2.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
Jan 23 17:05:03 localhost kernel: [  282.157934] ata2.00: irq_stat 0x40000008
Jan 23 17:05:03 localhost kernel: [  282.157938] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:05:03 localhost kernel: [  282.157943] ata2.00: cmd 60/08:10:00:84:9a/00:00:1e:00:00/40 tag 2 ncq 4096 in
Jan 23 17:05:03 localhost kernel: [  282.157943]          res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:05:03 localhost kernel: [  282.157946] ata2.00: status: { DRDY ERR }
Jan 23 17:05:03 localhost kernel: [  282.157947] ata2.00: error: { UNC }
Jan 23 17:05:03 localhost kernel: [  282.159582] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:05:03 localhost kernel: [  282.159588] Buffer I/O error on device sda2, logical block 63796096
Jan 23 17:05:07 localhost kernel: [  286.069482] ata2.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
Jan 23 17:05:07 localhost kernel: [  286.069487] ata2.00: irq_stat 0x40000008
Jan 23 17:05:07 localhost kernel: [  286.069491] ata2.00: failed command: READ FPDMA QUEUED
Jan 23 17:05:07 localhost kernel: [  286.069496] ata2.00: cmd 60/08:30:00:84:9a/00:00:1e:00:00/40 tag 6 ncq 4096 in
Jan 23 17:05:07 localhost kernel: [  286.069496]          res 41/40:08:04:84:9a/00:00:1e:00:00/6e Emask 0x409 (media error) <F>
Jan 23 17:05:07 localhost kernel: [  286.069499] ata2.00: status: { DRDY ERR }
Jan 23 17:05:07 localhost kernel: [  286.069501] ata2.00: error: { UNC }
Jan 23 17:05:07 localhost kernel: [  286.071955] end_request: I/O error, dev sda, sector 513442820
Jan 23 17:05:07 localhost kernel: [  286.071959] Buffer I/O error on device sda2, logical block 63796096

Waiting for your help.

Thank you.


.

Offline

#2 2013-01-23 16:31:53

kaszak696
Member
Registered: 2009-05-26
Posts: 543

Re: Every boot requires fsck. Makes file system read-only

On my old drive these messages meant a mechanical failure. Perhaps you can keep using this HD a while longer if you isolate the corrupt parts ot the drive, but you have to prepare for a total breakdown. Backup your data ASAP!

Can you provide SMART data of the drive?

Last edited by kaszak696 (2013-01-23 16:34:19)


'What can be asserted without evidence can also be dismissed without evidence.' - Christopher Hitchens
'There's no such thing as addiction, there's only things that you enjoy doing more than life.' - Doug Stanhope
GitHub Junkyard

Offline

#3 2013-01-23 16:42:23

gromlok
Member
Registered: 2010-04-19
Posts: 154

Re: Every boot requires fsck. Makes file system read-only

oh god, if my HD dies I will kill myself.

I did the SMART, short and long (following the ArchWiki) and got (will post the long as soon it ends):

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      7967         -

With more details:
smartctl -a /dev/sda

smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.6.9-1-ARCH] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MK..55GSX
Device Model:     TOSHIBA MK5055GSX
Serial Number:    897JC07RT
LU WWN Device Id: 5 000039 1f3c01f05
Firmware Version: FG001M
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Wed Jan 23 13:46:24 2013 PYST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 249) Self-test routine in progress...
                                        90% of test remaining.
Total time to complete Offline 
data collection:                (  120) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 183) minutes.
SCT capabilities:              (0x0039) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       1320
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       1807
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       7
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   081   081   000    Old_age   Always       -       7967
 10 Spin_Retry_Count        0x0033   136   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1789
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       97
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       33
193 Load_Cycle_Count        0x0032   082   082   000    Old_age   Always       -       189405
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       39 (Min/Max 9/50)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       9
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       87
222 Loaded_Hours            0x0032   085   085   000    Old_age   Always       -       6001
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       320
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 634 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 634 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 02 04 84 9a 6e  Error: UNC at LBA = 0x0e9a8404 = 245007364

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 00 84 9a 40 08      03:31:25.735  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      03:31:25.714  FLUSH CACHE EXT
  61 18 08 07 82 b1 40 08      03:31:25.714  WRITE FPDMA QUEUED
  61 08 00 0f 7d 31 40 08      03:31:25.714  WRITE FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      03:31:25.682  FLUSH CACHE EXT

Error 633 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 02 04 84 9a 6e  Error: UNC at LBA = 0x0e9a8404 = 245007364

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 00 00 84 9a 40 08      03:31:21.832  READ FPDMA QUEUED
  61 18 00 27 81 b1 40 08      03:31:21.451  WRITE FPDMA QUEUED
  61 18 00 27 77 b1 40 08      03:31:20.425  WRITE FPDMA QUEUED
  61 18 00 2f 8c b1 40 08      03:31:19.451  WRITE FPDMA QUEUED
  61 18 00 ef 81 b1 40 08      03:31:18.445  WRITE FPDMA QUEUED

Error 632 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 0a 04 84 9a 6e  Error: UNC at LBA = 0x0e9a8404 = 245007364

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 07 7f 09 40 08      03:16:43.581  READ FPDMA QUEUED
  60 08 08 00 84 9a 40 08      03:16:43.559  READ FPDMA QUEUED
  60 00 00 a7 5b 09 40 08      03:16:43.552  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      03:16:43.551  SET FEATURES [Reserved for Serial ATA]
  27 00 00 00 00 00 e0 00      03:16:43.551  READ NATIVE MAX ADDRESS EXT

Error 631 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 0a 04 84 9a 6e  Error: UNC at LBA = 0x0e9a8404 = 245007364

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 a7 5b 09 40 08      03:16:39.713  READ FPDMA QUEUED
  60 08 00 87 b5 25 40 08      03:16:39.705  READ FPDMA QUEUED
  60 00 00 8f 60 05 40 08      03:16:39.693  READ FPDMA QUEUED
  60 08 00 e7 d4 54 40 08      03:16:39.692  READ FPDMA QUEUED
  60 08 08 00 84 9a 40 08      03:16:39.678  READ FPDMA QUEUED

Error 630 occurred at disk power-on lifetime: 7967 hours (331 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 12 04 84 9a 6e  Error: WP at LBA = 0x0e9a8404 = 245007364

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 08 0e 4c b6 40 08      03:16:35.710  WRITE FPDMA QUEUED
  61 08 08 0e 4c b6 40 08      03:16:35.710  WRITE FPDMA QUEUED
  61 08 08 0e 4c b6 40 08      03:16:35.709  WRITE FPDMA QUEUED
  61 98 18 8f 41 31 40 08      03:16:35.709  WRITE FPDMA QUEUED
  61 08 08 0e 4c b6 40 08      03:16:35.708  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      7967         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Is there an equivalent to Solaris iostat -En in Linux? Havent found any. Remember that I can't install anything: read-only FS

Last edited by gromlok (2013-01-23 16:47:35)


.

Offline

#4 2013-01-23 16:45:23

kaszak696
Member
Registered: 2009-05-26
Posts: 543

Re: Every boot requires fsck. Makes file system read-only

Post 'smartctl -a' as well.

Last edited by kaszak696 (2013-01-23 16:45:38)


'What can be asserted without evidence can also be dismissed without evidence.' - Christopher Hitchens
'There's no such thing as addiction, there's only things that you enjoy doing more than life.' - Doug Stanhope
GitHub Junkyard

Offline

#5 2013-01-23 16:48:00

gromlok
Member
Registered: 2010-04-19
Posts: 154

Re: Every boot requires fsck. Makes file system read-only

Done (edited previous post)


.

Offline

#6 2013-01-23 17:18:53

kaszak696
Member
Registered: 2009-05-26
Posts: 543

Re: Every boot requires fsck. Makes file system read-only

Hmm, it looks kinda bad, drive logged 634 errors already, reallocated 7 bad sectors, and suspects another 9. Much better compared to my case, but still very concerning.

Last edited by kaszak696 (2013-01-23 17:19:38)


'What can be asserted without evidence can also be dismissed without evidence.' - Christopher Hitchens
'There's no such thing as addiction, there's only things that you enjoy doing more than life.' - Doug Stanhope
GitHub Junkyard

Offline

#7 2013-01-23 18:00:44

mich41
Member
Registered: 2012-06-22
Posts: 520

Re: Every boot requires fsck. Makes file system read-only

I don't like this "media error" in your dmesg. I'm not a Linux ATA driver expert, but my guess is that some files accessed during boot lie on not-yet-reallocated bad blocks and trigger this error which scares Linux into remounting the FS read-only. If I were you, I'd connect this HDD to another machine and dd it's contents to some file ASAP smile

Then you can dd this file back to HDD to force reallocation of any bad blocks and connect the HDD back. If it boots without errors, the problem was caused by HDD so you can throw it to trash smile

Offline

Board footer

Powered by FluxBB