Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Software > Calibre > Devices

Notices

Reply
 
Thread Tools Search this Thread
Old 03-08-2022, 05:35 AM   #1
Uncle Robin
Diligent dilettante
Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.
 
Uncle Robin's Avatar
 
Posts: 3,661
Karma: 52758936
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra Colour
[Kobo] Sage reboots when deleting books via Calibre

I'm not sure where the fault lies with this, but since it happens when using Calibre, I'm reporting it here. On the last two occasions that I have deleted batches of books by selecting "library and device", when the process is finished and I eject my Sage, the "importing content" progress bar shows up, then when the progress bar reaches the end, the devices reboots into the "Welcome to Kobo" screen and invites me to select a Wifi Network to begin the process of intialising the device. Happily, powering the device off then powering it back on restores the device to the previous state, minus the books that were successfully deleted. I'm about to downgrade to kobo 4.30 from 4.31 to see if that helps, but if there are any other suggestions, I'd be happy to hear them.

Last edited by Uncle Robin; 03-08-2022 at 01:38 PM.
Uncle Robin is offline   Reply With Quote
Old 03-08-2022, 06:37 AM   #2
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
I am pretty sure that is a side effect of the general issues with firmware 4.31 and the issues with connecting to the device. The issue is that something on the device is not letting the books partition unmount properly. And then all sorts of things happen. In this case, I suspect that when the device remounts the partition, it is mounted read-only. I have had some similar behaviour and was able to telnet in and see how the partition was mounted. As you found rebooting fixed it as the database hadn't been updated.

It's not strictly a calibre issue. The device was in a state where anything that accessed the database would have caused this. And I am not sure if it needed anything to access the database. It might have happened if you just accessed the drive. And if you had the scan-disk prompt from Windows and didn't, that might have been the trigger.
davidfor is offline   Reply With Quote
Advert
Old 03-08-2022, 01:41 PM   #3
Uncle Robin
Diligent dilettante
Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.
 
Uncle Robin's Avatar
 
Posts: 3,661
Karma: 52758936
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra Colour
Thanks David, I think I did get a scan disk prompt which I ignored. It will be interesting to see if it recurs now that my Sage is back to 4.30
Uncle Robin is offline   Reply With Quote
Old 03-08-2022, 04:06 PM   #4
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,047
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by Uncle Robin View Post
Thanks David, I think I did get a scan disk prompt which I ignored. It will be interesting to see if it recurs now that my Sage is back to 4.30
It was not just the Sage. My Libra2 had massive USB connection issue. It damaged the DB almost every time I transferred.
theducks is offline   Reply With Quote
Old 03-08-2022, 04:11 PM   #5
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,138
Karma: 168983734
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by theducks View Post
It was not just the Sage. My Libra2 had massive USB connection issue. It damaged the DB almost every time I transferred.
As @davidfor said, this seems to be an issue with the 4.31 firmware and the exposed partition is not being unmounted properly before being exposed to the USB connection.
DNSB is online now   Reply With Quote
Advert
Old 03-08-2022, 04:12 PM   #6
Uncle Robin
Diligent dilettante
Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.
 
Uncle Robin's Avatar
 
Posts: 3,661
Karma: 52758936
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra Colour
Quote:
Originally Posted by theducks View Post
It was not just the Sage. My Libra2 had massive USB connection issue. It damaged the DB almost every time I transferred.
Yes, I'd been reading about the Libra 2 problems. My Sage was not affected when I connected to update reading progress or to ADD books, only when I deleted. So I consider myself lucky.
Uncle Robin is offline   Reply With Quote
Old 03-09-2022, 11:59 AM   #7
Uncle Robin
Diligent dilettante
Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.
 
Uncle Robin's Avatar
 
Posts: 3,661
Karma: 52758936
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra Colour
Fwiw, I just deleted some 20 books in 3 or 4 batches, and my Sage (back on 4.30) behaved itself perfectly on ejecting it via Calibre, despite having again ignored the "there's a problem with this drive" message. So I'm putting the blame on 4.31
Uncle Robin is offline   Reply With Quote
Old 03-09-2022, 01:06 PM   #8
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,047
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by Uncle Robin View Post
Fwiw, I just deleted some 20 books in 3 or 4 batches, and my Sage (back on 4.30) behaved itself perfectly on ejecting it via Calibre, despite having again ignored the "there's a problem with this drive" message. So I'm putting the blame on 4.31
The drive is really corrupted. You should use Windows to correct that befor you lose other stuff.
A clue that 4.31 has issues, was multiple (USB device) connect/disconnect sounds (and the Kobo connect screen also seemed to repeat)
theducks is offline   Reply With Quote
Old 03-09-2022, 06:32 PM   #9
Uncle Robin
Diligent dilettante
Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.
 
Uncle Robin's Avatar
 
Posts: 3,661
Karma: 52758936
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra Colour
Quote:
Originally Posted by theducks View Post
The drive is really corrupted. You should use Windows to correct that befor you lose other stuff.
A clue that 4.31 has issues, was multiple (USB device) connect/disconnect sounds (and the Kobo connect screen also seemed to repeat)
The "there's a problem with this drive" message only comes up occasionallly, and not at all when I connect my device to USB while running KOReader, only Nickel. The behavior also matches that you describe with multiple USB connect/disconnect sounds and the kobo connect screen repeating. Again, not consistently and never in KOReader.
Uncle Robin is offline   Reply With Quote
Old 03-10-2022, 02:04 AM   #10
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by theducks View Post
The drive is really corrupted. You should use Windows to correct that befor you lose other stuff.
A clue that 4.31 has issues, was multiple (USB device) connect/disconnect sounds (and the Kobo connect screen also seemed to repeat)
I usually do the scan when the prompt is shown, but, I have rarely found the filesystem had any actual problems. But, the filesystem has the dirty flag set which is why the prompt is shown. The most likely reason for this is that something has a file opened and it was not released when the device attempted to unmount the partition. The problem for Kobo is working out what it is and why. And that's a fairly hard thing to do with the timing. The network gets turned off, so you cannot use telnet. The can use other means, but they have to see it happen. And they haven't. I am not seeing it consistently either.

If using KOReader the behaviour will be different. They don't work the same way, so hopefully they don't have the same bugs.
davidfor is offline   Reply With Quote
Old 03-10-2022, 03:13 AM   #11
Uncle Robin
Diligent dilettante
Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.
 
Uncle Robin's Avatar
 
Posts: 3,661
Karma: 52758936
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra Colour
Quote:
Originally Posted by davidfor View Post
I usually do the scan when the prompt is shown, but, I have rarely found the filesystem had any actual problems. But, the filesystem has the dirty flag set which is why the prompt is shown. The most likely reason for this is that something has a file opened and it was not released when the device attempted to unmount the partition. The problem for Kobo is working out what it is and why. And that's a fairly hard thing to do with the timing. The network gets turned off, so you cannot use telnet. The can use other means, but they have to see it happen. And they haven't. I am not seeing it consistently either.

If using KOReader the behaviour will be different. They don't work the same way, so hopefully they don't have the same bugs.

I made a point of connecting my Sage while in Nickel, to see and accept the "scan this disk?" message, but of course doing so guaranteed that I did not get the "there's a problem" message from Windows
Uncle Robin is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Calibre not deleting books on Kobo Aura H2O Gerard Lardner Devices 3 10-13-2019 04:49 PM
Aura ONE Kobo Aura One reboots when deleting epubs AbominableDavid Kobo Reader 15 09-04-2018 11:44 PM
New Calibre Kobo Driver allows deleting of Kobo Free books timlegge Kobo Reader 46 08-27-2011 10:16 PM
Kobo WIFI and deleting books with Calibre timlegge Kobo Reader 4 11-26-2010 02:16 AM


All times are GMT -4. The time now is 06:47 PM.


MobileRead.com is a privately owned, operated and funded community.