Re: strange behavior after reboot, iceweasel locking everything up
On Mon, 13 Aug 2012 17:07:53 -0400, Tony Baldwin wrote: On Mon, Aug 13, 2012 at 02:33:39PM +, Camaleón wrote: Okay, Tony, before going any further into this, are you sure that your hard disk and partitions are all fine? Were all the scary messages finally went away? How about the SMART test? There are no NEW such messages in dmesg. I ran fsck like 3 times, and the last time if finally ended with File system has been modified... and booted up fine without any more messages about a corrupt file system. That seems reassuring but I would also run the hard disk health tests from the hard disk manufacturer's utilities. And I'd do it just because it costs you nothing and to be sure because I don't like to play with this kind of errors as they can be really fatal ;-( Everything, except iceweasel, seems to be working normally. In the meantime, I am using SRWare's Iron browser, but would prefer to return to iceweasel. Okay, let's continue then with Iceweasel oddities. - Have you tried with an empty/fresh Icewasel profile? Nope. Not sure how that's done, but, anyway, the reason I want iceweasel back is to have all my bookmarks and settings and saved passwords, etc. This is the first thing to try because usually these problems are coming from your usual profile. Once you diagnose the problem then you can take whatever steps on how to proceed but at least you know what's happening. To test a new profile you can (among other options): a) Rename the current folder (e.g., from ~/.mozilla to ~/.mozilla_orig) and as soon as you launch Iceweasel again a new empty folder will be created. b) Or simply create a new user in your system, login with it and launch Icewasel. And check for the results. - Have you tried with upstream Firefox? No. Just Iceweasel 14 from backports. I try to use only debian packages. (Ok, I'm using iron, which is not a debian pkg, but our chromium is very old and out of date. Midori, arora, kazehake, and every other browser we have in repos suck. Iceape is working, and I may use that, but still, prefer my iceweasel). This would be another good test but well, that decission is, of course, up to you. Just to mention that Firefox (the upstream package) works smoothly in my old Lenny system and is very easy to maintain/update. - What does top say when system runs slowly? That's the weird part. I run htop. It will say, with iceweasel running, that I'm still only using like 1 or 2% cpu and 2 to 4 % ram. You mean the Iceweasel GUI is lagging but you see nothing strange in its process? No big amount of ram or cpu used by the browser nor any other application? :-? The (sluggish) behaviour you're getting is not normal, even more with a powerful computer like yours where Iceweasel has to run super-smoothly and flawlessly. It was, in fact, until this recent matter. A friend tells me he also is having similar issues, with iceweasel 14, and they only started after a reboot. Iceweasel was last updated sometime last week, I believe, when I ran updates. I had not rebooted (generally don't) until Saturday, and then this started, after the reboot. That points to a profile issue, indeed. In my case, to avoid that, I continously open/close the browser, remove all cookies, history and temporal data and keep no passwords saved. Yes, I'm not usual user-case, I know but this allows me to have a clean and bright Firefox experience :-) I have reinstalled iceweasel a couple of time, but nothing changes. Reinstalling makes no changes in your current profile, is kept as is. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k0dlt8$vu0$5...@dough.gmane.org
Re: strange behavior after reboot, iceweasel locking everything up
[78506.185358] sd 5:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed Sorry but you have already lost data. Avoid using the disk as it is no longer able to function reliably. Replace it asap. ddrescue is a good tool in these situations. But probably best to re-install from scratch and restore your data from a backup - but from a backup prior to when the disk errors started. Sadly, backups since may have some good data but those backups will contain corrupt files. Best wishes, Berni -- Confidence is what you have before you understand a problem - Woody Allen -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5028a5c3.4080...@gmail.com
Re: strange behavior after reboot, iceweasel locking everything up
On Sun, 12 Aug 2012 21:43:33 -0400, Tony Baldwin wrote: On Sun, Aug 12, 2012 at 08:10:07PM -0400, Tony Baldwin wrote: (...) Nope. Still hangingiceweasel hangs a long time just trying to grab pages, and I can't even go to another tab or something. The whole browser just locks up, for as much as a minute or two, when trying to load a page. It's become almost useless. I mean, what's the point in tabbed browsing if you can't read one tab while waiting for another to load? Okay, Tony, before going any further into this, are you sure that your hard disk and partitions are all fine? Were all the scary messages finally went away? How about the SMART test? If this is all good, then we can go on... if no, your priority should be the hard disk at first place. Now, in regards to your Iceweasel problems, some basic questions: - Have you tried with an empty/fresh Icewasel profile? - Have you tried with upstream Firefox? - What does top say when system runs slowly? The (sluggish) behaviour you're getting is not normal, even more with a powerful computer like yours where Iceweasel has to run super-smoothly and flawlessly. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k0b382$9nn$7...@dough.gmane.org
Re: strange behavior after reboot, iceweasel locking everything up
On Mon, Aug 13, 2012 at 02:33:39PM +, Camaleón wrote: On Sun, 12 Aug 2012 21:43:33 -0400, Tony Baldwin wrote: On Sun, Aug 12, 2012 at 08:10:07PM -0400, Tony Baldwin wrote: (...) Nope. Still hangingiceweasel hangs a long time just trying to grab pages, and I can't even go to another tab or something. The whole browser just locks up, for as much as a minute or two, when trying to load a page. It's become almost useless. I mean, what's the point in tabbed browsing if you can't read one tab while waiting for another to load? Okay, Tony, before going any further into this, are you sure that your hard disk and partitions are all fine? Were all the scary messages finally went away? How about the SMART test? There are no NEW such messages in dmesg. I ran fsck like 3 times, and the last time if finally ended with File system has been modified... and booted up fine without any more messages about a corrupt file system. Everything, except iceweasel, seems to be working normally. In the meantime, I am using SRWare's Iron browser, but would prefer to return to iceweasel. If this is all good, then we can go on... if no, your priority should be the hard disk at first place. Now, in regards to your Iceweasel problems, some basic questions: - Have you tried with an empty/fresh Icewasel profile? Nope. Not sure how that's done, but, anyway, the reason I want iceweasel back is to have all my bookmarks and settings and saved passwords, etc. - Have you tried with upstream Firefox? No. Just Iceweasel 14 from backports. I try to use only debian packages. (Ok, I'm using iron, which is not a debian pkg, but our chromium is very old and out of date. Midori, arora, kazehake, and every other browser we have in repos suck. Iceape is working, and I may use that, but still, prefer my iceweasel). - What does top say when system runs slowly? That's the weird part. I run htop. It will say, with iceweasel running, that I'm still only using like 1 or 2% cpu and 2 to 4 % ram. The (sluggish) behaviour you're getting is not normal, even more with a powerful computer like yours where Iceweasel has to run super-smoothly and flawlessly. It was, in fact, until this recent matter. A friend tells me he also is having similar issues, with iceweasel 14, and they only started after a reboot. Iceweasel was last updated sometime last week, I believe, when I ran updates. I had not rebooted (generally don't) until Saturday, and then this started, after the reboot. I have reinstalled iceweasel a couple of time, but nothing changes. ./tony -- http://www.tonybaldwin.me all tony, all the time! 3F330C6E signature.asc Description: Digital signature
Re: strange behavior after reboot, iceweasel locking everything up
Tony Baldwin wrote: Camaleón wrote: Okay, Tony, before going any further into this, are you sure that your hard disk and partitions are all fine? Were all the scary messages finally went away? How about the SMART test? There are no NEW such messages in dmesg. I was really worried there too. Those looked like a hardware related issue, not a software related issue. Probably just a cable but still. With the error from the syslog I would want to verify by unplugging and plugging back in the SATA cables. The older ones did not have any locks and would sometimes become dislodged. And even the newer ones might have a spot of corrosion on the connector that would be fixed by the remove and replace of the connector. These problems can show up after getting a thump from something like kicking out the power cord. Even just simple continuous vibration from the fans can cause things to walk around a little. I ran fsck like 3 times, and the last time if finally ended with File system has been modified... If there is a hardware issue be cautious about running fsck too early. The disk might be perfectly fine but getting a corrupted signal from a bad cable and the fsck modifications might actually be unneeded. Nope. Not sure how that's done, but, anyway, the reason I want iceweasel back is to have all my bookmarks and settings and saved passwords, etc. Firefox has had such a history of problems that they wrote automatic backup of bookmarks into the browser! Well if they have a problem then they might as well add code to work around it. Go to Bookmarks, Show All Bookmarks, to pop up a bookmark managment dialog. Then review the Import and Backup tab, Restore, and it should list a set of days of backups from which you can restore bookmarks. (These are actually json files in the .mozilla/firefox directory in your $HOME.) The rest of your history is stored in sqlite files. I have fished through them at various times. The point of all of this is that I have seen Firefox get very confused due to problems with the state of the .mozilla files. Never with my own desktop but routinely at a site with a substandard NFS mounted home directory environment. In order to recover there I often shutdown firefox, move their entire .mozilla directory out of the way, and then copy the bookmarks directory back, then start firefox back up again and restore the bookmarks. That has always worked and gets people running again with all of their bookmarks. Most of them don't care about their form history. I would imagine that it would be possible to carefully restore the sqlite files too. Just an idea for you. YMMV and all of that. (Ok, I'm using iron, which is not a debian pkg, but our chromium is very old and out of date. Midori, arora, kazehake, and every other browser we have in repos suck. Iceape is working, and I may use that, but still, prefer my iceweasel). I am a big advocate of http://mozilla.debian.net/ squeeze backport for stable. 14.0.1-1~bpo60+1 is current there as of today and that is the same as the mozilla.org upstream. That's the weird part. I run htop. It will say, with iceweasel running, that I'm still only using like 1 or 2% cpu and 2 to 4 % ram. Recently there was a kernel semaphore lockfile interaction that could be seen in firefox and other programs. You might want to check that you have the kernel upgrades appropriate for your release. If they are mismatched it is possible that might cause you a similar problem. Don't know but seems like a good thing to verify. It was, in fact, until this recent matter. A friend tells me he also is having similar issues, with iceweasel 14, and they only started after a reboot. Iceweasel was last updated sometime last week, I believe, when I ran updates. I had not rebooted (generally don't) until Saturday, and then this started, after the reboot. See that sounds similar to the recent kernel semaphore issue. But perhaps in reverse. Don't know. But this is the one I am talking about. https://lkml.org/lkml/2012/7/1/11 Not saying that is your problem. Just something I would verify that you have the appropriate kernel and userland. This is all old news now that a month has passed and I am not seeing this problem anywhere with the stock packages. But working fine and then not after a reboot sounds like a potentially similar issue. Bob signature.asc Description: Digital signature
Re: strange behavior after reboot, iceweasel locking everything up
On 12 August 2012 17:45, Tony Baldwin t...@tonybaldwin.org wrote:
Yesterday I had to reboot my machine.
Cleaning house, I had dislodged the plug for a power strip that powered
the computer, monitor, and printer.
Now, I am seeing very odd behavior.
Iceweasel hangs forever on some of the simplest tasks, such as loading a
static html page.
Not only that, but when it does so, other tasks on my machine are held
up. For instance, if I have iceweasel loading a page on my first
workspace, and try to load a message in mutt on another, mutt waits for
iceweasel to finish what it's doing before proceeding, which was not
previously the case.
I find this very, very odd.
Or even opening a terminal, for instance, a terminator, hangs, waiting
for iceweasel to finish its task.
It's as though iceweasel has dibs on system resources, and is blocking
other applications from using them, even when iceweasel, itself, is
using very few resources.
Now, when this is happening, I do not see any spikes in resource usage
that would explain slowing or stopping the entire machine while
iceweasel does its thing.
For instance, the machine will be using 2% of CPU and 4% of ram, but be
completely dormant until iceweasel succeeds in downloading a page.
This machine is a 2.8ghz x 4core AMD APU with 16gb of ram, too, so I'm
not exactly lacking in resources.
The only anomalies I have noted in dmesg, etc., are that some sectors of
my hdd are not reading correctly, or something.
A file system check forced on a second reboot yesterday failed, which is
disconcerting, but I'm not certain what to make of that.
dmesg | tail gives me
[79477.080607] ata6.00: failed command: READ DMA EXT
[79477.080621] ata6.00: cmd 25/00:08:9d:23:9f/00:00:6c:00:00/e0 tag 0
dma 4096 in
[79477.080624] res 51/40:00:9d:23:9f/40:00:6c:00:00/00 Emask
0x9 (media error)
[79477.080631] ata6.00: status: { DRDY ERR }
[79477.080635] ata6.00: error: { UNC }
[79477.196994] ata6.00: configured for UDMA/33
[78506.185310] sd 5:0:0:0: [sda] Unhandled sense code
[78506.185315] sd 5:0:0:0: [sda] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[78506.185322] sd 5:0:0:0: [sda] Sense Key : Medium Error [current]
[descriptor]
[78506.185331] Descriptor sense data with sense descriptors (in hex):
[78506.185335] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[78506.185351] 6c 9f 23 9d
[78506.185358] sd 5:0:0:0: [sda] Add. Sense: Unrecovered read error -
auto reallocate failed
[78506.185368] sd 5:0:0:0: [sda] CDB: Read(10): 28 00 6c 9f 23 9d 00 00
08 00
[78506.185378] end_request: I/O error, dev sda, sector 1822368669
[78506.185398] ata6: EH complete
I don't know what to make of that.
Before the reboot yesterday, the machine was working awesomely.
This is Debian Stable, AMD64, as mentioned on a 2.8ghz x 4core AMD APU
with 16gb ram.
I use Openbox window manager with no DE (which further keeps things
generally humming long quite efficiently).
The machine is only 8 months old, essentially (mobo, cpu, ram all
purchased in January, although the hdd is over a year old, about 1 year
and a half, really, so still not very old).
What is going on here?
I ran aptitude update safe-upgrade yesterday (had been about a week),
so everything is up to date.
./tony
Seems like the disk has some damage from when you pulled the plug.
Probably best to do a file system check from a live medium.
--
Sent from FOSS (Free Open Source Software)
Debian GNU/Linux
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAL36VG=qVTBg8e2eyYEOvL=yrAkUEmNv=434x9i+oK4=buc...@mail.gmail.com
Re: strange behavior after reboot, iceweasel locking everything up
On Sun, 12 Aug 2012 12:45:03 -0400, Tony Baldwin wrote:
Yesterday I had to reboot my machine. Cleaning house, I had dislodged
the plug for a power strip that powered the computer, monitor, and
printer.
Now, I am seeing very odd behavior.
(...)
The only anomalies I have noted in dmesg, etc., are that some sectors of
my hdd are not reading correctly, or something. A file system check
forced on a second reboot yesterday failed, which is disconcerting, but
I'm not certain what to make of that.
dmesg | tail gives me
[79477.080607] ata6.00: failed command: READ DMA EXT
[79477.080621] ata6.00: cmd 25/00:08:9d:23:9f/00:00:6c:00:00/e0 tag 0 dma
4096 in
[79477.080624] res 51/40:00:9d:23:9f/40:00:6c:00:00/00 Emask 0x9
(media error)
[79477.080631] ata6.00: status: { DRDY ERR }
[79477.080635] ata6.00: error: { UNC } [79477.196994] ata6.00: configured for
UDMA/33
[78506.185310] sd 5:0:0:0: [sda] Unhandled sense code
[78506.185315] sd 5:0:0:0: [sda] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[78506.185322] sd 5:0:0:0: [sda] Sense Key : Medium Error [current]
[descriptor]
[78506.185331] Descriptor sense data with sense descriptors (in hex):
[78506.185335] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[78506.185351] 6c 9f 23 9d
[78506.185358] sd 5:0:0:0: [sda] Add. Sense: Unrecovered read error - auto
reallocate failed
[78506.185368] sd 5:0:0:0: [sda] CDB: Read(10): 28 00 6c 9f 23 9d 00 00 08 00
[78506.185378] end_request: I/O error, dev sda, sector 1822368669
[78506.185398] ata6: EH complete
I don't know what to make of that.
(...)
Wow! Just to prevent from a disaster, ensure you have a full and updated backup
copy of your whole data. Then you can proceed with some basic tests:
1/ Check the cabling inside the computer, mainly sata cables, they could have
been
moved or be badly seated (ensure that all sata connectors are firmly tighten).
2/ Use sata quality cables when possible. For testing purposes, you can try
with a
different sata cable, at least for the device attached to ata6.00 port
(dmesg | grep -i ata6.00 will tell what's hanging there).
3/ Download the disk utilities from the hard disk manufacturer (which usually
runs
from an ISO livecd) and scan your hard disks for smart or another errors
(always run
soft/non-destructive tests).
4/ From a LiveCD, you can additionaly get the results from smartcl long test
mode
to compare with the results from step 3/.
And provide the results of all these set of tests :-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/k08o9u$fer$2...@dough.gmane.org
Re: strange behavior after reboot, iceweasel locking everything up
On Sun, Aug 12, 2012 at 12:45:03PM -0400, Tony Baldwin wrote:
Yesterday I had to reboot my machine.
Cleaning house, I had dislodged the plug for a power strip that powered
the computer, monitor, and printer.
Now, I am seeing very odd behavior.
Iceweasel hangs forever on some of the simplest tasks, such as loading a
static html page.
Not only that, but when it does so, other tasks on my machine are held
up. For instance, if I have iceweasel loading a page on my first
workspace, and try to load a message in mutt on another, mutt waits for
iceweasel to finish what it's doing before proceeding, which was not
previously the case.
I find this very, very odd.
I've suffered the same problem, very annoying. A ps indicates its
plugin-container, have to wait for ages to get mouse response so I can
quit iceweasel.
It seems to happen sometimes If I leave iceweasel open for a long time.
I have installed noscript (highly recommended!) but am not sure if it is
a script causing it. Once there was a message about a script being busy,
which tied up iceweasel and that was before I installed noscript. There
was a dialog box indicating this.
For instance, the machine will be using 2% of CPU and 4% of ram, but be
completely dormant until iceweasel succeeds in downloading a page.
This machine is a 2.8ghz x 4core AMD APU with 16gb of ram, too, so I'm
not exactly lacking in resources.
Mmmm, is this from ps?
The only anomalies I have noted in dmesg, etc., are that some sectors of
my hdd are not reading correctly, or something.
A file system check forced on a second reboot yesterday failed, which is
disconcerting, but I'm not certain what to make of that.
eeek! Grab any data you need, quick.
dmesg | tail gives me
[79477.080607] ata6.00: failed command: READ DMA EXT
[79477.080621] ata6.00: cmd 25/00:08:9d:23:9f/00:00:6c:00:00/e0 tag 0
dma 4096 in
[79477.080624] res 51/40:00:9d:23:9f/40:00:6c:00:00/00 Emask
0x9 (media error)
[79477.080631] ata6.00: status: { DRDY ERR }
[79477.080635] ata6.00: error: { UNC }
[79477.196994] ata6.00: configured for UDMA/33
[78506.185310] sd 5:0:0:0: [sda] Unhandled sense code
[78506.185315] sd 5:0:0:0: [sda] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[78506.185322] sd 5:0:0:0: [sda] Sense Key : Medium Error [current]
[descriptor]
[78506.185331] Descriptor sense data with sense descriptors (in hex):
[78506.185335] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[78506.185351] 6c 9f 23 9d
[78506.185358] sd 5:0:0:0: [sda] Add. Sense: Unrecovered read error -
auto reallocate failed
[78506.185368] sd 5:0:0:0: [sda] CDB: Read(10): 28 00 6c 9f 23 9d 00 00
08 00
[78506.185378] end_request: I/O error, dev sda, sector 1822368669
[78506.185398] ata6: EH complete
I don't know what to make of that.
Hard disk *could* be on way out. Get a testdisk, or use smartctl, but
I'd treat it as though its going to fail any minute and get any crucial
data off it now!
But just a heads up about iceweasel problems. So not necessarily related
to hdd errors.
--
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing. --- Malcolm X
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120812171318.GA20524@tal
Re: strange behavior after reboot, iceweasel locking everything up
On Sun, August 12, 2012 1:13 pm, Chris Bannister wrote: On Sun, Aug 12, 2012 at 12:45:03PM -0400, Tony Baldwin wrote: Yesterday I had to reboot my machine. Cleaning house, I had dislodged the plug for a power strip that powered the computer, monitor, and printer. Now, I am seeing very odd behavior. Iceweasel hangs forever on some of the simplest tasks, such as loading a static html page. Not only that, but when it does so, other tasks on my machine are held up. For instance, if I have iceweasel loading a page on my first workspace, and try to load a message in mutt on another, mutt waits for iceweasel to finish what it's doing before proceeding, which was not previously the case. I find this very, very odd. I've suffered the same problem, very annoying. A ps indicates its plugin-container, have to wait for ages to get mouse response so I can quit iceweasel. Yes, the only thing I see in htop, for instance, that seems odd is way too many flash-plugins running, or something. It seems to happen sometimes If I leave iceweasel open for a long time. I have installed noscript (highly recommended!) but am not sure if it is a script causing it. Once there was a message about a script being busy, which tied up iceweasel and that was before I installed noscript. There was a dialog box indicating this. For instance, the machine will be using 2% of CPU and 4% of ram, but be completely dormant until iceweasel succeeds in downloading a page. This machine is a 2.8ghz x 4core AMD APU with 16gb of ram, too, so I'm not exactly lacking in resources. Mmmm, is this from ps? Well, I can see cpu and memory use in a small conky I keep running, but I was also looking with htop (not ps). These should all show about the same thing, anyway. I mean, htop and ps will show processes, whereas conky only gives % of cpu/ram usage, but otherwise. The only anomalies I have noted in dmesg, etc., are that some sectors of my hdd are not reading correctly, or something. A file system check forced on a second reboot yesterday failed, which is disconcerting, but I'm not certain what to make of that. eeek! Grab any data you need, quick. I ran a back-up since my initial message. Manually running fsck now. ./tony -- http://tonybaldwin.me all tony, all the time -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21fc286397eb98d61c62cfe7169886db.squir...@tonybaldwin.org
Re: strange behavior after reboot, iceweasel locking everything up
On Sun, August 12, 2012 1:14 pm, Camale�n wrote:
On Sun, 12 Aug 2012 12:45:03 -0400, Tony Baldwin wrote:
Yesterday I had to reboot my machine. Cleaning house, I had dislodged
the plug for a power strip that powered the computer, monitor, and
printer.
Now, I am seeing very odd behavior.
(...)
The only anomalies I have noted in dmesg, etc., are that some sectors of
my hdd are not reading correctly, or something. A file system check
forced on a second reboot yesterday failed, which is disconcerting, but
I'm not certain what to make of that.
dmesg | tail gives me
[79477.080607] ata6.00: failed command: READ DMA EXT
[79477.080621] ata6.00: cmd 25/00:08:9d:23:9f/00:00:6c:00:00/e0 tag 0
dma 4096 in
[79477.080624] res 51/40:00:9d:23:9f/40:00:6c:00:00/00 Emask
0x9 (media error)
[79477.080631] ata6.00: status: { DRDY ERR }
[79477.080635] ata6.00: error: { UNC } [79477.196994] ata6.00:
configured for UDMA/33
[78506.185310] sd 5:0:0:0: [sda] Unhandled sense code
[78506.185315] sd 5:0:0:0: [sda] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[78506.185322] sd 5:0:0:0: [sda] Sense Key : Medium Error [current]
[descriptor]
[78506.185331] Descriptor sense data with sense descriptors (in hex):
[78506.185335] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[78506.185351] 6c 9f 23 9d
[78506.185358] sd 5:0:0:0: [sda] Add. Sense: Unrecovered read error -
auto reallocate failed
[78506.185368] sd 5:0:0:0: [sda] CDB: Read(10): 28 00 6c 9f 23 9d 00 00
08 00
[78506.185378] end_request: I/O error, dev sda, sector 1822368669
[78506.185398] ata6: EH complete
I don't know what to make of that.
(...)
Wow! Just to prevent from a disaster, ensure you have a full and updated
backup
copy of your whole data. Then you can proceed with some basic tests:
1/ Check the cabling inside the computer, mainly sata cables, they could
have been
moved or be badly seated (ensure that all sata connectors are firmly
tighten).
2/ Use sata quality cables when possible. For testing purposes, you can
try with a
different sata cable, at least for the device attached to ata6.00 port
(dmesg | grep -i ata6.00 will tell what's hanging there).
3/ Download the disk utilities from the hard disk manufacturer (which
usually runs
from an ISO livecd) and scan your hard disks for smart or another errors
(always run
soft/non-destructive tests).
4/ From a LiveCD, you can additionaly get the results from smartcl long
test mode
to compare with the results from step 3/.
And provide the results of all these set of tests :-)
Greetings,
--
Camaleón
I did a back-up moments after writing my initial message on this thread.
I rebooted to single-user mode and am running fsck -t ext3 /dev/sda6 right
now (/home partition, where the problem seems to be).
Oddly, I don't have a livecd on hand.
I did my most recent installations all from a usb stick.
(writing from another machine, a laptop with no optical drive to burn a cd).
./tony
--
http://tonybaldwin.me
all tony, all the time
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/e3f894dc60e6f170a18cb917f668cf58.squir...@tonybaldwin.org
Re: strange behavior after reboot, iceweasel locking everything up
On Sun, Aug 12, 2012 at 05:08:16PM -0400, tony baldwin wrote:
On Sun, August 12, 2012 1:14 pm, Camale�n wrote:
On Sun, 12 Aug 2012 12:45:03 -0400, Tony Baldwin wrote:
Yesterday I had to reboot my machine. Cleaning house, I had dislodged
the plug for a power strip that powered the computer, monitor, and
printer.
Now, I am seeing very odd behavior.
(...)
The only anomalies I have noted in dmesg, etc., are that some sectors of
my hdd are not reading correctly, or something. A file system check
forced on a second reboot yesterday failed, which is disconcerting, but
I'm not certain what to make of that.
dmesg | tail gives me
[79477.080607] ata6.00: failed command: READ DMA EXT
[79477.080621] ata6.00: cmd 25/00:08:9d:23:9f/00:00:6c:00:00/e0 tag 0
dma 4096 in
[79477.080624] res 51/40:00:9d:23:9f/40:00:6c:00:00/00 Emask
0x9 (media error)
[79477.080631] ata6.00: status: { DRDY ERR }
[79477.080635] ata6.00: error: { UNC } [79477.196994] ata6.00:
configured for UDMA/33
[78506.185310] sd 5:0:0:0: [sda] Unhandled sense code
[78506.185315] sd 5:0:0:0: [sda] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[78506.185322] sd 5:0:0:0: [sda] Sense Key : Medium Error [current]
[descriptor]
[78506.185331] Descriptor sense data with sense descriptors (in hex):
[78506.185335] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[78506.185351] 6c 9f 23 9d
[78506.185358] sd 5:0:0:0: [sda] Add. Sense: Unrecovered read error -
auto reallocate failed
[78506.185368] sd 5:0:0:0: [sda] CDB: Read(10): 28 00 6c 9f 23 9d 00 00
08 00
[78506.185378] end_request: I/O error, dev sda, sector 1822368669
[78506.185398] ata6: EH complete
I don't know what to make of that.
(...)
I did a back-up moments after writing my initial message on this thread.
I rebooted to single-user mode and am running fsck -t ext3 /dev/sda6 right
now (/home partition, where the problem seems to be).
Oddly, I don't have a livecd on hand.
I did my most recent installations all from a usb stick.
(writing from another machine, a laptop with no optical drive to burn a cd).
So, I manually ran fsck, had to do it three time, but I'm now getting a
clean bill of health (log in /var/log/fsck/checkfs says all good) on the
hdd.
Removing mongodb seems to have maybe been a factor (not sure why I had
it installed, anyway...some python thing I was going to play with but
didn't, I believe, required it).
Still having issues with iceweasel, however, being very, very slow in
loading pages and stuff and other applications hanging at the same time.
Even something as innocuous as running ls in a terminal will hang and
wait until iceweasel is done, so very weird.
Iceweasel will blank out, too, so I can not even read another tab or
something while waiting for a new tab to load a page, etc.
It does one of those things where, say, if I go to workspace 2 while
iceweasel is loading a page, workspace 2 being always a terminator
terminal full screen, then go back to workspace 1 (iceweasel), I see the
terminal where the iceweasel window should be.
Or if I go to another workspace that's empty, then go back to wordspace
1, I see the top-bar of the iceweasel window, and the empy desktop.
Weird.
./tony
--
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E
signature.asc
Description: Digital signature
Re: strange behavior after reboot, iceweasel locking everything up
On Sun, Aug 12, 2012 at 06:26:34PM -0400, Tony Baldwin wrote: On Sun, Aug 12, 2012 at 05:08:16PM -0400, tony baldwin wrote: On Sun, August 12, 2012 1:14 pm, Camale�n wrote: On Sun, 12 Aug 2012 12:45:03 -0400, Tony Baldwin wrote: Yesterday I had to reboot my machine. Cleaning house, I had dislodged the plug for a power strip that powered the computer, monitor, and printer. Now, I am seeing very odd behavior. ... clippage ... So, I manually ran fsck, had to do it three time, but I'm now getting a clean bill of health (log in /var/log/fsck/checkfs says all good) on the hdd. Removing mongodb seems to have maybe been a factor (not sure why I had it installed, anyway...some python thing I was going to play with but didn't, I believe, required it). Still having issues with iceweasel, however, being very, very slow in loading pages and stuff and other applications hanging at the same time. Even something as innocuous as running ls in a terminal will hang and wait until iceweasel is done, so very weird. Iceweasel will blank out, too, so I can not even read another tab or something while waiting for a new tab to load a page, etc. It does one of those things where, say, if I go to workspace 2 while iceweasel is loading a page, workspace 2 being always a terminator terminal full screen, then go back to workspace 1 (iceweasel), I see the terminal where the iceweasel window should be. Or if I go to another workspace that's empty, then go back to wordspace 1, I see the top-bar of the iceweasel window, and the empy desktop. Weird. The problem now is definitely something to do with iceweasel. I do not have the problem of stuff locking up when iceweasel is not running. I can use google-chrome without issue (but do not want to use chrome. I want to use iceweasel. I do not want google tracking me all over the internet). ./tony -- http://www.tonybaldwin.me all tony, all the time! 3F330C6E signature.asc Description: Digital signature
Re: strange behavior after reboot, iceweasel locking everything up
On Sun, Aug 12, 2012 at 06:39:05PM -0400, Tony Baldwin wrote: On Sun, Aug 12, 2012 at 06:26:34PM -0400, Tony Baldwin wrote: On Sun, Aug 12, 2012 at 05:08:16PM -0400, tony baldwin wrote: On Sun, August 12, 2012 1:14 pm, Camale�n wrote: On Sun, 12 Aug 2012 12:45:03 -0400, Tony Baldwin wrote: Yesterday I had to reboot my machine. Cleaning house, I had dislodged the plug for a power strip that powered the computer, monitor, and printer. Now, I am seeing very odd behavior. ... clippage ... Still having issues with iceweasel, however, being very, very slow in loading pages and stuff and other applications hanging at the same time. Even something as innocuous as running ls in a terminal will hang and wait until iceweasel is done, so very weird. Iceweasel will blank out, too, so I can not even read another tab or something while waiting for a new tab to load a page, etc. It does one of those things where, say, if I go to workspace 2 while iceweasel is loading a page, workspace 2 being always a terminator terminal full screen, then go back to workspace 1 (iceweasel), I see the terminal where the iceweasel window should be. Or if I go to another workspace that's empty, then go back to wordspace 1, I see the top-bar of the iceweasel window, and the empy desktop. Weird. The problem now is definitely something to do with iceweasel. I do not have the problem of stuff locking up when iceweasel is not running. I can use google-chrome without issue (but do not want to use chrome. I want to use iceweasel. I do not want google tracking me all over the internet). Okay, so I did some digging around, and found out I had 4 xulrunners installed (I was seeing a lot of xulrunner in htop with iceweasel running, and wondering if this was somehow at fault). I completely removed all of them, which, of course, took iceweasel with it. I then reinstalled iceweasel (14, from backports) and it brought back only one xulrunner, being xulrunner-14. Things seem to be normal now. It seems perhaps too much xulrunner was maybe the source of the iceweasel problem. The hdd problem seems solved, too, from my manual fscking. ./tony -- http://www.tonybaldwin.me all tony, all the time! 3F330C6E signature.asc Description: Digital signature
Re: strange behavior after reboot, iceweasel locking everything up
On Sun, Aug 12, 2012 at 08:10:07PM -0400, Tony Baldwin wrote: On Sun, Aug 12, 2012 at 06:39:05PM -0400, Tony Baldwin wrote: On Sun, Aug 12, 2012 at 06:26:34PM -0400, Tony Baldwin wrote: On Sun, Aug 12, 2012 at 05:08:16PM -0400, tony baldwin wrote: On Sun, August 12, 2012 1:14 pm, Camale�n wrote: On Sun, 12 Aug 2012 12:45:03 -0400, Tony Baldwin wrote: Yesterday I had to reboot my machine. Cleaning house, I had dislodged the plug for a power strip that powered the computer, monitor, and printer. Now, I am seeing very odd behavior. ... clippage ... The problem now is definitely something to do with iceweasel. I do not have the problem of stuff locking up when iceweasel is not running. I can use google-chrome without issue (but do not want to use chrome. I want to use iceweasel. I do not want google tracking me all over the internet). Okay, so I did some digging around, and found out I had 4 xulrunners installed (I was seeing a lot of xulrunner in htop with iceweasel running, and wondering if this was somehow at fault). I completely removed all of them, which, of course, took iceweasel with it. I then reinstalled iceweasel (14, from backports) and it brought back only one xulrunner, being xulrunner-14. Things seem to be normal now. Nope. Still hangingiceweasel hangs a long time just trying to grab pages, and I can't even go to another tab or something. The whole browser just locks up, for as much as a minute or two, when trying to load a page. It's become almost useless. I mean, what's the point in tabbed browsing if you can't read one tab while waiting for another to load? ./tony -- http://www.tonybaldwin.me all tony, all the time! 3F330C6E signature.asc Description: Digital signature
