Re: system_crash.
CHRIS WAKEFIELD wrote: Greetings all. Had my machine (amdx2) up and running for about 70 days (2.6.16-16), came home today to a frozen kde. Rebooted and grub would _NO_ partitions! ...15 or twenty different kernels between 2 drives. Checked, and they're all there just fine, so I'm reinstalling I rememeber a few months ago trying to boot with a freshly compiled kernel and having the boot freeze umptine times at the scheduler initialization (?) tried many different kernel configs, gave up and stuck with the only kernel that'll boot my new machine - 2.6.16-16. Seems the latest 'debian-testing-amd64-netinst' doesn't use this kernel. My original image from an install of a year ago stops installing at 'tzdata' (tried 6 times now). So I'm stuck between a rock and windows here. Any ideas would be greatly appreciated. Chris W. What file system were you using? ext3? -- !!! INCLUDE ALL TEXT IN TECHNICAL SUPPORT EMAIL REPLIES!!! !!!Send in plain-text mode - mail with attached GIFs will be rejected !!! Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Misdirection is the key to being a good magician. Magicians tell you they are doing something while they do something quite different; much like politicians -- except we can afford magicians. -KPS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: system_crash.
I was using reiserfs (from about ver.3.5 - 4 years or so), but I've switched to ext3 until reiser4 is mature. On Tuesday 23 January 2007 17:01, Karl Schmidt wrote: CHRIS WAKEFIELD wrote: Greetings all. Had my machine (amdx2) up and running for about 70 days (2.6.16-16), came home today to a frozen kde. Rebooted and grub would _NO_ partitions! ...15 or twenty different kernels between 2 drives. Checked, and they're all there just fine, so I'm reinstalling I rememeber a few months ago trying to boot with a freshly compiled kernel and having the boot freeze umptine times at the scheduler initialization (?) tried many different kernel configs, gave up and stuck with the only kernel that'll boot my new machine - 2.6.16-16. Seems the latest 'debian-testing-amd64-netinst' doesn't use this kernel. My original image from an install of a year ago stops installing at 'tzdata' (tried 6 times now). So I'm stuck between a rock and windows here. Any ideas would be greatly appreciated. Chris W. What file system were you using? ext3? -- !!! INCLUDE ALL TEXT IN TECHNICAL SUPPORT EMAIL REPLIES!!! !!!Send in plain-text mode - mail with attached GIFs will be rejected !!! Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Misdirection is the key to being a good magician. Magicians tell you they are doing something while they do something quite different; much like politicians -- except we can afford magicians. -KPS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: system_crash.
On Thu, Jan 18, 2007 at 11:56:23PM -0800, CHRIS WAKEFIELD wrote: I rememeber a few months ago trying to boot with a freshly compiled kernel and having the boot freeze umptine times at the scheduler initialization (?) tried many different kernel configs, gave up and stuck with the only kernel that'll boot my new machine - 2.6.16-16. I had the same problems, it was only till the 2.6.19.x versions that kernels started booting again. Seems the latest 'debian-testing-amd64-netinst' doesn't use this kernel. My original image from an install of a year ago stops installing at 'tzdata' (tried 6 times now). A little newer: http://tmp.tryba.nl/debian-testing-amd64-netinst.iso Dates in the iso are Aug. 10 2006. I guess this is the image I used to install my machine. Maybe it works for you. -- When you do things right, people won't be sure you've done anything at all. Daniel Tryba
Re: system_crash.
On Thu, Jan 18, 2007 at 11:56:23PM -0800, CHRIS WAKEFIELD wrote: Greetings all. Had my machine (amdx2) up and running for about 70 days (2.6.16-16), came home today to a frozen kde. Rebooted and grub would _NO_ partitions! ...15 or twenty different kernels between 2 drives. Checked, and they're all there just fine, so I'm reinstalling I rememeber a few months ago trying to boot with a freshly compiled kernel and having the boot freeze umptine times at the scheduler initialization (?) tried many different kernel configs, gave up and stuck with the only kernel that'll boot my new machine - 2.6.16-16. Seems the latest 'debian-testing-amd64-netinst' doesn't use this kernel. My original image from an install of a year ago stops installing at 'tzdata' (tried 6 times now). So I'm stuck between a rock and windows here. Any ideas would be greatly appreciated. Chris W. Hello Chris, I'm sorry to hear of your crash. I don't do kde so I can't help diagnose that. Summary: need more info. Checked, and they're all there just fine Can you access /var and look at syslog to see what happened? To confirm: you say that the current standard kernel (as on my Etch amd64) 2.6.18-3 doesn't boot you machine so you had to compile 2.6.16-16 (or is that an older standard debian kernel). If you compiled it, hopefully you have a backup and can make custom install media per the manual. If standard debian, you can download it and make custom install media per the manual. Either way, first try a daily-image Etch amd64. I wonder if the problem is with grub itself. I guess you first need something that boots, e.g. an install CD or USB-stick (hd-media) in rescue mode. It seems to me that if grub can't find the partition then the problem at this point isn't the kernel. What happens from the grub command line (as opposed to, or from editing, the pre-defined grub menu choices)? The only time I've had hard freezes is when hardware dies. Do you have some dead hardware, say a drive, soundcard, video? What is your drive setup, e.g. raid1, LVM, separate /boot, what is your normal kernel command-line. As always, I hope you have backups and I hope this isn't putting you out of busness while you fix it. Good luck, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
