Yeah, I bought the clock, attched it and set it. Never got the
message again. Becuase you don't have a clock, the date resets every
time you reboot.
Quoting Fabio Vaz <>:
> I have the same problem here. I created a new 1gb CF with the debian
> linux and every boot I get the following message :
>
> /dev/hda1 has gone 49710 days without being checked, check forced
>
> Did anyone get a solution for this "every boot fsck" problem ?
>
>
> --- In "fabianmejia" <> wrote:
>>
>> Unfortunately, it's not possible for me to have access to another
>> Linux Box. I think I will try to us a different CF.
>>
>> Do you think is it possible to modify somewhere in the system so CF
>> filesystem is not checked (bypass)? Is it bad doing this?
>>
>> Regards
>>
>> --- In Jason Stahls <jason@> wrote:
>> >
>> > The DriveReady bit is normal (I think) mine does it too. The
> file
>> > system check doesn't look right tho, I don't get that. Check the
> card
>> > on another Linux box and verify the filesystem.
>> >
>> > Jason
>> >
>> > fabianmejia wrote:
>> > > Hi Jason,
>> > >
>> > > Thanks a lot for your help.
>> > >
>> > > I followed the steps you mention and yes, it worked .... but
>> > > partially. After some fights with fconfig (I din't have the jp3
>> > > plugged :S) I did make the system boot from the CF, but the
> following
>> > > happens:
>> > >
>> > > 1. Still shows that message:
>> > > hda: task_no_data_intr: status=0x58 { DriveReady SeekComplete
>> > > DataRequest }
>> > >
>> > > hda: 989856 sectors (507 MB) w/1KiB Cache, CHS=982/16/63
>> > > Partition check:
>> > > /dev/ide/host0/bus0/target0/lun0:hda: status error:
> status=0x58 {
>> > > DriveReady SeekComplete DataRequest }
>> > >
>> > >
>> > > 2. At the end, I get this message:
>> > > ===================
>> > > /dev/hda1 has gone 49710 days without being checked, check
> forced.
>> > > Pass 1: Checking inodes, blocks, and sizes
>> > > Pass 2: Checking directory
> structure
>> > >
>> > > Pass 3: Checking directory
> connectivity
>> > >
>> > > Pass 3A: Optimizing directories
>> > > Pass 4: Checking reference
> counts
>> > >
>> > > Pass 5: Checking group summary
> information
>> > >
>> >
>>
>
>> > >
>> > > /dev/hda1: ***** FILE SYSTEM WAS MODIFIED *****
>> > > /dev/hda1: ***** REBOOT LINUX *****
>> > > /dev/hda1: 13989/123952 files (0.4% non-contiguous),
> 226672/494800
>> blocks
>> > >
>> > > fsck corrected errors on the root partition, but requested that
>> > > the system be rebooted (exit code 3).
>> > > =====================
>> > >
>> > > After checking, system reboots and goes to this part again and
> again
>> > > (Everytime it reboots it says it has to check the disk again,
> and
>> reebot)
>> > >
>> > > What do you think? Is there anything wrong with the CF? Is there
>> > > anyway to fix it? (I already tried fsck, but after fixed in my
> PC, it
>> > > still doesn't work in card: 4000 days without being checked???)
>> > >
>> > > Regards
>> >
>>
>
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|