Author Topic: [RESOLVED] Help-kernel panic! I didn't do it!!!! (Read 2179 times)

Old-Polack · « **Reply #15 on:** July 23, 2010, 07:39:45 PM »

Quote from: ziggy on July 23, 2010, 06:05:20 PM

Thanks for the response old-polack. Nothing exotic on the USB stick. It's become somewhat of a permanent attachment on this computer. Mostly miscellaneous stuff like password manager and some date etc. It's never given me any problem before. Anyway, I removed it, rebooted, and got the same results. I normally have several external firewire drives connected also, but these are not attached now. I don't speak Linux very well and any problems I have are almost always self-inflicted, but this one is strange. This is why I proclaimed innocence in my posting title. Perhaps my next step is to run fsck as joble suggested?
ziggy

I would, were it my machine. The fact that the partition mounts from the liveCD makes me thing this is not the primary cause of the problem, but it's possible that a single unreadable file could prevent proper booting, so it's worth the effort, even if it only rules out filesystem corruption as the cause. It takes us one step closer the a proper repair.

ziggy · « **Reply #16 on:** July 23, 2010, 07:42:33 PM »

OK, I'm going to try it now and see what happens. Will report back later.
ziggy

ziggy · « **Reply #17 on:** July 23, 2010, 07:57:22 PM »

Below is my output from fsck -f /dev/sdb8. For some reason it can read my volume label (PCLOS2010_root) whereas PCCC is not able to. Doesn't look as if there's anything significant in the output. I'm goint to try to reboot again.

[root@localhost root]# fsck -f /dev/sdb8
fsck from util-linux-ng 2.16.2
e2fsck 1.41.9 (22-Aug-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
PCLOS2010_root: 122152/655776 files (0.1% non-contiguous), 867554/2622603 blocks
[root@localhost root]#

ziggy · « **Reply #18 on:** July 23, 2010, 08:23:34 PM »

No joy! Just tried rebooting again after running fsck. I think I'll give this up for this evening and get back at it again tomorrow. Thanks all for the help.
ziggy

Old-Polack · « **Reply #19 on:** July 23, 2010, 09:01:41 PM »

Quote from: ziggy on July 23, 2010, 08:23:34 PM

No joy! Just tried rebooting again after running fsck. I think I'll give this up for this evening and get back at it again tomorrow. Thanks all for the help.
ziggy

When you do get back to it, from the liveCD, PCC --> Hardware --> Browse and configure hardware, check which driver is used for the controller the /dev/sdb hard drive is on, and report that here.

ziggy · « **Reply #20 on:** July 23, 2010, 10:01:08 PM »

Quote

When you do get back to it, from the liveCD, PCC --> Hardware --> Browse and configure hardware, check which driver is used for the controller the /dev/sdb hard drive is on, and report that here.

O-P,
I'm not quite sure what you are asking. I don't see any driver listed. I'll post the data from PCC on sdb. Not sure this will be helpful for you. Will be back tomorrow. Thanks - ziggy

Identification
Vendor: ‎Western Digital Corp.

Description: ‎WD1200BB-53C

Disk identifier: ‎Western Digital Corp. WD1200BB-53C

Media class: ‎hd

Bus identification
Target id number: ‎1

Connection
Bus: ‎SCSI

Channel: ‎0

Logical unit number: ‎0

Target id number: ‎1

Device
Old device file: ‎/dev/sdb

Partitions
Primary partitions: ‎2 (sdb1, sdb3)

Extended partitions: ‎6 (sdb5, sdb6, sdb7, sdb8, sdb9, sdb10)

Misc
Disk controller: ‎1

Geometry: ‎14593/255/63 (CHS)

Module: ‎ata_piix

Old-Polack · « **Reply #21 on:** July 23, 2010, 10:32:06 PM »

Quote from: ziggy on July 23, 2010, 10:01:08 PM

Quote
When you do get back to it, from the liveCD, PCC --> Hardware --> Browse and configure hardware, check which driver is used for the controller the /dev/sdb hard drive is on, and report that here.

O-P,
I'm not quite sure what you are asking. I don't see any driver listed. I'll post the data from PCC on sdb. Not sure this will be helpful for you. Will be back tomorrow. Thanks - ziggy

Identification
Vendor: ‎Western Digital Corp.

Description: ‎WD1200BB-53C

Disk identifier: ‎Western Digital Corp. WD1200BB-53C

Media class: ‎hd

Bus identification
Target id number: ‎1

Connection
Bus: ‎SCSI

Channel: ‎0

Logical unit number: ‎0

Target id number: ‎1

Device
Old device file: ‎/dev/sdb

Partitions
Primary partitions: ‎2 (sdb1, sdb3)

Extended partitions: ‎6 (sdb5, sdb6, sdb7, sdb8, sdb9, sdb10)

Misc
Disk controller: ‎1

Geometry: ‎14593/255/63 (CHS)

Module: ‎ata_piix

The module highlighted in maroon is what I was looking for.

ziggy · « **Reply #22 on:** July 24, 2010, 09:27:25 AM »

Quote

The module highlighted in maroon is what I was looking for.

O-P, I'm glad you got what you were looking for. You must have stayed up late last night. I'm not sure what to try next, so if you're around today I'll check in occasionally to see if you have any more suggestions. -- ziggy

Mike · « **Reply #23 on:** July 24, 2010, 01:32:45 PM »

Since you didn't get a error pertaining to the module, I suspect he was checking to make sure it is there.

He works like a very precise detective, complete and in proper order.

ziggy · « **Reply #24 on:** July 24, 2010, 01:43:07 PM »

Quote

Since you didn't get a error pertaining to the module, I suspect he was checking to make sure it is there.
He works like a very precise detective, complete and in proper order.

Yea, I've read many of his posts before. I believe O-P enjoys tracking down problems like this and helping dummies like me! ziggy

Joble · « **Reply #25 on:** July 29, 2010, 07:45:21 AM »

So...... I the kernel still in a panic?

ziggy · « **Reply #26 on:** July 29, 2010, 03:39:06 PM »

joble,
Well no, just me! I finally decided it would be faster for me to reinstall, which I did. Then after doing the synaptic updates, I got a message "Error: Can't have overlapping partitions." I posted about that problem here. http://www.pclinuxos.com/forum/index.php/topic,76837.0.html. Problem was that I had a primary partition inside an extended partition. Since it has been this way for a long time and didn't seem to cause me any problem, I decided to let it go. Then I read some posts by OP on this topic and he made it seem simple to use his favorite utility, fdisk, to correct this situation. So I rebuilt my partition table using the exact same start/end points for each partition as reported by fdisk and changed the primary partition inside the extended partition to an extended partition. But now I have a different problem which, if you're interested in, I've posted here. http://www.pclinuxos.com/forum/index.php/topic,76920.0.html. Basically, I can't boot into my Linux install anymore. I just get booted to a grub prompt.

Thanks for your interest, and at least I'm learning a lot in the process. Would like to get off this live CD though and get back to HD booting.

ziggy

eor2004 · « **Reply #27 on:** July 29, 2010, 09:27:00 PM »

This problem had happened to me three times I tried to install pclinux 2010 Gnome but never has happened to me installing pclinux 2010 KDE, from my experiences with pclinux I would say that the installation process is much better with the KDE version than with Gnome, don't know why???

Joble · « **Reply #28 on:** August 04, 2010, 01:02:48 PM »

It's about time you came back and picked up this topic O-P!

Old-Polack · « **Reply #29 on:** August 04, 2010, 01:05:12 PM »

Quote from: Joble on August 04, 2010, 01:02:48 PM

It's about time you came back and picked up this topic O-P!

OK! I need to see the contents of fdisk -l and /boot/grub/menu.lst from the installed / partition.

PCLinuxOS-Forums

News: