reinstalled using *normal* partitioning, ignoring the sparc way. still has the same result, system will boot and run, just mounts root as -ro. we are not amused. dmesg sez nothing at all about mounting -ro, or i would have caught it sooner ( at least i tell myself that). kern.log reveals that root is mounted -ro but does not state a reason or even mention errors. this makes absolutely no sense. the /var partition is now @ sda3 and it mounts -rw. why does it insist on / being -ro?
g ----- Original Message ----- From: "Ben Collins" <[EMAIL PROTECTED]> To: "Greg Teigue" <[EMAIL PROTECTED]> Cc: "Sabino Maggi" <[EMAIL PROTECTED]> Sent: Wednesday, July 04, 2001 9:26 PM Subject: Re: (newbee alert) cant save changes to edited scripts. > On Wed, Jul 04, 2001 at 09:18:17PM -0400, Greg Teigue wrote: > > dropped the list from this since it seems that you fine folks are the only > > ones interested in playing "let's help the newfish". i do appreciate all of > > the time you have spent in trying to help me through this! > > Usually you keep the list in the CC so it gets archived for others that > may have the same problems. > > Is your SCSI chain terminated? Somewhere, there has to be an exact error > in the kernel logs about why the fs was remounted read-only. You need to > send me that. You can get it from the dmesg command, or the > /var/log/kern.log file (dmesg is easier). > > Ben > > -- > -----------=======-=-======-=========-----------=====------------=-=----- - > / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ > ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' > `---=========------=======-------------=-=-----=-===-======-------=--=---' >
