You are not logged in.

Pages: 1

#1 2015-02-26 17:16:52

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

errors=remount-ro in effect, but why?

I should think the title says it all, and I should think the answer is quite simple, but since I haven't been able to find it, here I am again.

The problem is quite simple, I need to figure out why, on occasion, one of two drives in my laptop is remount read only. I can live with it, but it does happen too often. It seems obvious that the issue arise due to the part of my fstab stating:

errors=remount-ro

The question is why it happens, which I can't seem to figure out. I know this is something I should know, but I don't.Part of the problem presumably is that the first thing I do when I experience the problem, is restarting the system and thus, for a time at least, fixing the problem.


Anyway, please do enlighten me if you've got nothing better to do.


Best regards.

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#2 2015-02-26 19:00:51

Tutti
Member
Registered: 2015-02-26
Posts: 117

Re: errors=remount-ro in effect, but why?

From the man pages of mount(8)

errors={continue|remount-ro|panic}
              Define  the  behavior  when  an  error  is encountered.  (Either
              ignore errors and just mark the filesystem  erroneous  and  con‐
              tinue,  or  remount  the filesystem read-only, or panic and halt
              the system.)  The default is set in the  filesystem  superblock,
              and can be changed using tune2fs(8).

You probably have an error occur when mounting the drive, which is then mounted as read only.
I do not have any tips on solving the errors except trying fsck.

Offline

#3 2015-02-26 19:06:29

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

Tutti wrote:

From the man pages of mount(8)

errors={continue|remount-ro|panic}
              Define  the  behavior  when  an  error  is encountered.  (Either
              ignore errors and just mark the filesystem  erroneous  and  con‐
              tinue,  or  remount  the filesystem read-only, or panic and halt
              the system.)  The default is set in the  filesystem  superblock,
              and can be changed using tune2fs(8).

You probably have an error occur when mounting the drive, which is then mounted as read only.
I do not have any tips on solving the errors except trying fsck.

Thanks for the reply, but no, every thing works fine for days and then suddenly, I get issues because suddenly something can't be written, I check how the drive is mounted, and I find that it's mounted read only, though that hasn't been the case from the start. I should probably also mention that it's not the root file system, but the /home which has a dedicated hdd. I should think that I could remount it once again once this problem occur, without the need to reboot, or fsck or what not, but as the issue does repeat itself often enough, I am concerned, and would thus like to figure out what the issue is. That is, what particular error get it to remount-ro.


Best regards.

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#4 2015-02-26 19:19:07

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: errors=remount-ro in effect, but why?

Perhaps it's a hardware problem or a filesystem problem (you haven't mentioned which filesystem type you are using)?
Have you tried running a smartctl test?

Offline

#5 2015-02-26 19:20:30

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

paulkerry wrote:

Perhaps it's a hardware problem or a filesystem problem (you haven't mentioned which filesystem type you are using)?
Have you tried running a smartctl test?

GTP/etx4 and no. Haven't the slightest clue what smartctl is, but will look it up at once.

Last edited by zacariaz (2015-02-26 19:22:08)

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#6 2015-02-26 19:22:09

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,018

Re: errors=remount-ro in effect, but why?

Perhaps you'd see errors in dmesg after it gets remounted read-only.

Offline

#7 2015-02-26 19:29:02

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

lucke wrote:

Perhaps you'd see errors in dmesg after it gets remounted read-only.

I had the same thought, but after I rebooted of course. I would have thought the information was still available, but I can find it.

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#8 2015-02-26 19:29:38

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,018

Re: errors=remount-ro in effect, but why?

It should be in the journal.

Offline

#9 2015-02-26 19:46:42

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

lucke wrote:

It should be in the journal.

Yes, at least there something, though I'm not sure how to enterpret it...

feb 25 20:02:43 zarchbook kernel: sd 1:0:0:0: [sdb] Write Protect is off
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 58828384
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 3687 (offset 0 size 7180288 starting block 7353676)
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353292
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353293
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353294
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353295
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353296
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353297
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353298
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353299
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353300
feb 26 16:56:54 zarchbook kernel: Buffer I/O error on device sdb1, logical block 7353301
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 58829408
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 3687 (offset 0 size 7180288 starting block 7353804)
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 58830432
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 3687 (offset 0 size 7180288 starting block 7353932)
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 58831456
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 3687 (offset 0 size 7180288 starting block 7354060)
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 58832480
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 3687 (offset 0 size 7180288 starting block 7354149)
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 893712488
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 3979 (offset 0 size 0 starting block 111714062)
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 8466176
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 1990 (offset 0 size 323584 starting block 1058351)
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 54622080
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 3979 (offset 0 size 0 starting block 6827761)
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 54622512
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 3979 (offset 0 size 0 starting block 6827815)
feb 26 16:56:54 zarchbook kernel: blk_update_request: I/O error, dev sdb, sector 293372360
feb 26 16:56:54 zarchbook kernel: EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O error -5 writing to inode 792 (offset 0 size 0 starting block 36671546)
feb 26 16:56:54 zarchbook kernel: EXT4-fs error (device sdb1): ext4_journal_check_start:56: Detected aborted journal
feb 26 16:56:54 zarchbook kernel: EXT4-fs error (device sdb1): ext4_journal_check_start:56: Detected aborted journal
feb 26 16:56:54 zarchbook kernel: EXT4-fs error (device sdb1): ext4_journal_check_start:56: Detected aborted journal
feb 26 17:58:59 zarchbook kernel: EXT4-fs error (device sdb1): ext4_put_super:789: Couldn't clean up the journal
feb 26 17:59:05 zarchbook kernel: sd 1:0:0:0: [sdb] Write Protect is off
feb 26 17:59:07 zarchbook systemd-fsck[293]: /dev/sdb1 contains a file system with errors, check forced.

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#10 2015-02-26 19:59:52

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: errors=remount-ro in effect, but why?

An I/O error like this usually points to a hardware problem, which your logs show is on sdb1, so you try smartctl from the smartmontools package to test the entire sdb disk and not just partition 1

https://wiki.archlinux.org/index.php/S.M.A.R.T.

smartctl -t short /dev/sdb

and then

smartctl -a /dev/sdb

Last edited by paulkerry (2015-02-26 20:05:48)

Offline

#11 2015-02-26 20:07:20

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

paulkerry wrote:

An I/O error like this usually points to hardware problem, which in your logs show is on sdb1, so you try smartctl from the smartmontools package to test the entire sdb disk and not just partition 1

https://wiki.archlinux.org/index.php/S.M.A.R.T.

smartctl -t short /dev/sdb

and then

smartctl -a /dev/sdb

I already did a short test, which didn't seem to turn up anything, and am now in the process of doing a long one. However, I just looked at overall health. The -a flag tells me that there's no errors logged, nut I don't know if that's because I'm in the process of a new test or not.

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#12 2015-02-26 20:10:12

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: errors=remount-ro in effect, but why?

When the long test has completed, post the output from

smartctl -a /dev/sdb

Offline

#13 2015-02-26 20:16:50

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

paulkerry wrote:

When the long test has completed, post the output from

smartctl -a /dev/sdb

Will do, in about 3 hours, assuming I'm still awake.

Thanks for now.

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#14 2015-02-27 13:34:57

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

Okay, so it took a bit longer than intended, as for some odd reason the test kept getting interrupted, but in the end I got it to work and here's the output.

smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.18.6-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus SpinPoint M8 (AF)
Device Model:     ST1000LM024 HN-M101MBB
Serial Number:    S2U5J9FD139084
LU WWN Device Id: 5 0004cf 209721609
Firmware Version: 2AR10001
User Capacity:    1.000.204.886.016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Feb 27 14:29:16 2015 CET
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:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(12840) 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: 	 ( 214) minutes.
SCT capabilities: 	       (0x003f)	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     0x002f   100   100   051    Pre-fail  Always       -       11
  2 Throughput_Performance  0x0026   054   054   000    Old_age   Always       -       12223
  3 Spin_Up_Time            0x0023   089   089   025    Pre-fail  Always       -       3451
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       424
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       13365
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       419
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       309
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       250
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   056   000    Old_age   Always       -       36 (Min/Max 20/44)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       4
200 Multi_Zone_Error_Rate   0x002a   001   001   000    Old_age   Always       -       91720
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       419
225 Load_Cycle_Count        0x0032   054   054   000    Old_age   Always       -       472113

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     13364         -
# 2  Extended offline    Interrupted (host reset)      30%     13354         -
# 3  Extended offline    Interrupted (host reset)      50%     13349         -
# 4  Short offline       Completed without error       00%     13347         -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    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.

As far as I can discern, there's nothing of use, but then again I'm hardly the expert.

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#15 2015-02-27 16:36:26

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,018

Re: errors=remount-ro in effect, but why?

It might be that the drive isn't connected properly.

Offline

#16 2015-02-27 16:53:39

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: errors=remount-ro in effect, but why?

I had a similar issue recently, this fixed it (add to the bootloader's kernel commandline):

libata.force=1.5Gbps

Offline

#17 2015-02-27 17:52:01

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

lucke wrote:

It might be that the drive isn't connected properly.

I suppose, but it does seem unlikely. I'll make sure to check though, if I can pull my self together to take appart my laptop.

brebs wrote:

I had a similar issue recently, this fixed it (add to the bootloader's kernel commandline):

libata.force=1.5Gbps

How would you know your issue was similar? Is it simply similar symptoms, or have you read something from the test results I haven't?

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#18 2015-02-27 18:49:29

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: errors=remount-ro in effect, but why?

I was getting these kinda errors in the system log, after varying amount of time (sometimes many hours):

ata5.00: irq_stat 0x08000000, interface fatal error
ata5.00: failed command: WRITE FPDMA QUEUED
res 40/00:ac:38:af:bc/00:00:21:00:00/40 Emask 0x10 (ATA bus error)

Offline

#19 2015-02-27 19:05:06

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

brebs wrote:

I was getting these kinda errors in the system log, after varying amount of time (sometimes many hours):

ata5.00: irq_stat 0x08000000, interface fatal error
ata5.00: failed command: WRITE FPDMA QUEUED
res 40/00:ac:38:af:bc/00:00:21:00:00/40 Emask 0x10 (ATA bus error)

I recognize line 2, and I suppose it kinda coincides with the remount incidents... Well it's hard to say, as I don't really know when exactly it happens.

jan 11 01:28:03 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 11 01:28:03 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 11 01:28:03 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 11 01:28:03 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 11 01:28:03 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 11 01:28:03 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 11 01:28:03 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 11 01:28:03 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 11 01:28:03 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 13 15:57:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 13 15:57:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 13 15:57:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 13 15:57:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 13 15:57:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 13 15:57:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 13 15:57:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 16:23:22 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
jan 27 21:50:54 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 21 16:26:04 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 24 16:54:09 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 26 22:59:45 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED
feb 27 04:06:14 zarchbook kernel: ata2.00: failed command: WRITE FPDMA QUEUED

I count 8 incidents this year, some of which I may not even have notices, so it is about the right amount actually. As for the rest, of the errors, they don't apply to me, at least they don't appear in the logs.

So, what does "WRITE FPDMA QUEUED" mean, and what does it mean for it to fail, what might be the cause, and might it be the cause for the remount-ro?

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#20 2015-02-27 20:46:38

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: errors=remount-ro in effect, but why?

zacariaz wrote:

many questions

I don't have anything particularly illuminating to add. Do your own googling. Reading the kernel source code is probably best - which is of course horrendous.

At this point, what you *should* be doing is assessing the potential risk vs reward of what I suggested, and just doing what I suggested - it's easy, and pretty safe.

Offline

#21 2015-02-27 20:50:40

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

brebs wrote:
zacariaz wrote:

many questions

I don't have anything particularly illuminating to add. Do your own googling. Reading the kernel source code is probably best - which is of course horrendous.

At this point, what you *should* be doing is assessing the potential risk vs reward of what I suggested, and just doing what I suggested - it's easy, and pretty safe.

And I'll probably try it out, if nothing else turns up, but in short I haven't the slightest clue what your suggestion does, or how to assess if it has helped, since I don't know the cause of the issue. Google is of little help, and to be blunt I do not have the skills to look through the source code of anything more complicated than a terminal based tic tac toe game.

Anyway, thanks again.

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#22 2015-02-27 21:31:44

Tutti
Member
Registered: 2015-02-26
Posts: 117

Re: errors=remount-ro in effect, but why?

Have you tried swapping cables / SATA ports?
Searching the FPDMA message gave me: http://askubuntu.com/questions/141862/i … 880#141880
among other results indicating drive failure and faulty power, connector or cables.

And do you have any idea of when it remounts? (during file transfer, after idle time, etc.)

Offline

#23 2015-02-27 21:39:26

zacariaz
Member
From: Denmark
Registered: 2012-01-18
Posts: 539

Re: errors=remount-ro in effect, but why?

Tutti wrote:

Have you tried swapping cables / SATA ports?
Searching the FPDMA message gave me: http://askubuntu.com/questions/141862/i … 880#141880
among other results indicating drive failure and faulty power, connector or cables.

And do you have any idea of when it remounts? (during file transfer, after idle time, etc.)

A bad connection is somewhat unlikely, but it's of course an option, which swapping sata port and probably cable isn't, since it's a laptop.
The only thing I can think of that may have an affect, is some heat issues I've had on occasion lately.

Anyway, I'm pretty  tired now, but I'll make sure to check out the link and get back later or in the morning, when/if I've got anything to add.

Thanks.

I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.

Offline

#24 2015-02-27 21:56:48

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: errors=remount-ro in effect, but why?

zacariaz wrote:

what your suggestion does, or how to assess if it has helped

It limits the speed to 1.5GB/sec, rather than 3GB/sec - which is hugely important if you're using (old-style) hardware (e.g. motherboard, RAID controller, or the drive itself) which doesn't *support* 3GB/sec.

If it works, the error messages will completely disappear.

Just try it. It's about speed, and low-risk.

Offline

Pages: 1

Board footer

Powered by FluxBB