Glowworm or OS 1.15? bad mount/unmount and sdcard mount/stay umounted behavior?

[roustabout]

I can't tell if this is particular to my unit, or if it's a global problem (but I'll soon have a second unit to look at.)

My glowworm is unable to stably mount its internal partition for read/write by my computer. 

I have reset the device, completely erased the device, and restored from a disk-based backup made after registration but no other work was done on the device. 

When a USB cable is connected, the glowworm begins mounting and unmounting the internal storage for a few minutes or more, displaying the "usb connected" message and then not displaying it. 

The inserted sd card is mounted by the PC, but when I eject the card from the PC, the glowworm does not remount it.  Only a full shut down and start up will remount it. 

My device is currently using the stock uRamdisk and still exhibits this behavior. 

I have seen the behavior on two different cables and two different computers, even after usng USB Deview to remove all traces of the old Simple Touch from the registry.

When I booted the device from the Noogie disk to make my backup, the connection was rock-solid. 

Is anyone else seeing this? 

[roustabout]

Following up to my own message, the problem seems to have resolved on its own.  I'm stumped. 

As I was setting up to do logcat just now, I found that

a) my NST was exhibiting some of the same behavior

b) uninstalling many things from the NST, including nook touch tools, nook color tools and the refresh rate tools (the refresh rate tools were not installed on the glowworm) seem to have cleared the problem on the NST. 

c) the problem on the glowworm seems to have gone away...None of the eink tweaks were installed on the glowworm to start with. 

I can't explain any of what I'm seeing at this point, since my memory is that I'd given up on the glowworm last night and decided to set up for logcat this morning. 

I am pleased, though.

[roustabout]

As I was setting up to do logcat just now, I found that

a) my NST was exhibiting some of the same behavior

b) uninstalling many things from the NST, including nook touch tools, nook color tools and the refresh rate tools (the refresh rate tools were not installed on the glowworm) seem to have cleared the problem on the NST. 

c) the problem on the glowworm seems to have gone away...None of the eink tweaks were installed on the glowworm to start with. 

I can't explain any of what I'm seeing at this point, since my memory is that I'd given up on the glowworm last night and decided to set up for logcat this morning. 

I am pleased, though.

[AquaticAmethyst]

I don't understand most of what you just said, but I am glad your Glowworm is working again!  I don't think I've ever physically connected my NST to my computer for anything--I am still too new to e-readers to start sideloading any of my own content.  Keep us posted if anything strange happens again--I am interested in hearing the differences between the Glow and the NST. 

[Byteguy]

Just so others know, roustabout is talking about a rooted glowworm (used special programs to get under-the-hood to take control of the device and change it).

This isn't a report of a problem with a factory-standard unit.

It's a valid question and report of strangeness even if rooting voids the warrenty.  But, Aquatic and others don't need to worry if they're just using their device normally.

[keriflur]

It's also not a problem specific to the glow.  The NST has this issue also.

[nlstein]

So let me get this right. If I don't root my NST or Glow I won't void my warranty or have this problem? If that's right then the answer is simple - don't root and then complain.

[keriflur]

---

nlstein wrote:
So let me get this right. If I don't root my NST or Glow I won't void my warranty or have this problem? If that's right then the answer is simple - don't root and then complain.

---

Nope.  I'm not rooted and I have this problem on my NST, since 1.1.  So, not such a simple answer.

[nlstein]

Sorry. I misunderstood. I thought Byteguy said the unit was rooted. No?

[Byteguy]

---

keriflur wrote:

---

nlstein wrote:
So let me get this right. If I don't root my NST or Glow I won't void my warranty or have this problem? If that's right then the answer is simple - don't root and then complain.

---

Nope.  I'm not rooted and I have this problem on my NST, since 1.1.  So, not such a simple answer.

---

Very odd.  I'm nearly 100% sideload on an SD card and I've never had this problem; not once.  And, I tend to do a lot when on USB mode (I load books, delete books, change my mind, load different books..lather, rinse, and repeat until I give up trying to plan what I'll be reading more than 2 books down the road).

How big is your SD card?  I just have a 2GB.  Maybe it has something to do with the size and problems with HC reading?

[roustabout]

Yes, I was asking the question mostly to see if anyone with a stock Nook was seeing it.  In a different thread, Keriflur says she has seen her NST do things like this when the battery is running low.  

There is an additional change she may have made to her NST, but I'm not sure she has.  

I've customized my nooks pretty intensively, and an advantage to that is that I can run a tool called logcat which lets me see basically all of the things the device is doing, or write them to a file.  

My own hairball resolved on its own and the device has been chipper and well-behaved since.  : ) 

[keriflur]

---

Byteguy wrote:

---

keriflur wrote:

---

nlstein wrote:
So let me get this right. If I don't root my NST or Glow I won't void my warranty or have this problem? If that's right then the answer is simple - don't root and then complain.

---

Nope.  I'm not rooted and I have this problem on my NST, since 1.1.  So, not such a simple answer.

---

Very odd.  I'm nearly 100% sideload on an SD card and I've never had this problem; not once.  And, I tend to do a lot when on USB mode (I load books, delete books, change my mind, load different books..lather, rinse, and repeat until I give up trying to plan what I'll be reading more than 2 books down the road).

How big is your SD card?  I just have a 2GB.  Maybe it has something to do with the size and problems with HC reading?

---

Hmm, I want to say it's 4gb, so not that big, but I'll have to check for sure.

It only happens when I'm in the library or have a book open.  It's fine when I'm on the home page when I connect the nook, as long as the battery isn't low.  I assume it's trying to read data from the internal or SD storage when it's connected to the PC and then freaking out.

Mine's fully stock, no changes.

[frantastk]

---

keriflur wrote:

---

Byteguy wrote:

---

keriflur wrote:

---

nlstein wrote:
So let me get this right. If I don't root my NST or Glow I won't void my warranty or have this problem? If that's right then the answer is simple - don't root and then complain.

---

Nope.  I'm not rooted and I have this problem on my NST, since 1.1.  So, not such a simple answer.

---

Very odd.  I'm nearly 100% sideload on an SD card and I've never had this problem; not once.  And, I tend to do a lot when on USB mode (I load books, delete books, change my mind, load different books..lather, rinse, and repeat until I give up trying to plan what I'll be reading more than 2 books down the road).

How big is your SD card?  I just have a 2GB.  Maybe it has something to do with the size and problems with HC reading?

---

Hmm, I want to say it's 4gb, so not that big, but I'll have to check for sure.

It only happens when I'm in the library or have a book open.  It's fine when I'm on the home page when I connect the nook, as long as the battery isn't low.  I assume it's trying to read data from the internal or SD storage when it's connected to the PC and then freaking out.

Mine's fully stock, no changes.

---

That's weird. My NST has never done that. I also do some weird sideloading sometimes. I once hooked it up, sideloaded a couple hundred books to my sd card, then changed my mind, ejected, changed my mind again, remounted it, deleted everything, ejected it, then remembered I'd just deleted all my books and didn't have anything new to read, so remounted it and added a couple of books, and ejected it again. I can never seem to decide if I like keeping all my books on it or only a few, that and the fact I seem to always get interupted by little people when I'm in the middle of something and forget exactly why I've plugged it into the computer in the first place.

I know I've plugged it into my computer while on the homescreen, library, and while a book was open and have never had any problems. I have a 2 gb sd card if that matters (not sure why it should).

[nlstein]

From Byteguy's post: "Just so others know, roustabout is talking about a rooted glowworm (used special programs to get under-the-hood to take control of the device and change it). This isn't a report of a problem with a factory-standard unit. It's a valid question and report of strangeness even if rooting voids the warrenty. But, Aquatic and others don't need to worry if they're just using their device normally." This is where I got the idea that the unit with the unit was rooted. If the problem is happening on units that aren't then there must be something else going on. My NST has no problems like the one mentioned and I got it right when they started shipping.

[keriflur]

---

nlstein wrote:
From Byteguy's post: "Just so others know, roustabout is talking about a rooted glowworm (used special programs to get under-the-hood to take control of the device and change it). This isn't a report of a problem with a factory-standard unit. It's a valid question and report of strangeness even if rooting voids the warrenty. But, Aquatic and others don't need to worry if they're just using their device normally." This is where I got the idea that the unit with the unit was rooted. If the problem is happening on units that aren't then there must be something else going on. My NST has no problems like the one mentioned and I got it right when they started shipping.

---

That's when I got mine too.  The problem started after the 1.1 release.

[nlstein]

Sorry to hear you have a problem. I am running the latest software on a Mac and have no problems. Maybe it's not the Nook? I assume you've tried plugging in a standard thumb drive and that works fine.

[roustabout]

I initially thought this might be related to root, but when I restored to stock, I was still seeing the behavior. (That is, I took the exact copy of the whole device I made before I started working and overwrote everything, doing a restore to 10 minutes after I unboxed.) 

Keriflur's experience tells me there's something that can make this happen to stock NST's as well, which is helpful to know.  If I see it again, I will set up to trap the events and pass them on to BN -- it sounds as if I've run across something that can happen on the stock device, just not often. 

[gstone]

---

keriflur wrote:

.... The problem started after the 1.1 release.

---

I've seen this behavior on the original nook and once on the NST (v1.0).  I don't know how low the battery was in your case but in mine it was well after the warning messages about low battery charge.

I decided the USB port must not be fully powering the drive and just made sure the battery wasn't that low again before connecting.

[keriflur]

---

gstone wrote:

---

keriflur wrote:

.... The problem started after the 1.1 release.

---

I've seen this behavior on the original nook and once on the NST (v1.0).  I don't know how low the battery was in your case but in mine it was well after the warning messages about low battery charge.

I decided the USB port must not be fully powering the drive and just made sure the battery wasn't that low again before connecting.

---

The first time it happened it was really, really low.  The second time, I still had about 50% charge.  That was when I started to fuss with what screen the device was on when I connected it.

I don't connect very often, so I've probably only connected a dozen or so times since I got it (not including re-connects in the same session).

@nlstein - No, the issue is the nook not the computer.  Buying a mac isn't going to fix my issue. LOL.

[nlstein]

Glad to hear you've narrowed the problem down to the Nook and not the computer. I wouldn't dream of suggesting that buying a Mac would fix your issue. LOL Once the Nook was rooted all bets are off in my mind. If there's some that have the problem with very low battery but not ever rooted I can imagine that doesn't help. If it happens with a charged battery and units that were never rooted the possibility of finding the problem is even harder. Obviously, it's now going to be very hard to track down the problem now that it's gone. I don't remember hearing about this problem in the past. Has this happened to people in the recent past or always? Good luck. Keep us in the loop please.

[roustabout]

" If it happens with a charged battery and units that were never rooted the possibility of finding the problem is even harder"

If it repeats itself, I know that it may not be rooting related and because I am able to run the debugging tools, I can collect information that should be valuable if it starts to happen again.