On 03 Feb 2004, Andreas Janssen wrote:
> Hello
>
> Hanspeter Kunz (<[EMAIL PROTECTED]>) wrote:
> > On Tue, 2004-02-03 at 16:37, Anthony Campbell wrote:
> >>
> >> I've noticed a worrying message at boot. It comes just after
> >> "Cleaning /tmp /var/run /var/lock"
> >>
> >> and reads:
> >> "mount: w
Hello
Hanspeter Kunz (<[EMAIL PROTECTED]>) wrote:
> On Tue, 2004-02-03 at 16:37, Anthony Campbell wrote:
>>
>> I've noticed a worrying message at boot. It comes just after
>> "Cleaning /tmp /var/run /var/lock"
>>
>> and reads:
>> "mount: wrong fstype, bad option, bad superblock on tmpfs, or
>> to
Hello
Anthony Campbell (<[EMAIL PROTECTED]>) wrote:
> On 03 Feb 2004, Adam Aube wrote:
>> On Tuesday 03 February 2004 10:37 am, Anthony Campbell wrote:
>>> I've noticed a worrying message at boot. It comes just after
>>> "Cleaning /tmp /var/run /var/lock"
>>
>>> and reads:
>>> "mount: wrong fsty
is any of the filesystems (not marked as 'noauto') missing after
booting?
On Tue, 2004-02-03 at 17:04, Anthony Campbell wrote:
> On 03 Feb 2004, Adam Aube wrote:
> > On Tuesday 03 February 2004 10:37 am, Anthony Campbell wrote:
> > > I've noticed a worrying message at boot. It comes just after
> >
On Tuesday 03 February 2004 11:04 am, Anthony Campbell wrote:
> On 03 Feb 2004, Adam Aube wrote:
> > Can you post the contents of /etc/fstab?
[/etc/fstab snipped]
I have only two suggestions, and likely neither one will make a
difference, but they might be worth checking out anyway.
- On the /g
Hello
Anthony Campbell (<[EMAIL PROTECTED]>) wrote:
> I've noticed a worrying message at boot. It comes just after
> "Cleaning /tmp /var/run /var/lock"
>
> and reads:
> "mount: wrong fstype, bad option, bad superblock on tmpfs, or
> too many mounted filesystems"
>
> In spite of this, everything
check /etc/fstab, I guess one of the entries is the problem.
cheers,
Hp.
On Tue, 2004-02-03 at 16:37, Anthony Campbell wrote:
> I've noticed a worrying message at boot. It comes just after
> "Cleaning /tmp /var/run /var/lock"
>
> and reads:
> "mount: wrong fstype, bad option, bad su
On 03 Feb 2004, Adam Aube wrote:
> On Tuesday 03 February 2004 10:37 am, Anthony Campbell wrote:
> > I've noticed a worrying message at boot. It comes just after
> > "Cleaning /tmp /var/run /var/lock"
>
> > and reads:
> > "mount: wrong fstype, bad option, bad superblock on tmpfs, or
> >
check /etc/fstab, I guess one of the entries is the problem.
cheers,
Hp.
On Tue, 2004-02-03 at 16:37, Anthony Campbell wrote:
> I've noticed a worrying message at boot. It comes just after
> "Cleaning /tmp /var/run /var/lock"
>
> and reads:
> "mount: wrong fstype, bad option, bad su
On Tuesday 03 February 2004 10:37 am, Anthony Campbell wrote:
> I've noticed a worrying message at boot. It comes just after
> "Cleaning /tmp /var/run /var/lock"
> and reads:
> "mount: wrong fstype, bad option, bad superblock on tmpfs, or
> too many mounted filesystems"
> In spi
I've noticed a worrying message at boot. It comes just after
"Cleaning /tmp /var/run /var/lock"
and reads:
"mount: wrong fstype, bad option, bad superblock on tmpfs, or
too many mounted filesystems"
In spite of this, everything seems to work as it should and
/var/log/boot
11 matches
Mail list logo
