![](https://seccdn.libravatar.org/avatar/961cb91afb232ccfdad4fd8cabe8dd87.jpg?s=120&d=mm&r=g)
On Sunday 24 Oct 2004 07:10, Jerome Lyles wrote:
On Wednesday 13 October 2004 09:46 pm, Jerome Lyles wrote:
On Wednesday 13 October 2004 05:38 pm, Patrick Shanahan wrote:
* Patrick Shanahan
[10-13-04 19:46]: boot until the system stops, I believe declaring that root is mounted readonly.
from the command-line as root: remount /dev/hdb2
found another remount command: mount -n -w -o remount /dev/sda2 /
init 5
I wiped the / partition clean. Reloaded Suse 9.1 from the DVD and updated online and rebooted. No problem. Then I used a suse mirror and the Yast system upgrade module to upgrade to KDE 3.3.1 and rebooted. Problems. Fsck fails (again) and prompts for command line root password just like before I wiped and reloaded everything. So I run fsck.reiserfs --fix-fixable on my / filesystem mounted read only, no corruptions found, just like before. So I login and run mount. I've got two instances of the / filesystem again! So I did 'init 5' logged in as my usual user and ran startx, this time startx crashes.
I've updated KDE before and this never happened. The only difference this time is that when update was done and I was asked to insert the dvd I did. Usually I select skip. This time I didn't assuming that doing what the program asked wouldn't hurt, was I wrong??
Does anyone have a clue why mount shows / mounted twice? Could loading software off the dvd do this? Incompatibilities? I would like to solve this without having to start all over again, who knows how many times. I lost some data but I really thought I had put this problem behind me (This time I'm backed up to the hilt). I thought I was last time too but I used the damaged system to make the backup and after I wiped the damaged drive and tried to use the backup the backup was blank.
Amazed to be here again, Jerome
I would suggest you have a good long hard look at your Hard drive .. I have just had similar problems here with an SCSI drive i use to store all my music on " RIAA can FOAD" it aint on line for the whingers out there ? any how i started to get problems with it recently once again last night ni have now backed it up and completely deleted the entire drive removed all partitions re partitioned it to /dev/sdb1 ran mkereiserfs with full checking and it appeares so far to be OK .. MAybe you should try similar .. pete -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan, The time is here to FORGET that M$ Corp ever existed the world does not NEED M$ Corp the world has NO USE for M$ Corp it is time to END M$ Corp , Play time is over folks time for action approaches at an alarming pace the death knell for M$ Copr has been sounded . Termination time is around the corner ..