On Wed, Dec 01, 1999 at 09:33:51AM -0200, Mario Olimpio de Menezes wrote:
> On 1 Dec 1999, Martyn Pearce wrote:
>
> >
> > Mario Olimpio de Menezes writes:
> > | I forgot to say that I already did this: went to single mode (init
> > | 1), then ran: mount -t ext2 -r -o remount,ro /dev/sdaX /mount
Mario Olimpio de Menezes writes:
| Yes, it's interesting.
| The box is at work (here). I think the hardware (fan cooler, power supply,
| etc) is OK. This is a new machine (arrived last friday Nov 26th).
|
| Yes, the machine is permanently networked but I can't say which other
| processes
On 1 Dec 1999, Martyn Pearce wrote:
>
> Mario Olimpio de Menezes writes:
> | I forgot to say that I already did this: went to single mode (init
> | 1), then ran: mount -t ext2 -r -o remount,ro /dev/sdaX /mount-point
> | Then, e2fsck -c /dev/sdaX
> |
> | Well, no badblocks, no problem
Mario Olimpio de Menezes writes:
| I forgot to say that I already did this: went to single mode (init
| 1), then ran: mount -t ext2 -r -o remount,ro /dev/sdaX /mount-point
| Then, e2fsck -c /dev/sdaX
|
| Well, no badblocks, no problem at all in the whole disk.
| Where/what
On 1 Dec 1999, Martyn Pearce wrote:
>
> Mario Olimpio de Menezes writes:
> | Hi,
> |
> | I'm having a strange problem here (ok, maybe it's not a real
> | problem, yet). Every day (at least for the last two), I'm having a SCSI
> | disk error entry in my kern.log, occurring at 6:25 am.
> |
5 matches
Mail list logo