10.2 KDEinit problem

[andytheman]

Hi Everyone
Hope some one can help with this one on it for days now with out success. I install SuSe 10.2 with no problems at all. It runs for varying periods fine(very fast in fact) then when i attempt to open a program (any it doesn't matter, yast firefox etc) no screen appears and next time i re-boot the pc i get the following message. Could Not Start kdeinit check your installation. So i attempt to check my installation using various methods and always get the same result unknown file system on md3 is corrupt. I try to run the recover but to no avail.

My system detals:
Motherboard: ASRock Pi65G
Processor: P4 3.40GHZ
Memory: 1GB
Disks: 2 x Hitachi SCSI 137gb
SCSI Controller Adaptec 29160n (on SuSe supported list)

Disk partioning /boot partion 3.9gb 1st disk
/diags partion 3.9gb 2nd disk
2 0 raid arrays swap 7.8gb
/ rest of disk 238gb
I dont think the disks have anything to do with the problem or the controller
as I have changed these. Also disabled on board stuff i.e. sound and network etc. Still same problem. Really am struggling now so any help would be gratefully recieved.

[gogalthorp]

Why are you using 7.9 gig swap and on top of that why a raid????

Normal is twice the memory and you really don't need more then 1 gig

type should be Linux swap / Solaris

post result of (as root in a console)
fdisk -l

[andytheman]

Thanks for the reply. Large swap or raid arrays have nothing to do with the problem. Have tried single disk with no raid. Tried recommended lay out that install program suggests. Still with the same results. To answer your question though it's because we've always had a standard setup through the linux versions I used.
Andytheman.

[gogalthorp]

post result of (as root in a console)
fdisk -l

[andytheman]

Sorry can't send you the fdisk -l result because Ive had to format the machine and load SuSe 9.2 on it. This by the way runs fine no problems at all. Is set up in exactly the same manner. Will set up another 10.2 machine asap and let yo know.
Thanks

[andytheman]

Hi All
Back again to the KDE problem. GOGALTHORP asked for the results of fdisk -l
Here they are.

Disk Dev/sda: 1470 GB, 147015821824
255 Heads, 63 Sectors/track 17873 cyclinders
Units = cyclinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/Dev/sda1 * 1 513 4120641 83 Linux
/Dev/sda2 514 1025 4112640 fd Linux Raid autodetect
/Dev/sda3 1026 17873 135331560 fd Linux Raid autodetect

Disk Dev/sdb: 1470 GB, 147015821824
255 Heads, 63 Sectors/track 17873 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/Dev/sdb1 1 513 4120641 83 Linux
/Dev/sdb2 514 1025 4112640 fd Linux Raid autodetect
/Dev/sdb3 1026 17873 135331560 fd Linux Raid autodetect


Disk /Dev/md0: 8422mb, 8422555648 bytes
2 Heads, 4 Sectors/track, 2056288 bytes
units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md0 Doesn't contain a valid partition table

Disk /Dev/md1: 277.1 GB, 277158821888 bytes
2 Heads, 4 Sectors/track, 67665728 bytes
units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md1 Doesn't contain a valid partition table

There is an obvious discrepancy between what they actually are and what the system thinks they are but why? As i said previously the system can run
fine for xx amount of day's suddenly this happens. Really scratching my head.
Thanks in advance.