| Autor |
Nachricht |
|
|
Titel: lockup at startup
 Verfasst am: 30.09.2006, 16:51 Uhr
|
|
Anmeldung: 07. Dez 2005
Beiträge: 369
Wohnort: Port Angeles, Wa. USA
|
|
I'm unable to run Kanotix-2006-Easter from HD anymore because it locks up while the panel icons are halfway loaded. No mouse or keyboard response. I have to boot with the 2005-04 CD. I restored with rdiff-backup but the same thing occurs. My .xsession-errors [below] reports BadWindow etc. I wonder if I ran h2's script to upgrade the kernel would help. I haven't done any dist-upgrades. I have ran memtest86+ cleaned out power supply, fan, etc. My system is fairly new so I'm pretty certain hardware or temperature is not the issue.
konqueror-crash-6FeY file reports opening & closing etc but I don't understand what it all means. I've pasted a portion of it below as well. If anyone can help I will be very grateful because I'm tired of running from CD & want my system back if possible.
Xsession: X session started for joyboy at Tue Aug 8 07:49:46 PDT 2006
startkde: Starting up...
kbuildsycoca running...
DOUBLE-CLICK: 250 --> -1 THRESHOLD: 8 --> -1 X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e00046
DOUBLE-CLICK: 250 --> -1 THRESHOLD: 8 --> -1 X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e0003d
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e00046
DOUBLE-CLICK: 250 --> -1 THRESHOLD: 8 --> -1 X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e0003d
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e14598
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e13899
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e15545
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e00046
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e00046
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x1e022a8
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x1e022a8
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x1e022a8
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x1e022a8
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e08ed1
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x1e08ed1
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e00046
DOUBLE-CLICK: 250 --> -1 THRESHOLD: 8 --> -1 X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e0003d
DOUBLE-CLICK: 250 --> -1 THRESHOLD: 8 --> -1 X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e0003d
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x2200011
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x2200011
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e00046
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e00007
QObject::disconnect: Unexpected null parameter
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e00046
QObject::connect: No such signal KListView::doubleclicked(QListViewItem*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'KateSaveModifiedDialog')
QObject::disconnect: Unexpected null parameter
invalid length 24902
Failed to process 45 bytes from server
invalid length 24902
invalid length 24902
invalid length 24902
DOUBLE-CLICK: 250 --> -1 THRESHOLD: 8 --> -1 X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x2200046
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x1e0003d
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x2400046
DOUBLE-CLICK: 250 --> -1 THRESHOLD: 8 --> -1 X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x2600046
konqueror-crash-6FeY [partial]
opened(7a6b3767):error:/?error=11&errText=/media/hda1/home/joyboy/.kde/tmp-WorldsEnd#file:///media/hda1/home/joyboy/.kde/tmp-WorldsEnd
closed(706a659c):
opened(706a659c):error:/?error=11&errText=/media/hda1/home/joyboy/.kde/tmp-WorldsEnd#file:///media/hda1/home/joyboy/.kde/tmp-WorldsEnd
closed(7a6b3767):
opened(7a6b3767):media:/hda1/home/joyboy/.kde
closed(7a6b3767):
opened(7a6b3767):media:/hda1/home/joyboy/.kde/Autostart
closed(706a659c):media:/hda1/home/joyboy/.kde
opened(706a659c):media:/hda1/home/joyboy/.kde/Autostart
closed(7a6b3767): |
_________________
illegitimati non carborundum
|
| |
|
|
|
 |
|
|
|
Titel: RE: lockup at startup
Verfasst am: 30.09.2006, 20:39 Uhr
|
|
Anmeldung: 05. Dez 2005
Beiträge: 414
Wohnort: Auckland, New Zealand
|
|
Are you able to restore with rdiff-backup to an earlier version than the last backed up one?
Is your hard drive full?
What were the last things you did before it wouldn't boot for you?
When you boot to init 3 (by putting a 3 at grub) can you log in as root and user ok and is everything mounted and can you read and write ok? |
_________________
Linux is evolution, not intelligent design - Linus Torvalds
|
| |
|
|
|
|
|
|
|
Titel: RE: lockup at startup
Verfasst am: 30.09.2006, 21:02 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
One day we will learn the actual cause of the consistent failures 2radical has suffered, and I seriously doubt they will turn out to be what anyone thought they would be.
I lean towards some type of hardware issue. These failures have simply been too consistent over time. Or some fairly obscure type of formatting corruption on the drive, it's hard to say, but it's almost for certain something that is not kanotix related. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 30.09.2006, 21:30 Uhr
|
|
Anmeldung: 07. Dez 2005
Beiträge: 369
Wohnort: Port Angeles, Wa. USA
|
|
The last thing I did before this happened was to try & get googlearth to run & display properly. I haven't tried to rdiff-backup restore from an earlier backup than the last one, but I will check that out. I also haven't tried typing 3 at grub but I will try what you suggest. My HD is not full.
h2: I too, don't think that it's something Kanotix related, but I haven't had this problem with other OS's. I admit I'm not very knowledgeable about hardware issues, or even most other issues, but I'm doing my best with the limited deck I have.  I don't know how to diagnose hardware. Maybe with some diagnostic CD? I cringe when I think of taking it to somebody to fix, because nobody that I know of around here knows anything about linux, & the cost of doing so is something I'm trying to avoid at this point. |
_________________
illegitimati non carborundum
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 30.09.2006, 21:39 Uhr
|
|
Anmeldung: 07. Dez 2005
Beiträge: 369
Wohnort: Port Angeles, Wa. USA
|
|
| If it were hardware wouldn't the Kanotix CD not work as well? I mean, minus the hard drive as it's running on memory? |
_________________
illegitimati non carborundum
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 30.09.2006, 21:42 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
There is almost certainly some problem at some point of the procedures. It could be anywhere, from using cheap cd blanks, burning too fast, which I doubt you're doing now, a defective cd burner, or a cheap cd burner. That would be in the iso part of the question. That could be worked around by downloading the iso to another partition, then installing kanotix using the fromiso cheat codes.
Or it could be defective or buggy formatting of partition, or a subtle error on the hard drive itself. Failing hard disks can in fact fail in only one partition, I've had that happen to me.
Those would be the most likely candidates. You'd be amazed at just how bad a cd burner can get as it fades away. The disks sort of work, but not quite, weak burns, hard to read. And cheap, no name burners are the very worst, I've bought new ones that created toaster after toaster, while name brand units priced the same burned perfectly.
But I think it's almost certainly a hardware related issue. I simply have not encountered any problems like this on any install, no matter what type of hardware the box ran.
While testing ram is always nice, it's very rare to find that it's the problem.
Other more obscure, but entirely likely scenarios are that you have a problematic power supply in the box, that your incoming power is not particularly clean, that you are not using a battery backup between wall power and box, which can lead to the system getting fried in subtle ways, and so on.
It's one of these, but since this only happens with kanotix, the places I'd look most closely would be the places where kanotix is most demanding, which is in this case the cd burning process. Bad cables to burner, poor connections, that kind of work, and so on. Lots of places it could happen.
Since I've seen every one of the above scenarios personally, I don't consider any of them all that unlikely. The failing sectors on the install partition is an especially interesting one, since you can run the hard disk utiliity, tell it to correct bad sectors, then install, not realizing that the disk is simply failing. This is easy to see by simply running the disk test utility, installing os, running it a bit, then rerunning the test utility. If fresh errors appear in that short time period, the disk is failing.
Bad cables also lead to funny, and widely unpredictable results. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 30.09.2006, 22:44 Uhr
|
|
Anmeldung: 05. Dez 2005
Beiträge: 414
Wohnort: Auckland, New Zealand
|
|
|
2radical hat folgendes geschrieben::
The last thing I did before this happened was to try & get googlearth to run & display properly.
When you are in init 3 (pressing 3 in grub) and logging into the terminal as root, it might be an idea to re-install your graphics drivers.
Failing that, assuming it's not a hardware fault, and that the problem is only with X, you might try starting up a different X windows like gnome or icewn or what ever and see if you have any problems. If you don't then that suggests the problem is with KDE (if you use that). In that case you could look at some radical options like removing KDE and KDM and installing them again, or using h2's script to dist-upgrade may just sort things out for you.
BTW, did you change xorg.conf when you were trying to get google earth working? |
_________________
Linux is evolution, not intelligent design - Linus Torvalds
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 30.09.2006, 23:00 Uhr
|
|
Anmeldung: 05. Dez 2005
Beiträge: 414
Wohnort: Auckland, New Zealand
|
|
Another thing 2radical, you said you hadn't done any dist-upgrade, and I bet that's because you were sick of your system breaking ... and here it goes breaking on you 
So I can see that if you are careful and if it still breaks then it could well be an inconsistend hardware problem. But just in case it's not, before changing anything (including anything to do with upgrading or installing graphics drivers or playing with graphics drivers to get google earth going), it's usually a good idea to rdiff-backup first, and then make the changes/installs, and then reboot to make sure everything is still ok, and then only when you are happy then rdiff-backup again. When restoring using rdiff-backup, you should be able to flick back to where you were in a matter of 15 minutes or so. After booting the live cd, it seems to help if you re-formate the partition you are restoring too, and then doing the backup (but careful you don't format the wrong partition).
That reminds me, if it is a failing disk, well, when you boot up with the live cd, what does the file system check show you (eg if you've installed to hda1), as root do:
fsck /dev/hda1
(or /dev/sda1 if you've installed it there ... but make sure that the partition that you're checking is unmounted ... some people even boot the live cd with the "noswap" boot code so that the live cd wont mount swap on the disk they are checking) ... any errors? |
_________________
Linux is evolution, not intelligent design - Linus Torvalds
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 30.09.2006, 23:17 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
| If I had to guess just one thing, I'd guess corrupted or slowly degrading/failing hard disk partition. That would account for the 'it works, then it doesn't work' which consistently happens. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 01.10.2006, 01:34 Uhr
|
|
Anmeldung: 07. Dez 2005
Beiträge: 369
Wohnort: Port Angeles, Wa. USA
|
|
Sorry for the scatter-brained nature of this respose, but to answer your questions & supply a little more info, I haven't installed any graphics drivers. I have a A7V400-MX MB with integrated VIA UniChrome Graphics which is the reason googleearth wouldn't work for me. I didn't change xorg.conf.
I've run rdiff-backup a few times but when I look for earlier sessions than my last backup I can't find them. That is, /hda5/backups has a locked rdiff-backup-data folder which I looked at as root in console which contains:
root@0[rdiff-backup-data]# ls
backup.log
chars_to_quote
current_mirror.2006-08-08T21:32:25-07:00.data
error_log.2006-07-25T18:01:05-04:00.data
error_log.2006-07-31T14:12:54-07:00.data.gz
error_log.2006-07-31T15:30:17-07:00.data
error_log.2006-08-01T17:00:45-07:00.data.gz
error_log.2006-08-08T17:31:46-07:00.data.gz
error_log.2006-08-08T21:32:25-07:00.data.gz
file_statistics.2006-07-25T18:01:05-04:00.data.gz
file_statistics.2006-07-31T14:12:54-07:00.data.gz
file_statistics.2006-07-31T15:30:17-07:00.data.gz
file_statistics.2006-08-01T17:00:45-07:00.data.gz
file_statistics.2006-08-08T17:31:46-07:00.data.gz
file_statistics.2006-08-08T21:32:25-07:00.data.gz
increments
increments.2006-07-25T15:01:05-07:00.dir
increments.2006-07-31T14:12:54-07:00.dir
increments.2006-07-31T15:30:17-07:00.dir
increments.2006-08-01T17:00:45-07:00.dir
increments.2006-08-08T17:31:46-07:00.dir
mirror_metadata.2006-07-25T15:01:05-07:00.diff.gz
mirror_metadata.2006-07-31T14:12:54-07:00.diff.gz
mirror_metadata.2006-07-31T15:30:17-07:00.diff.gz
mirror_metadata.2006-08-01T17:00:45-07:00.diff.gz
mirror_metadata.2006-08-08T17:31:46-07:00.diff.gz
mirror_metadata.2006-08-08T21:32:25-07:00.snapshot.gz
restore.log
session_statistics.2006-07-25T18:01:05-04:00.data
session_statistics.2006-07-31T14:12:54-07:00.data
session_statistics.2006-07-31T15:30:17-07:00.data
session_statistics.2006-08-01T17:00:45-07:00.data
session_statistics.2006-08-08T17:31:46-07:00.data
session_statistics.2006-08-08T21:32:25-07:00.data
I don't know what to do with this information. Last time I tried to restore I ran the command: rdiff-backup -r now --force /media/hda5/backups /media/hda1
I didn't re-format the partition before doing so, as I thought the --force option would overwrite what was on /hda1. At the time of my last backup I wasn't having any lockup problems, so I figured that it was clean & would fix things, but not so. Should I have re-formatted hda1 with cfdisk first? I have a gparted livecd 0.2.5-3. I wonder if that would be useful.
If all else fails, I could just start all over again with a re-format & install 2006-01-RC3. I think I DID burn 2006-Easter-RC4 too fast last time. My cd drives & cables are less than a year old, & the HD I got in '04. Would I be able to D/L the ISO to /dev/hda1? I have 6.9GB free there, & 18.5GB free on /dev/hda2 where /home is.
I ran fsck /dev/hda1 which reported at the end:
finished
No corruptions found
There are on the filesystem:
Leaves 31965
Internal nodes 224
Directories 15455
Other files 135913
Data block pointers 583119 (6 of them are zero)
Safe links 3 |
_________________
illegitimati non carborundum
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 01.10.2006, 02:24 Uhr
|
|
Anmeldung: 05. Dez 2005
Beiträge: 414
Wohnort: Auckland, New Zealand
|
|
The file:
current_mirror.2006-08-08T21:32:25-07:00.data
shows that the last backup was done on the 8th of Aug at about half past nine at night.
The previous ones are shown but the files starting with the name "increments". So the one before that was done on the same day, but at about half past 5 pm.
Better way to list your backups is to do:
rdiff-backups -l path/to/backups
... eg, it might be this in your case:
rdiff-backups -l /media/hda5/backups
The "--force" option is supposed to overwrite everything, and delete anything else left over in the partition. But I've found that sometimes it doesn't work, and re-formatting the partition is a cleaner way of doing it.
So I'd do (if I had your setup):
(live cd):
sudo su -
If you use ext3 then re-format the old partition like this without mounting hda1:
mke2fs -j /dev/hda1
or for reiserfs, do:
mkreiserfs /dev/hda1
Now mount the partitions:
mount /media/hda1 #ie mount root partition
mount /media/hda5 #ie mount backups partition
And to do the backup from the last backup:
rdiff-backup -r now /media/hda5/backups /media/hda1
or, to get the previous one, you could do:
rdiff-backup -r 2006-08-08T17:31:46-07:00 /media/hda5/backups /media/hda1
But I'm thinking that your last (current) backup was done quite a while ago, well before any of your problems, so I don't think restoring will help.
Note: The restore command you have isn't restoring your home which is on hda2, and I'm assuming that you're excluding that when do you backups (which you should do, as each partition should be done separately). Maybe it's something in your /home that's tripping up X windows?? (I dunno) If you have been backing up your home (ie hda2) regularly, then it may be a good idea to restore that (although if it's not a recent backup then you'll lose some of your recent data, so, you might want to do some "cp -a" commands to make sure you don't lose some of your data).
Note2: I see that you're backing up your data to the same disk, and that's risky, as if the disk dies, then you may lose everything.
So anyway, since your backup was done a while ago, I'm inclined to think now that it must be some xorg/KDE/KDM issue (that is, if it isn't a hardware problem, which it sounds as if that's quite likely due to the inconsistent behaviour that you have been explaining). So if it isn't a hardware issue, then you might try and reinstall KDM/KDE/xorg.
BTW, you /home is mounted ok in /etc/fstab right?
So I can only think of trying to reinstall KDM/KDE/xorg, and failing that, do an upgrade install off the live cd. |
_________________
Linux is evolution, not intelligent design - Linus Torvalds
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 01.10.2006, 03:27 Uhr
|
|
Anmeldung: 07. Dez 2005
Beiträge: 369
Wohnort: Port Angeles, Wa. USA
|
|
Yes, fstab is mounted ok in fstab & yes I did exclude /home in hda2 because /home was in hda1 as well, even though I specified during installation that it be in hda2. Thank you very much for your helpful suggestions. I will try them out. I have to tear myself away from this now to go to relative's, but will be back at it tomorrow. Thanks alot, kurt
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs devmode=0666 0 0
/dev/hda1 / reiserfs defaults 0 1
/dev/hda2 /home reiserfs defaults 0 2
/dev/hda3 none swap sw 0 0
/dev/hda5 /media/hda5 reiserfs defaults 0 0
# /dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 |
_________________
illegitimati non carborundum
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 01.10.2006, 07:04 Uhr
|
|
Anmeldung: 26. Jun 2005
Beiträge: 389
|
|
| I'm with h2 on this. I'd try reinstalling or moving the system to a new partition. Or use an old disk I have lying around somewhere. Just note that if it is a disk/partition problem, then your backups might be problematic. Far too many errors, especially when you have not been upgrading, for it to be a software issue, methinks. |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 02.10.2006, 01:26 Uhr
|
|
Anmeldung: 07. Dez 2005
Beiträge: 369
Wohnort: Port Angeles, Wa. USA
|
|
I figured out what was wrong with my installation. I have a bad Easter CD. Apparently as h2 suggested, I must have burnt it too fast, although I do remember checking it at the time of burning it & it matched the ISO. Perhaps my ISO download was bad. It seems I have to learn everything the hard way. Anyway, I didn't want to install 2005-04 & then try to dist-upgrade, so I installed PCLinuxOS -p92 from liveCD just to get a system up & running. I think I'll wait until 2006-01 becomes a stable release then download it to install. I hope that doesn't take too long. I could have installed Knoppix 4.2, but thought I'd try this out just during the meantime to test. Kanotix truly is the best distribution I've used, & I look forward to get back to it.
I used the gparted livecd 0.2.5-3 to partition & format, this time with ext3 instead of reiserfs. I enlarged hda5 a couple more gigs which I will use for backups as I did before. Prior to doing the pclinux install (which btw took much longer than Kanotix) I tried restoring with an earlier backup than my last one, but I got a host of error messages reporting amongst other things that I had run out of room. I use hda5 for backups because I've read that cd's aren't trustworthy, & I don't have another medium to do them to. This is the least expensive alternative, although I realize that it has it's risks too.
Thank you both Swynndla & h2 for your assistance & expertise. Later, kurt |
_________________
illegitimati non carborundum
|
| |
|
|
|
|
|
|
|
|
|
|
