Can't startx, don't know how to repair

[jtjumper]

Summary:
I tried to reformat a non SUSE partition, and messed up the computer. I can't start window managers.
I need to know how to fix the problem
What is the filesystem type for PC-BSD? or should I venture the route of command line? in which case what commands should I type?
Thanks in advance!

Details and Background:
I was running low on space on my hard drive.
I had another hard drive on my computer with PC-BSD installed.
I get this idea: "I don't care a hoot about PC-BSD, I never use it. I'll reformat that disk and I'll have more space."
So, I run yast. I open up the partition program that gave some disclaimer that only experts should use it.
I think, "Ha, I know what I'm doing."
So I see what looks like two partitions for the same hard disk. Both are 15 GB, the size of my maxtor hard drive. I think, "More Linux weirdness. Just reformat one and the other will follow." I reformatted the one that said FreeBSD. The one that said Maxtor remained the same.
So I open sysyinfo in konqueror, and bam! Two "drives" pointing to the same place! Then a power out happened.
"No problem. Just turn on the system."
I boot normally.
It stops. I never reach the login screen.
"Fine. I'll log in in failsafe mode"
I do so. StartX.
Nothing Happens.
I reinstall PC-BSD on the other drive. This (obviously) doesn't help. (much)
I try to repair with the install disk, but end up logged in as root in command line being asked by OpenSUSE to type those magic words which will repair everything and restore all to happiness. Unfortunately, I don't know what commands to type.
So, I use the install disk to try to update OpenSUSE. I resolve package conflicts
I try again to Repair/Update, and reach a screen where a list of partitions is founds. I click show all partitions. Yast seems to almost promise that if I tell it the filesystem type of the hard drive PC-BSD is installed, it will fix the problem. I have used Linux for less than a year, so I have no clue.
What is the filesystem type for PC-BSD? or should I venture the route of command line? in which case what commands should I type?
Thanks in advance!

[Jonathan183]

Post the output of

fdisk -l

so we can see the disk structure.

[bobescalin2005]

ok...i am confused try to get out that hard drive and let only the suse hard and then try to boot....next time i recomand a bootable cd partitioner for example GParted
If it`s booting try that GParted and format that hard like it should be...

[smoothgecko]

Boot off the install disk and head for installation.
Keep going, accept novell license,
soon you will see a screen with a button and "Other" written on it.
Don't go further!
Click the button and then choose Repair.

[jtjumper]

(repair filesystem) # fdisk -l

Disk /dev/sda: 40.0 GB 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000426a5

Device       Boot  Start    End     Blocks   Id  System 
/dev/sda1              1     96     771088+  82  Linux swap / Solaris
/dev/sda2     *       97   2012    15390270  83  Linux
/dev/sda3           2013   4865   22916722+  83  Linux

Disk /dev/sdb: 15GB, 15000330240 bytes
255 heads, 63 sectors/track, 1823 cylinders
Units cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x90909090
Device    Boot  Start    End    Blocks   Id  System 
/dev/sda1   *       1   1741  13984551   83  Linux
/dev/sda1        1742   1823    658665+   5  Extended
/dev/sda5        1742   1823    658633+  82  Linux swap / Solaris

[jtjumper]

I just fixed the problem ... mostly. (There is still one problem)
I forgot to mention that I had entered the partioner program and set the filesystem to 'reiserfs'. I hadn't reformatted the drive with 'reiserfs' so SUSE got confused and spit errors at me. I should have put the errors here.
I solved this problem by taking a live cd and formatting to reiserfs on the non suse drive. Now I can startx. Hurray!
The bad news is that I have to boot in failsafe.
How do I fix this?

[Jonathan183]

I suggest first you post

fdisk -l

output again since you have changed partitions since the last post. Also post the contents of /etc/fstab and /etc/mtab file ... you can do this by posting the ouput of

cat /etc/fstab
cat /etc/mtab

We should be able to confirm partition structure and mount information match.

Also if you try to boot Linux normally what errors do you get?

[jtjumper]

I suggest first you post

fdisk -l

output again since you have changed partitions since the last post. Also post the contents of /etc/fstab and /etc/mtab file ... you can do this by posting the ouput of

cat /etc/fstab
cat /etc/mtab

We should be able to confirm partition structure and mount information match.

Also if you try to boot Linux normally what errors do you get?

susebox:/home/<username removed># fdisk -l

Disk /dev/sda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000426a5

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1          96      771088+  82  Linux swap / Solaris
/dev/sda2   *          97        2012    15390270   83  Linux
/dev/sda3            2013        4865    22916722+  83  Linux

Disk /dev/sdb: 15.0 GB, 15000330240 bytes
255 heads, 63 sectors/track, 1823 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x90909090

   Device Boot      Start         End      Blocks   Id  System
susebox:/home/<username removed> # cat /etc/fstab
/dev/disk/by-id/scsi-SATA_ST340014A_5JX1J813-part2 /                    ext3       acl,user_xattr        1 1
/dev/disk/by-id/scsi-SATA_ST340014A_5JX1J813-part3 /home                ext3       acl,user_xattr        1 2
/dev/disk/by-id/scsi-SATA_ST340014A_5JX1J813-part1 swap                 swap       defaults              0 0
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
/dev/fd0             /media/floppy        auto       noauto,user,sync      0 0
susebox:/home/<username removed> # cat /etc/mtab
/dev/sda2 / ext3 rw,acl,user_xattr 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
debugfs /sys/kernel/debug debugfs rw 0 0
udev /dev tmpfs rw 0 0
devpts /dev/pts devpts rw,mode=0620,gid=5 0 0
/dev/sda3 /home ext3 rw,acl,user_xattr 0 0
securityfs /sys/kernel/security securityfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0

[Jonathan183]

It looks like you have missed off the entries for sdb in the fdisk -l command output. Fstab and mtab do not appear to list reiserfs partitions.
You could try remaking swap on sda1 using

mkswap /dev/sda1

Make sure you get the right partition!

I'm not sure this will cure the boot problem though, and you should only try this command using the system/boot method you used to create the fdisk output in your last post.

Can you give more information on errors the system throws when you try a normal boot.

[jtjumper]

It looks like you have missed off the entries for sdb in the fdisk -l command output. Fstab and mtab do not appear to list reiserfs partitions.
You could try remaking swap on sda1 using

mkswap /dev/sda1

Make sure you get the right partition!

I'm not sure this will cure the boot problem though, and you should only try this command using the system/boot method you used to create the fdisk output in your last post.

Can you give more information on errors the system throws when you try a normal boot.

There is a reason why the entries are missing. I deleted them once I got X to start. Maybe that was bad.
On a normal boot, I get a black screen.