Arch Linux

ctarwater

Member

Registered: 2009-02-05

Posts: 300

Disc keeps locking as "read only"

I've been away from my computer for a few months and just finished updating everything, so far the only problem is that when I run ktorrent, the source disc becomes read only.

I have a second hdd that holds all of my media and houses the destination folder for my torrents. 
The hdd is mounted with the following line via fstab:

UUID=f8bb1b42-c860-457b-8f8d-045953c423b4 /xbox ext3 defaults 0 0

I've tried unmounting and remounting it, which works until I try to download something again and then ktorrent spits out an error that the disc is read only. 
I also tried running deluge and qbittorrent and get the same results.

Any ideas?  What the hell have I missed in the past few months?

Last edited by ctarwater (2009-10-11 13:46:01)

Renan Birck

Member

From: Brazil

Registered: 2007-11-11

Posts: 401

Website

Re: Disc keeps locking as "read only"

Is there any error message on dmesg? Usually filesystems are remounted as read-only if the filesystem has a problem.

---

x64 Arch + KDE|last.fm|twitter|blog|git|stack exchange|AUR

ctarwater

Member

Registered: 2009-02-05

Posts: 300

Re: Disc keeps locking as "read only"

I found this at the end of dmesg logs:

EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with writeback data mode.
Adding 2008116k swap on /dev/sdb2.  Priority:-1 extents:1 across:2008116k

The first time I ran fsck I got this:

fsck from util-linux-ng 2.16
e2fsck 1.41.9 (22-Aug-2009)
hda1: recovering journal
hda1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #0 (31170, counted=31169).
Fix<y>? yes

Free blocks count wrong (23376613, counted=23376612).
Fix<y>? yes

Free inodes count wrong for group #0 (8179, counted=8178).
Fix<y>? yes

Directories count wrong for group #0 (1, counted=2).
Fix<y>? yes

Free inodes count wrong (30493235, counted=30493234).
Fix<y>? yes

As soon as I ran ktorrent, I get the "read-only" disc error and the second time I ran fsck gave me this:

fsck from util-linux-ng 2.16
e2fsck 1.41.9 (22-Aug-2009)
hda1: recovering journal
hda1: clean, 38349/30531584 files, 98719387/122096000 blocks

And my error log contains a lot of this:

Oct 10 23:29:19 nemobot kernel: Buffer I/O error on device sda1, logical block 49020828

Oct 10 23:29:19 nemobot kernel: end_request: I/O error, dev sda, sector 392165663

Oct 10 23:29:17 nemobot kernel: ata2.00: cmd 61/20:40:1f:fd:5f/03:00:17:00:00/40 tag 8 ncq 409600 out
Oct 10 23:29:17 nemobot kernel: res 41/84:44:1f:fd:5f/84:00:17:00:00/40 Emask 0x10 (ATA bus error)
Oct 10 23:29:17 nemobot kernel: ata2.00: status: { DRDY ERR }
Oct 10 23:29:17 nemobot kernel: ata2.00: error: { ICRC ABRT }
Oct 10 23:29:18 nemobot kernel: ata2: EH in SWNCQ mode,QC:qc_active 0x1FF sactive 0x1FF
Oct 10 23:29:18 nemobot kernel: ata2: SWNCQ:qc_active 0x1FF defer_bits 0x0 last_issue_tag 0x8
Oct 10 23:29:18 nemobot kernel: dhfis 0x1FF dmafis 0x1 sdbfis 0x0
Oct 10 23:29:18 nemobot kernel: ata2: ATA_REG 0x41 ERR_REG 0x84
Oct 10 23:29:18 nemobot kernel: ata2: tag : dhfis dmafis sdbfis sacitve
Oct 10 23:29:18 nemobot kernel: ata2: tag 0x0: 1 1 0 1  
Oct 10 23:29:18 nemobot kernel: ata2: tag 0x1: 1 0 0 1  
Oct 10 23:29:18 nemobot kernel: ata2: tag 0x2: 1 0 0 1  
Oct 10 23:29:18 nemobot kernel: ata2: tag 0x3: 1 0 0 1  
Oct 10 23:29:18 nemobot kernel: ata2: tag 0x4: 1 0 0 1  
Oct 10 23:29:18 nemobot kernel: ata2: tag 0x5: 1 0 0 1  
Oct 10 23:29:18 nemobot kernel: ata2: tag 0x6: 1 0 0 1  
Oct 10 23:29:18 nemobot kernel: ata2: tag 0x7: 1 0 0 1  
Oct 10 23:29:18 nemobot kernel: ata2: tag 0x8: 1 0 0 1

Pomalo

Member

Registered: 2009-09-28

Posts: 17

Re: Disc keeps locking as "read only"

I had the same problem with transmission.

I reinstalled kernel2.6.31-5
Seems to work for now...