Re: [ubuntu-uk] fsck during boot

[Neil Greenwood]

On 3 Oct 2013 19:44, "Mark Fraser"  wrote:
>
> I realised the other day that I hadn't seen my computer run fsck during
boot
> for quite a while. Running dumpe2fs I get this:
> Mount count:  220
> Maximum mount count:  -1
> Last checked: Wed Mar 20 21:20:51 2013
>
> I understand that I can run
> tune2fs -c 35
> To get it to check every 35 mounts, but do I have to do this when the
> partition is unmounted?
>
> Not even sure why it has been set up this was as I don't remember
changing it.
>

You can run that tune2fs command while the partition is mounted without
problem. It will then take effect on the next boot.

Neil
-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

[ubuntu-uk] fsck during boot

[Mark Fraser]

I realised the other day that I hadn't seen my computer run fsck during boot 
for quite a while. Running dumpe2fs I get this:
Mount count:  220
Maximum mount count:  -1
Last checked: Wed Mar 20 21:20:51 2013

I understand that I can run
tune2fs -c 35
To get it to check every 35 mounts, but do I have to do this when the 
partition is unmounted?

Not even sure why it has been set up this was as I don't remember changing it.

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

[ubuntu-uk] Fsck for bad blocks?

[LeeGroups]

I'm having an issue with my new Viglen mini PC which I've just set up as 
my latest home server.
I've been copying stuff to it over the lan, but it was failing, so I did 
an fsck -c to check for bad blocks.
The output is below...

l...@mserver:~$ fsck -f -c /dev/sda1
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
Checking for bad blocks (read-only test): done603
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda1: * FILE SYSTEM WAS MODIFIED *
/dev/sda1: 11/1311552 files (0.0% non-contiguous), 73973/2622603 blocks
l...@mserver:~$

The question is - were there any bad blocks?
The filesystem was modified and the number 603 looks ominous, but it 
doesn't say any bad blocks were found...

Lee


-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

Re: [ubuntu-uk] fsck

[Tony Arnold]

London School of Puppetry wrote:
> 
> 
> On 29/01/2008, *Tony Arnold* <[EMAIL PROTECTED]
> > wrote:
> 
> 
> 
> Chris Bannister wrote:
> > On 29/01/08 19:53, London School of Puppetry wrote:
> >
> >> Can someone tell me the code for doing a manual fsck check?
> >
> > Unless you need it to do something specific you just need to run
> >
> > fsck /dev/device_name
> >
> > as root or via sudo (replacing /dev/device_name with the real
> device of
> > course)
> 
> fsck will complain if the device is mounted. It will continue if you let
> it but it warns that it may cause severe file system damage. I suggest
> you boot from a live CD and then run fsck from there.
> 
> Regards,
> Tony.
> 
> 
> Oh.I put in fsck and it all came to life and it took several hours.
> Everything fine now.
> How will I know if damage has been done?

Did you get some messages from fsck on the problems it found and fixed?
Was the file system mounted at the time?

You could try running fsck again, ensuring the file system is not
mounted and see if it produces further errors, if it reports it clean.

Regards,
Tony.
-- 
Tony Arnold, IT Security Coordinator, University of Manchester,
IT Services Division, Kilburn Building, Oxford Road, Manchester M13 9PL.
T: +44 (0)161 275 6093, F: +44 (0)870 136 1004, M: +44 (0)773 330 0039
E: [EMAIL PROTECTED], H: http://www.man.ac.uk/Tony.Arnold

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] fsck

[London School of Puppetry]

On 29/01/2008, Tony Arnold <[EMAIL PROTECTED]> wrote:
>
>
>
> Chris Bannister wrote:
> > On 29/01/08 19:53, London School of Puppetry wrote:
> >
> >> Can someone tell me the code for doing a manual fsck check?
> >
> > Unless you need it to do something specific you just need to run
> >
> > fsck /dev/device_name
> >
> > as root or via sudo (replacing /dev/device_name with the real device of
> > course)
>
> fsck will complain if the device is mounted. It will continue if you let
> it but it warns that it may cause severe file system damage. I suggest
> you boot from a live CD and then run fsck from there.
>
> Regards,
> Tony.


Oh.I put in fsck and it all came to life and it took several hours.
Everything fine now.
How will I know if damage has been done?

Caroline

--
> Tony Arnold, IT Security Coordinator, University of Manchester,
> IT Services Division, Kilburn Building, Oxford Road, Manchester M13 9PL.
> T: +44 (0)161 275 6093, F: +44 (0)870 136 1004, M: +44 (0)773 330 0039
> E: [EMAIL PROTECTED], H: http://www.man.ac.uk/Tony.Arnold
>
> --
> ubuntu-uk@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
> https://wiki.kubuntu.org/UKTeam/
>



-- 

---
London School of Puppetry
www.londonschoolofpuppetry.com
-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] fsck

[Tony Arnold]

Chris Bannister wrote:
> On 29/01/08 19:53, London School of Puppetry wrote:
> 
>> Can someone tell me the code for doing a manual fsck check?
> 
> Unless you need it to do something specific you just need to run
> 
> fsck /dev/device_name
> 
> as root or via sudo (replacing /dev/device_name with the real device of
> course)

fsck will complain if the device is mounted. It will continue if you let
it but it warns that it may cause severe file system damage. I suggest
you boot from a live CD and then run fsck from there.

Regards,
Tony.
-- 
Tony Arnold, IT Security Coordinator, University of Manchester,
IT Services Division, Kilburn Building, Oxford Road, Manchester M13 9PL.
T: +44 (0)161 275 6093, F: +44 (0)870 136 1004, M: +44 (0)773 330 0039
E: [EMAIL PROTECTED], H: http://www.man.ac.uk/Tony.Arnold

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] fsck

[Chris Bannister]

On 29/01/08 19:53, London School of Puppetry wrote:

> Can someone tell me the code for doing a manual fsck check?

Unless you need it to do something specific you just need to run

fsck /dev/device_name

as root or via sudo (replacing /dev/device_name with the real device of
course)

-- 
Chris Bannister
email/msn/jabber: [EMAIL PROTECTED]
photos: http://www.flickr.com/photos/moodog
blog: http://blog.suddenmoves.org.uk/

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

[ubuntu-uk] fsck

[London School of Puppetry]

Can someone tell me the code for doing a manual fsck check?

Caroline

-- 

---
London School of Puppetry
www.londonschoolofpuppetry.com
-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems after update

[Rob Beard]

Michael Holloway wrote:

> 
> Hi
> 
> Honestly I've installed Ubuntu countless times, mostly servers. Since
> 7.04 i seem to get this every time! On different machines and VMs. I
> assumed this was just a "lazy" way of forcing a disk check after its
> been installed. 
> 
> So all i do is install, apt-get upgrade, reboot, reboot... and then all
> is fine after that... almost like a post install intentional mess that
> sorts itself out.
> 
> Later,
> Michael
> 

Ahh I'm glad I'm not the only one experiencing the problem.

I'm hoping that 7.10 won't have any issues like this.  I must admit 7.10 
Beta looks okay.

Rob

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems after update

[Rob Beard]

MailoGroups wrote:
>> Snip...
>> Quite what the actual problem is, I don't know but I wouldn't be looking
>> at changing batteries, I'd suspect some hardware incompatibility.
>>   
> Have you actually replaced the hard drive?
> Or at least run a decent disk checker on it (the one from Maxtor  
> excellent)?
> 
> Installing a whole new OS on a flakey harddrive is a recipe for disaster.
> 
> In my experience once drive start showing back sectors they usually go 
> bang pretty quickly.
> 40-60GB laptop drive are pretty cheap these days and most laptops have 
> bays so they are easy to change.
> 
It's a brand new Seagate Momentus 54200 2.5" Hard Drive, the old drive 
was faulty hence putting in this new one.

I will check the drive when my dad is back from holiday.

Rob



-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems after update

[Stephen Drake]

On Sat, 2007-10-06 at 10:42 +0100, Michael Holloway wrote:
> On Sat, 2007-10-06 at 09:11 +0100, David Restall - System Administrator
> wrote:
> > Hi Rob,
> > 
> > > I've been trying to install Ubuntu 7.04 on my dad's Thinkpad R50e 
> > > notebook this evening with not much luck.
> > 
> > Snip...
> > 
> > > I then rebooted again, and during the reboot the machine complained 
> > > about not having a disk check for about 49,710 days.  It ran through the 
> > > disk check and rebooted, it then on the second reboot said exactly the 
> > > same thing.
> > 
> > It isn't the battery - I don't know what it is but it's much nastier
> > than a dead battery :-(
> > 
> > Doing some simple maths :-
> > 
> > 2 ^ 32 = 4294967296
> > MAXINT = 4294967296 - 1 = 4294967295
> > 4294967295 / 86400 = 49710.2696181
> > 
> > this is unlikely to be a battery problem.  It looks as if some routine
> > is not reading the date correctly and it is returning either 0 or MAXINT.
> > For those that haven't clicked, 4294967295 is biggest number that can be
> > represented in a 32 bit word and 86400 is the number of seconds in a day.
> > Standard UTC uses the same 32 bits, that's why we have to worry about 2038
> > (1970 + 49000 days).
> > 
> > Quite what the actual problem is, I don't know but I wouldn't be looking
> > at changing batteries, I'd suspect some hardware incompatibility.
> > 
> > Some numbers just ring funny :-)
> > 
> > TTFN
> 
> 
> Hi
> 
> Honestly I've installed Ubuntu countless times, mostly servers. Since
> 7.04 i seem to get this every time! On different machines and VMs. I
> assumed this was just a "lazy" way of forcing a disk check after its
> been installed. 
> 
> So all i do is install, apt-get upgrade, reboot, reboot... and then all
> is fine after that... almost like a post install intentional mess that
> sorts itself out.
> 
> Later,
> Michael
> 
> 
> 

Yeah, I get this all the time too.

There's at least two bug reports already open on this issue.
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/96471
and https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/107793

Steve


-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems after update

[Michael Holloway]

On Sat, 2007-10-06 at 09:11 +0100, David Restall - System Administrator
wrote:
> Hi Rob,
> 
> > I've been trying to install Ubuntu 7.04 on my dad's Thinkpad R50e 
> > notebook this evening with not much luck.
> 
> Snip...
> 
> > I then rebooted again, and during the reboot the machine complained 
> > about not having a disk check for about 49,710 days.  It ran through the 
> > disk check and rebooted, it then on the second reboot said exactly the 
> > same thing.
> 
> It isn't the battery - I don't know what it is but it's much nastier
> than a dead battery :-(
> 
> Doing some simple maths :-
> 
> 2 ^ 32 = 4294967296
> MAXINT = 4294967296 - 1 = 4294967295
> 4294967295 / 86400 = 49710.2696181
> 
> this is unlikely to be a battery problem.  It looks as if some routine
> is not reading the date correctly and it is returning either 0 or MAXINT.
> For those that haven't clicked, 4294967295 is biggest number that can be
> represented in a 32 bit word and 86400 is the number of seconds in a day.
> Standard UTC uses the same 32 bits, that's why we have to worry about 2038
> (1970 + 49000 days).
> 
> Quite what the actual problem is, I don't know but I wouldn't be looking
> at changing batteries, I'd suspect some hardware incompatibility.
> 
> Some numbers just ring funny :-)
> 
> TTFN


Hi

Honestly I've installed Ubuntu countless times, mostly servers. Since
7.04 i seem to get this every time! On different machines and VMs. I
assumed this was just a "lazy" way of forcing a disk check after its
been installed. 

So all i do is install, apt-get upgrade, reboot, reboot... and then all
is fine after that... almost like a post install intentional mess that
sorts itself out.

Later,
Michael



-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems after update

[MailoGroups]

> Snip...
> Quite what the actual problem is, I don't know but I wouldn't be looking
> at changing batteries, I'd suspect some hardware incompatibility.
>   
Have you actually replaced the hard drive?
Or at least run a decent disk checker on it (the one from Maxtor  
excellent)?

Installing a whole new OS on a flakey harddrive is a recipe for disaster.

In my experience once drive start showing back sectors they usually go 
bang pretty quickly.
40-60GB laptop drive are pretty cheap these days and most laptops have 
bays so they are easy to change.



-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems after update

[David Restall - System Administrator]

Hi Rob,

> I've been trying to install Ubuntu 7.04 on my dad's Thinkpad R50e 
> notebook this evening with not much luck.

Snip...

> I then rebooted again, and during the reboot the machine complained 
> about not having a disk check for about 49,710 days.  It ran through the 
> disk check and rebooted, it then on the second reboot said exactly the 
> same thing.

It isn't the battery - I don't know what it is but it's much nastier
than a dead battery :-(

Doing some simple maths :-

2 ^ 32 = 4294967296
MAXINT = 4294967296 - 1 = 4294967295
4294967295 / 86400 = 49710.2696181

this is unlikely to be a battery problem.  It looks as if some routine
is not reading the date correctly and it is returning either 0 or MAXINT.
For those that haven't clicked, 4294967295 is biggest number that can be
represented in a 32 bit word and 86400 is the number of seconds in a day.
Standard UTC uses the same 32 bits, that's why we have to worry about 2038
(1970 + 49000 days).

Quite what the actual problem is, I don't know but I wouldn't be looking
at changing batteries, I'd suspect some hardware incompatibility.

Some numbers just ring funny :-)

TTFN


D
ubuntu/uk-2007-10-06.txubuntu-uk [EMAIL PROTECTED]
++
| Dave Restall, Computer Nerd, Cyclist, Radio Amateur G4FCU, Bodger  |
| Mob +44 (0) 7973 831245  Skype: dave.restall Radio: G4FCU  |
| email : [EMAIL PROTECTED] Web : Not Ready Yet :-(   |
++
| Any father who thinks he's all important should remind himself that|
| this country honors fathers only one day a year while pickles get a|
| whole week.|
++


-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems after update

[Rob Beard]

Farran Lee wrote:
> Hi Rob
> just had that happen with my laptop.
> Inside is a tiny battery that powers the BIOS memory (or something). My
> laptop is awfully old, and the battery has finally gone flat. This means
> that every time my laptop is disconnected from the mains, it forgets all
> the settings I have made in the BIOS. It complains at me a lot, but I
> have got round it.
> The BIOS (as far as I am aware - I'm only 14, so don't quote me on this)
> manages the system clock as well - consequently, it forgets the time and
> date. Now, when I boot up, it complains that it has not had a system
> check for several thousand days (last time I worked it out, it was over
> 316 years). This obviously cannot be the case! When an error is found on
> the hd and the fsck reaches the end, it normally says something like
> this to me: "Errors found on hda1! Linux is going down for reboot in 5!"
> My guess is that all that needs to be done is to replace the battery. It
> is only a tiny round [lithium-ion?] battery.
> Hope this helped... as I said, I'm only 14, so I could be talking a load
> of rubbish... :P
> Farran
> 

Hi Farran,

Thanks for the suggestion, the battery is fine, it also was running on 
the mains.  The amount of days in question (over 49,700) works out at 
about 163 years, and it said the date was in the future!  (so much for 
the Millenium bug!)

Funny you should mention your age, I first found out about the BIOS 
batteries when I was about 13/14 when I first started learning about the 
hardware side of PCs - I put a password on the BIOS of my dad's PC and 
forgot the password, luckily the technician at my school at the time 
told me how to clear the CMOS :-)

I've installed 7.10 Beta now, I'm actually quite impressed with it apart 
from having to jump through a load of hurdles to get DVD playback 
working (I'm sure it was easier under 7.04 after adding the Medibuntu 
repos).

At least my dad's laptop is working now anyway.  When he gets back from 
his holiday I'll try and do a fresh install of the full version of 
Ubuntu 7.10.

Rob


-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems afterupdate

[james]

I wish I knew what I know now at 57, which is precious little, when I was
14!

James
- Original Message -
From: "Chris Rowson" <[EMAIL PROTECTED]>
To: "British Ubuntu Talk" 
Sent: Friday, October 05, 2007 10:27 PM
Subject: Re: [ubuntu-uk] Fsck forced on boot up due to date problems
afterupdate


> > Inside is a tiny battery that powers the BIOS memory (or something). My
> > laptop is awfully old, and the battery has finally gone flat. This means
> > that every time my laptop is disconnected from the mains, it forgets all
> > the settings I have made in the BIOS. It complains at me a lot,
>
> Sounds like it's worth looking at :-) I'm guessing that if Rob keeps
> his laptop plugged into the mains and restarts it then it shouldn't
> fsck if that's the problem then?
>
> > Hope this helped... as I said, I'm only 14, so I could be talking a load
> > of rubbish... :P
>
> Meh, doesn't matter how old you are mate ;-)
>
> Chris
>
> --
> ubuntu-uk@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
> https://wiki.kubuntu.org/UKTeam/


-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems after update

[Chris Rowson]

> Inside is a tiny battery that powers the BIOS memory (or something). My
> laptop is awfully old, and the battery has finally gone flat. This means
> that every time my laptop is disconnected from the mains, it forgets all
> the settings I have made in the BIOS. It complains at me a lot,

Sounds like it's worth looking at :-) I'm guessing that if Rob keeps
his laptop plugged into the mains and restarts it then it shouldn't
fsck if that's the problem then?

> Hope this helped... as I said, I'm only 14, so I could be talking a load
> of rubbish... :P

Meh, doesn't matter how old you are mate ;-)

Chris

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

Re: [ubuntu-uk] Fsck forced on boot up due to date problems after update

[Farran Lee]

Hi Rob
just had that happen with my laptop.
Inside is a tiny battery that powers the BIOS memory (or something). My
laptop is awfully old, and the battery has finally gone flat. This means
that every time my laptop is disconnected from the mains, it forgets all
the settings I have made in the BIOS. It complains at me a lot, but I
have got round it.
The BIOS (as far as I am aware - I'm only 14, so don't quote me on this)
manages the system clock as well - consequently, it forgets the time and
date. Now, when I boot up, it complains that it has not had a system
check for several thousand days (last time I worked it out, it was over
316 years). This obviously cannot be the case! When an error is found on
the hd and the fsck reaches the end, it normally says something like
this to me: "Errors found on hda1! Linux is going down for reboot in 5!"
My guess is that all that needs to be done is to replace the battery. It
is only a tiny round [lithium-ion?] battery.
Hope this helped... as I said, I'm only 14, so I could be talking a load
of rubbish... :P
Farran

On Fri, 2007-10-05 at 21:34 +0100, Rob Beard wrote:
> Hi folks,
> 
> I've been trying to install Ubuntu 7.04 on my dad's Thinkpad R50e 
> notebook this evening with not much luck.
> 
> Basically my dad's had his laptop for a year and the hard drive 
> developed bad sectors just after the warranty ran out.  To complicate 
> things further, the installation files were on the hard disk itself 
> (good old Microsoft!).  Now I have got a set of install disks for the 
> laptop (my other half has exactly the same laptop) but I can't find 
> them, so to get my dad up and running again I decided to install Ubuntu 
> (okay, I'm hoping he moves over to Ubuntu).
> 
> Now this is where the problem starts.  I've installed Ubuntu 7.04 from a 
> Desktop CD, it all appears to install okay, I've partitioned the drive 
> as follows:
> 
> / 20GB Ext3
> /home 99GB Ext3
> swap  1GB Swap
> 
> I rebooted the machine after the install, so far so good.  Everything 
> booted up fine.  I then went to install the updates (about 126 updates), 
> again these installed fine.
> 
> I then rebooted again, and during the reboot the machine complained 
> about not having a disk check for about 49,710 days.  It ran through the 
> disk check and rebooted, it then on the second reboot said exactly the 
> same thing.
> 
> I checked the date and time, all were fine, I then reinstalled again.
> 
> On the second reinstall it did exactly the same as before, reporting 
> that the disk hadn't been checked for over 49,000 days, after the forced 
> fsck it rebooted and then appeared to boot okay.
> 
> I'm going to try Ubuntu 7.10 Beta, my dad goes away this weekend for a 
> week and I needed to get his machine working.  When he's back hopefully 
> I'll be able to put the full release of 7.10 on the laptop (along with 
> Windows if he really really wants it).
> 
> Just wondered though if anyone else had seen this problem?
> 
> Ta,
> 
> Rob
> 


-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/

[ubuntu-uk] Fsck forced on boot up due to date problems after update

[Rob Beard]

Hi folks,

I've been trying to install Ubuntu 7.04 on my dad's Thinkpad R50e 
notebook this evening with not much luck.

Basically my dad's had his laptop for a year and the hard drive 
developed bad sectors just after the warranty ran out.  To complicate 
things further, the installation files were on the hard disk itself 
(good old Microsoft!).  Now I have got a set of install disks for the 
laptop (my other half has exactly the same laptop) but I can't find 
them, so to get my dad up and running again I decided to install Ubuntu 
(okay, I'm hoping he moves over to Ubuntu).

Now this is where the problem starts.  I've installed Ubuntu 7.04 from a 
Desktop CD, it all appears to install okay, I've partitioned the drive 
as follows:

/   20GB Ext3
/home   99GB Ext3
swap1GB Swap

I rebooted the machine after the install, so far so good.  Everything 
booted up fine.  I then went to install the updates (about 126 updates), 
again these installed fine.

I then rebooted again, and during the reboot the machine complained 
about not having a disk check for about 49,710 days.  It ran through the 
disk check and rebooted, it then on the second reboot said exactly the 
same thing.

I checked the date and time, all were fine, I then reinstalled again.

On the second reinstall it did exactly the same as before, reporting 
that the disk hadn't been checked for over 49,000 days, after the forced 
fsck it rebooted and then appeared to boot okay.

I'm going to try Ubuntu 7.10 Beta, my dad goes away this weekend for a 
week and I needed to get his machine working.  When he's back hopefully 
I'll be able to put the full release of 7.10 on the laptop (along with 
Windows if he really really wants it).

Just wondered though if anyone else had seen this problem?

Ta,

Rob

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.kubuntu.org/UKTeam/