> Lukas Ruf <[EMAIL PROTECTED]> [2004-01-02 12:16]:
>
> Dear all,
>
> when returning back to work after the Xmas-break, my root-file
> system was mounted read-only. However, I have no idea why this
> happened -- and problems fixing it. Any help would be greatly
> appreciated!
>
Thanks for all th
On Fri, 02 Jan 2004 12:26:36 +0100, Jan Minar wrote:
> On Fri, Jan 02, 2004 at 12:16:35PM +0100, Lukas Ruf wrote:
>> Dec 30 07:35:52 [kernel] EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc:
>> unable to read inode block - inode=972554, block=1966176
>> Dec 30 07:35:52 [kernel] Remounting fi
On Fri, 2 Jan 2004 12:16:35 +0100,
Lukas Ruf <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
> Dear all,
>
> when returning back to work after the Xmas-break, my root-file system
> was mounted read-only. However, I have no idea why this happened --
> and problems fixing it. Any help
On Fri, Jan 02, 2004 at 12:16:35PM +0100, Lukas Ruf wrote:
> Dec 30 07:35:52 [kernel] EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc:
> unable to read inode block - inode=972554, block=1966176
> Dec 30 07:35:52 [kernel] Remounting filesystem read-only
This is probably what it should do: rem
Dear all,
when returning back to work after the Xmas-break, my root-file system
was mounted read-only. However, I have no idea why this happened --
and problems fixing it. Any help would be greatly appreciated!
Checking my logs, I found:
Dec 25 02:54:00 [kernel]
Dec 25 02:54:00 [kernel] hda: (
5 matches
Mail list logo