Uh, this might be a quick question, since it's a little abstract. I'm dual booting and I've noticed that every time I boot into Arch after I've booted into one of my other systems, there is a forced file system check. It's not a huge deal, because I use Arch almost exclusively, but I have to say, I cringe at the thought of having to boot into one of the other systems now. How would you trouble shoot this? I have also never seen a system where after every ~20 reboots, a file system check is mandatory. This might just be my ignorance here, so a reference to some background about that part of the boot process might suffice. Thanks in advance. -- chris
On 01/21/2010 09:11 PM, christopher floess wrote:
Uh, this might be a quick question, since it's a little abstract.
I'm dual booting and I've noticed that every time I boot into Arch after I've booted into one of my other systems, there is a forced file system check. It's not a huge deal, because I use Arch almost exclusively, but I have to say, I cringe at the thought of having to boot into one of the other systems now.
How would you trouble shoot this? I have also never seen a system where after every ~20 reboots, a file system check is mandatory. This might just be my ignorance here, so a reference to some background about that part of the boot process might suffice.
Thanks in advance.
-- chris
Is the other operative system a windows? Maybe the hardware clock is continuously changing, so the last write looks like in the future? -- Enrico Carlesso<ecarlesso@ecarlesso.org> http://www.ecarlesso.org carlessoenrico @ skype enricocarlesso@gmail.com @ gtalk& msn
On Fri, Jan 22, 2010 at 4:45 AM, Enrico Carlesso <enrico@ecarlesso.org> wrote:
On 01/21/2010 09:11 PM, christopher floess wrote:
Uh, this might be a quick question, since it's a little abstract.
I'm dual booting and I've noticed that every time I boot into Arch after I've booted into one of my other systems, there is a forced file system check. It's not a huge deal, because I use Arch almost exclusively, but I have to say, I cringe at the thought of having to boot into one of the other systems now.
How would you trouble shoot this? I have also never seen a system where after every ~20 reboots, a file system check is mandatory. This might just be my ignorance here, so a reference to some background about that part of the boot process might suffice.
Thanks in advance.
-- chris
Is the other operative system a windows? Maybe the hardware clock is continuously changing, so the last write looks like in the future?
^ what he said Also, the hard disk check can be set. I set mine to every 30 days (previously was rebooting up to 10 times a day from playing with kernel configs). Its not a hard-coded check, and can be (I think) cancelled with Ctrl-C, based on some other mails going around here a few days back.
On 01/21/2010 01:11 PM, christopher floess wrote:
Uh, this might be a quick question, since it's a little abstract.
I'm dual booting and I've noticed that every time I boot into Arch after I've booted into one of my other systems, there is a forced file system check. It's not a huge deal, because I use Arch almost exclusively, but I have to say, I cringe at the thought of having to boot into one of the other systems now.
How would you trouble shoot this? I have also never seen a system where after every ~20 reboots, a file system check is mandatory. This might just be my ignorance here, so a reference to some background about that part of the boot process might suffice.
Thanks in advance.
-- chris
Are you using shut down or hibernate? I think if you hibernate Windows, your partitions don't get unmounted and that could be what's happening.
To control the frequency of automatic checks, you can use tune2fs.
On 01/21/2010 02:11 PM, christopher floess wrote:
Uh, this might be a quick question, since it's a little abstract.
I'm dual booting and I've noticed that every time I boot into Arch after I've booted into one of my other systems, there is a forced file system check. It's not a huge deal, because I use Arch almost exclusively, but I have to say, I cringe at the thought of having to boot into one of the other systems now.
How would you trouble shoot this? I have also never seen a system where after every ~20 reboots, a file system check is mandatory. This might just be my ignorance here, so a reference to some background about that part of the boot process might suffice.
Thanks in advance.
-- chris
Usually you set your system clock to 'localtime' for your unix install since windows only uses localtime. If you have your unix install using gmt, then on every reboot (at least those where the reboot occurs within a timeframe less than your localtime offset from gmt), fsck can get called because the filesystem time has changed. Big pain. If dual-booting, make sure you configure /etc/rc.conf and set: HARDWARECLOCK="localtime" If all that is already done -- dunno?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Usually you set your system clock to 'localtime' for your unix install since windows only uses localtime. If you have your unix install using gmt, then on every reboot (at least those where the reboot occurs within a timeframe less than your localtime offset from gmt), fsck can get called because the filesystem time has changed. Big pain.
If dual-booting, make sure you configure /etc/rc.conf and set:
HARDWARECLOCK="localtime"
If all that is already done -- dunno??
Damn, I got all excited there, but it turns out that it's already in there. Yeah, it's really weird. Thanks anyway. Which of the logs might this be recorded in? -- chris
Are you using automatic time synchronisation (NTP) on any of the systems? This might be the problem. Sébastien Leblanc
On 01/23/2010 09:47 AM, Sébastien Leblanc wrote:
Are you using automatic time synchronisation (NTP) on any of the systems? This might be the problem.
Sébastien Leblanc
Yes I am. How does this have an affect? -- Chris
Okay, so I got smart an realized that this whole time I'd assumed that the fault was with Arch, simply because it detected the error. False. Windows was set to the wrong time zone, so when I booted into it, it set the to that time zone time, and a subsequent reboot by Arch was then seen as the last boot having been in future time. Sorry for the noise. -- Chris
There you go.
participants (7)
-
Brendan Long
-
christopher floess
-
David C. Rankin
-
Enrico Carlesso
-
gt
-
Ng Oon-Ee
-
Sébastien Leblanc