09-08-2010, 04:45 AM | #1 |
Groupie
Posts: 185
Karma: 1110435
Join Date: Jul 2010
Location: Shanghai, China
Device: Sibrary G5
|
Calibre sets my reader to R/O
I've got a Sibrary G5, which Linux (I'm running Ubuntu 10.10) automounts (in my case at mountpoints /media/disk-1/ for the card and /media/BOOX Internal Memory for the internal memory). Using Dolphin (Ubuntu's file manager) or a command line I can copy files to the reader, rename, delete, the works, until I run Calibre. Calibre loads, detects the reader as a Boox, and then about thirty seconds later I get "Error communicating with device", and the following details:
Code:
(30, 'Read-only file system') Traceback (most recent call last): File "/home/kovid/build/calibre/src/calibre/gui2/device.py", line 68, in run File "/home/kovid/build/calibre/src/calibre/gui2/device.py", line 288, in _books File "/home/kovid/build/calibre/src/calibre/devices/usbms/driver.py", line 164, in books File "/home/kovid/build/calibre/src/calibre/devices/usbms/driver.py", line 303, in sync_booklists File "/home/kovid/build/calibre/src/calibre/devices/usbms/driver.py", line 301, in write_prefix IOError: [Errno 30] Read-only file system: u'/media/disk-1/.metadata.calibre' Any guesses? --Nathanael |
09-08-2010, 05:12 AM | #2 |
Wizard
Posts: 4,553
Karma: 950151
Join Date: Nov 2008
Device: Sony PRS-950, iphone/ipad (Marvin/iBooks/QuickReader)
|
Sounds as if you have two automounting systems fighting each other (system one and calibre one). When someone else reported a similar issue Kovid recommended either deleting (or renaming) the calibre automounter so that it no longer runs.
|
Advert | |
|
09-08-2010, 07:09 AM | #3 | |
Groupie
Posts: 185
Karma: 1110435
Join Date: Jul 2010
Location: Shanghai, China
Device: Sibrary G5
|
Quote:
Strike One: I turned up this, which creates a dummy /usr/bin/calibre-mount-helper, but that didn't fix my problem. Strike Two: So I renamed /opt/calibre/calibre-mount-helper. Same luck. Strike Three: So I un-renamed /opt/calibre/calibre-mount-helper, deleted the dummy /usr/bin/calibre-mount-helper, then unmounted my device (leaving it connected) in order to give Calibre a shot at mounting it itself. Same problem, slightly different details: Code:
(30, 'Read-only file system') Traceback (most recent call last): File "/home/kovid/build/calibre/src/calibre/gui2/device.py", line 68, in run File "/home/kovid/build/calibre/src/calibre/gui2/device.py", line 288, in _books File "/home/kovid/build/calibre/src/calibre/devices/usbms/driver.py", line 164, in books File "/home/kovid/build/calibre/src/calibre/devices/usbms/driver.py", line 303, in sync_booklists File "/home/kovid/build/calibre/src/calibre/devices/usbms/driver.py", line 301, in write_prefix IOError: [Errno 30] Read-only file system: u'/media/BOOX Internal Memory (1)/.metadata.calibre' |
|
09-08-2010, 07:50 AM | #4 |
Addict
Posts: 305
Karma: 78651
Join Date: May 2010
Location: New Brunswick, Canada
Device: Kobo, Kobo Wifi, Kobo Touch
|
I saw similar issues recently. I believe in my case I may have tried to connect my kobo while the devicev was attempting to access the internal memory. I am not certain though so I would need to retest
Tim |
09-08-2010, 11:07 AM | #5 |
creator of calibre
Posts: 44,419
Karma: 24044628
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
calibre contains no code that will ever mount a device in ro mode. Most linux kernels remount a filesystem in read only mode if filesystem errors are detected. Look at your system log to see if that is happening.
|
Advert | |
|
09-08-2010, 11:45 PM | #6 |
Not who you think I am...
Posts: 374
Karma: 30283
Join Date: Jan 2010
Location: Honolulu
Device: PocketBook 360 -- Ivory
|
I had a similar problem. I seem to have solved it by switching to a system automount system that doesn't use HAL.
How is Calibre doing automount? (No need to get into the weeds, just a general description would do.) |
09-08-2010, 11:54 PM | #7 |
creator of calibre
Posts: 44,419
Karma: 24044628
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
It call mount
|
09-09-2010, 12:42 AM | #8 |
Groupie
Posts: 185
Karma: 1110435
Join Date: Jul 2010
Location: Shanghai, China
Device: Sibrary G5
|
All solved
You were right about the filesystem errors, errors, Kovid. What threw me was that it turned out only .metadata.calibre was corrupted, so that I could write to the card all day long as long as I never touched .metadata.calibre. But as soon as I tried to copy it from the command line, syslog threw a few hundred errors, and the fs was set r/o.
So I renamed .metadat.calibre, hoping Calibre would rebuilt it, but as soon as Calibre tried to touch the card it was back to r/o. So I copied everything off, reformatted the card, and restored. I seem to be back in business, except that I can no longer see the reader's main memory (it's not even mounted in Linux), and Calibre sees the card as the reader's main memory. Thanks for the help. I hope everything's fixed. --Nathanael |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kobo sets date for new reader versions | Nate the great | News | 0 | 01-22-2010 09:08 AM |
Amazon Kindle sets sales records. | sibelhodge | News | 37 | 12-21-2009 06:56 AM |
Multi book sets - one file | lisa.m | Calibre | 0 | 10-16-2009 08:38 PM |
Data on Kindle character sets and font | susan_cassidy | Amazon Kindle | 1 | 02-13-2009 03:24 PM |
WildCharge sets a date for Wireless Charging | NatCh | News | 12 | 06-18-2007 09:22 AM |