[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
** Changed in: e2fsprogs (Ubuntu Gutsy) Target: tribe-4 => tribe-5 -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
** Changed in: e2fsprogs (Ubuntu Gutsy) Target: tribe-3 => tribe-4 -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
I don't think bug #89069 is a duplicate of this bug. Bug #89069 is clearly a bug in Ubiquity, which updates the system clock to localtime by syncing to a time server shortly after starting its real installation work, but without updating the timezone accordingly. It is experienced by people in GMT + timezones only. - It hasn't been fixed yet in Tribe-2 CD. I suggest people experience this bug (bug #63175) check their hardware clocks: 1. Type "sudo hwclock -r" regularly to see if it goes slower than the system time. 2. Power cycle your computers and boot straight into BIOS to see if the hardware clocks are correct. (Perhaps keep your computers switched off with power cables disconnected for a couple of hours.) -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
We are checking the file system after 180 days by default and this errors seems to occur for people who are ahead of GMT by a few hours (and people with wasted batteries probably). Could we not simply fix this by adding 12+ hours to the time variable in the code that checks against last fsck? In reality that would cause a check every 179.5 days, but who's counting? :) The last comment by tillicollaps3 describes a work-around that suggests this should work. ** Changed in: e2fsprogs (Ubuntu Gutsy) Target: ubuntu-7.04 => tribe-3 -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
This is for #89069 but because it is marked as a duplicate of this topic, should be useful here too. Found a workaround for who has mine same problem (only at first boot after installation - Last mount in future - fsck died with exit status 3), thanks to #ubuntu-it. Install normally ubuntu, after installation shutdown the system and does not start for so much hours as the difference (+) with GMT is (in my case ROME, boot system 2 hours after installing). No error messages will appear on first Feisty boot. enjoy ;) -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Two things about ogra's superblock info: Filesystem created: Wed Mar 21 14:46:13 2007 Last mount time: Wed Mar 21 14:28:37 2007 Last write time: Wed Mar 21 14:28:37 2007 Mount count: 2 Maximum mount count: 26 Last checked: Wed Mar 21 14:19:59 2007 Check interval: 15552000 (6 months) First, the filesystem creation time is later than the last mount time. Second, the check interval is set (don't we set that to zero by default now?). If my guess is correct, it should be possible to reproduce this problem by setting the hardware clock backward between installation and first boot. Systems with a faulty CMOS battery, where the clock resets to an earlier epoch at each boot, would exhibit this type of problem. -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
I suspect the problem does not relate to the filesystem check interval, but to one of the other timestamps, such as the last mount time. A discrepancy there will trigger a full filesystem check regardless of the checkinterval. For example: potpal:[/tmp] dd if=/dev/zero bs=1M count=1 of=fs.ext3 1+0 records in 1+0 records out 1048576 bytes (1.0 MB) copied, 0.00205541 seconds, 510 MB/s potpal:[/tmp] mke2fs -j fs.ext3 mke2fs 1.40-WIP (14-Nov-2006) fs.ext3 is not a block special device. Proceed anyway? (y,n) y Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) 128 inodes, 1024 blocks 51 blocks (4.98%) reserved for the super user First data block=1 Maximum filesystem blocks=1048576 1 block group 8192 blocks per group, 8192 fragments per group 128 inodes per group Writing inode tables: done Filesystem too small for a journal Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 38 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. potpal:[/tmp] debugfs -w fs.ext3 debugfs 1.40-WIP (14-Nov-2006) debugfs: ssv mtime 20100101 debugfs: quit potpal:[/tmp] fsck -n /tmp/fs.ext3 fsck 1.40-WIP (14-Nov-2006) e2fsck 1.40-WIP (14-Nov-2006) Superblock last mount time is in the future. Fix? no /tmp/fs.ext3 contains a file system with errors, check forced. 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 /tmp/fs.ext3: 11/128 files (9.1% non-contiguous), 38/1024 blocks -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Fresh installed feisty does the same thing, it runs fsck at every boot. Do you think the reason is the same? -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
If I were not wrong, this problem shall be experienced by people living in the GMT minus timezones who reboots often. The root cause of this problem is that the kernel initializes the system clock from the RTC, the hardware clock on motherboard, which is several hours behind UTC in GMT minus timezones. Therefore, during the early stage of the boot process, the system clock is several hours behind the UTC, and fsck complains. -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
After some researching, I think it must be caused by the fact that the hwclock.sh init script gets run very late in the boot process. Priror to S50hwclock.sh, the system clock (or kernel clock) is uninitialized, so fsck-1.40 complains the last mount/write time is in the future. -- Edgy Beta -- fsck on every (re)boot https://bugs.launchpad.net/bugs/63175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Bringing milestone forward ** Changed in: e2fsprogs (Ubuntu) Target: 7.04-beta => ubuntu-7.04 -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
mvo, i think i have the cause for my fsck ... my bios clock isnt set to gmt but the fs creation happens before setting the clock, the timestamp on the created filesysstem is in the future -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
tune2fs 1.40-WIP (14-Nov-2006) Filesystem volume name: Last mounted on: Filesystem UUID: 0e176fbb-7754-4436-94b4-b68a3c86221e Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: signed directory hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 2203200 Block count: 4399801 Reserved block count: 219990 Free blocks: 3743628 Free inodes: 2081545 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 1022 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16320 Inode blocks per group: 510 Filesystem created: Wed Mar 21 14:46:13 2007 Last mount time: Wed Mar 21 14:28:37 2007 Last write time: Wed Mar 21 14:28:37 2007 Mount count: 2 Maximum mount count: 26 Last checked: Wed Mar 21 14:19:59 2007 Check interval: 15552000 (6 months) Next check after: Mon Sep 17 15:19:59 2007 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode:8 First orphan inode: 587597 Default directory hash: tea Directory Hash Seed: 42e4f4c3-98fd-474d-b3f2-c507f79196bb Journal backup: inode blocks this is the output on ogras test system. but the fsck happend only on the first boot on a fresh edubuntu server install. Saying its 49710 days without check ... the clock is correct in teh installer as well as in teh installed system though. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
$ cat /var/log/fsck/* Log of fsck -C -R -A -a Tue Mar 13 03:55:03 2007 fsck 1.39 (29-May-2006) dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/sda1: 220649 files, 3665979/15312004 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/hdb5: 122194 files, 1681108/1876384 clusters Tue Mar 13 03:56:11 2007 Log of fsck -C -a -t ext3 /dev/hdb1 Tue Mar 13 03:55:03 2007 fsck 1.39 (29-May-2006) /dev/hdb1: clean, 296511/2496960 files, 2196210/4992190 blocks Tue Mar 13 03:55:03 2007 $ sudo tune2fs -l /dev/-insert-device-here- (root partition only) tune2fs 1.39 (29-May-2006) Filesystem volume name: Last mounted on: Filesystem UUID: b1c9ae04-50dc-4513-9a52-ef3b7c8a0640 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 2496960 Block count: 4992190 Reserved block count: 249609 Free blocks: 2795980 Free inodes: 2200449 First block: 0 Block size: 4096 Fragment size:4096 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16320 Inode blocks per group: 510 Last mount time: Tue Mar 13 03:55:03 2007 Last write time: Tue Mar 13 03:55:03 2007 Mount count: 25 Maximum mount count: 30 Last checked: Tue Feb 27 13:35:24 2007 Check interval: 0 () Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode:8 Journal backup: inode blocks $ date mar mar 13 04:27:46 COT 2007 -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Alright, I just rebooted again, and again, fine, no fsck. Weird. I checked the BIOS date, and it shows up fine 13-March as I'd expect. Output of 'date' from my system is: [EMAIL PROTECTED]:~$ date Tue Mar 13 09:22:19 SGT 2007 [EMAIL PROTECTED]:~$ I'll attach the tune2fs output, as well as /var/log/udev. But as of right now, it seems to 'magically' have resolved itself... :-\ ** Attachment added: "output of tune2fs -l /dev/hda1" http://librarian.launchpad.net/6766350/tune2fs_output.txt -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
gzipped /var/log/udev ** Attachment added: "gzipped /var/log/udev" http://librarian.launchpad.net/6766355/udev.gz -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Sorry it's taken me a while to get back to this. As of right now, I'm thoroughly confused. I left the Edgy box up for the past couple weeks (no need to reboot, and was tired of the fsck action). But I rebooted now just to generate the bootchart - and fsck didn't run. Also, I've checked the tune2fs output, and it looks like now the last fsck check has been updated in the output to reflect 28-Feb (my last reboot prior to todays). My system clock appears to be behaving normally. The "future" date from my previous attachment was because sudo was giving me grief (date too far in the future). I ran sudo for some stuff, then I enabled NTP which changed my clock to +8GMT (I'm in Singapore). So to avoid rebooting I had thrown my clock even further ahead manually in order to get sudo to behave without rebooting. I'll attach the bootchart anyways, as well as /var/log/udev. The output for cat /var/log/fsck/* is small, so I'll paste: [EMAIL PROTECTED]:~$ cat /var/log/fsck/* Log of fsck -C -R -A -a Tue Mar 13 08:51:23 2007 fsck 1.39 (29-May-2006) /dev/md0: clean, 11216/19546112 files, 4482325/39072064 blocks Tue Mar 13 08:51:23 2007 Log of fsck -C -a -t ext3 /dev/hda1 Tue Mar 13 08:51:23 2007 fsck 1.39 (29-May-2006) /dev/hda1: clean, 155148/9371648 files, 1243005/18731782 blocks Tue Mar 13 08:51:23 2007 [EMAIL PROTECTED]:~$ ** Attachment added: "bootchart from Daniel Wintschel" http://librarian.launchpad.net/6766339/edgy-20070313-1.png -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
I'm not in front of my Edgy-box right now, so I can't check any log files, but after the last post I think the whole problem might be related to using intervals for checking. The proof would be my two systems: the desktop checks my /home-partition (ext3) every 14 days (all the others are set to 30 boots) and suffers from this problem. My laptop has all partitions left at 30 boots and does not suffer from this. Now the only strange thing is, that editing /etc/fstab so that my FAT32-partitions won't be checked actually "resolves" the problem. I'll see if I can dig up some valuable logs. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
I looked at the checkfs scripts and the various forum posts to see if I can find any indication what causes this problem and also I tried to reproduce this on a vmware image without success so far. If someone is still affected by this problem I would really appreciate the output of: $ cat /var/log/fsck/* $ sudo tune2fs -l /dev/-insert-devices-here- $ date and the BIOS date settings. The puzzeling thing is that on the systems I have at hand the "check interval is unset: Check interval: 0 () This means that it shouldn't do this check even if the clock is off a lot. Debian sets this interval to 6 month, but for ext3 we haven't been using this neither in edgy nor dapper (according to my checks on fresh installs). If I run tune2fs -i and give it a different value than 0 I can easily reproduce the problem with a incorrect clock setting (as expected). I would really appreciate the logs from someone affected by this bug. Thanks, Michael ** Changed in: e2fsprogs (Ubuntu) Status: Confirmed => Needs Info -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Useful things from those affected would be: * a bootchart from your system. Install the "bootchart" package and reboot, attach the PNG from /var/log/bootchart * a copy of /var/log/udev from your system * output of tune2fs on the affected filesystems * output of "date" -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Assigned to mvo; please investigate this. Possibilities are that it's caused by faulty hardware clocks, and somehow it's not being set correctly (by the udev 85-hwclock.rules). Or maybe it's something even weirder. ** Changed in: e2fsprogs (Ubuntu) Assignee: Brian Murray => Michael Vogt -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Running 'sudo date -s @0' and then rebooting certainly seems to produce a thoroughly confused hardware clock for a couple of reboots. I wonder if this is a useful starting point. One thought I have is that we could use /etc/adjtime very early in the boot process (although probably not in the initramfs, or we'd have to update it at every boot) to try to make sure that the hardware clock is at least somewhat sane. It might take a couple of boots to stabilise after installation, but that's better than nothing. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Daniel, the log files you attached show that fsck thought the filesystems were clean. Was this from a manual run of fsck, or was it from the automatic one at boot, and if the latter did fsck decide to do a full filesystem check on the boot immediately before you attached these logs? Also, I note that your "last mount time" and "last write time" are in the future, to go along with your "last checked" being in the past. Does your system clock appear to be behaving normally? -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Milestoning for beta to make sure this doesn't fall off the radar. ** Changed in: e2fsprogs (Ubuntu) Target: None => beta -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Adding checkfs file ** Attachment added: "fsck output (checkfs) - Daniel Wintschel" http://librarian.launchpad.net/6580442/checkfs -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Adding checkroot file ** Attachment added: "fsck output (checkroot) - Daniel Wintschel" http://librarian.launchpad.net/6580441/checkroot -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Thanks for taking the time to report this bug and helping to make Ubuntu better. When fsck is run it logs to /var/log/fsck/checkfs and /var/log/fsck/checkroot. Could you please add those files to your bug report? Thanks in advance. ** Changed in: e2fsprogs (Ubuntu) Assignee: (unassigned) => Brian Murray -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
I can confirm the same thing on my system, but in addition, I notice the following output from tune2fs: [EMAIL PROTECTED]:~$ sudo tune2fs -l /dev/hda1 tune2fs 1.39 (29-May-2006) Filesystem volume name: Last mounted on: Filesystem UUID: 01489b91-7a70-4355-9108-b0b86ad2c4da ... ... Last mount time: Thu Mar 29 07:48:46 2007 Last write time: Thu Mar 29 07:48:46 2007 Mount count: 7 Maximum mount count: 30 Last checked: Thu Jan 1 07:30:00 1970 Check interval: 0 () ... What I notice is that the last checked time doesn't seem to be getting updated. It shows Jan 1, 1970 - even though if just ran through fsck 30 minutes ago, and every time I boot. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Do you have any FAT32-partitions? It seems, that fsck always checks FAT32-partitions, even though it may show it was checking your root and/or home partition. Try editing your fstab and change the two numbers at the end of the FAT32 entries (probably 0 and 1) to 0 for both. This will cause the partitions not to be checked on startup, so don't do it, if you have anything important stored on your FAT32-partiton(s). Alternatively you can try this with all the other drives, one at a time, to see which one is really checked. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
i got the same fsck issue, making my boot time around 30min. Additionnaly i got a OOM killer during the fsck done during the boot. from dmesg: [17180557.48] Out of Memory: Kill process 3528 (logsave) score 5361 and children. [17180557.48] Out of memory: Killed process 3529 (fsck). and the box is 512mbyte of ram + 256mbyte of swap. so largely enougth to support a fsck. i dunno what to do and the fsck during the boot doesnt say which partition is checked which make it very hard to diagnose -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
AFAIK it's still not fixed. In my case editing /etc/fstab helped. You need to change the last two digits for FAT32 partitions to zero (normally the last one is 1). The effect is, that the partitions won't be checked. It's a nasty workaround but since I only use it to share certain files between Ubuntu and WinXP, it doesn't matter for me. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Have this been fixed or looked in to??? Four months had passed...And I believe this is kinda serious bug. Or very very annoying at least. Regards, Matías -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
I have the same issue with Edgy Eft final. It's there a way to get rid of this problem? Taking so much time to boot. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Same with me on a fresh Edgy install on a Sony Vaio FS415B, formatted as ext3. Possibly related: On running sudo tune2fs -l /dev/ Mount count: 13 Maximum mount count: 30 Last checked: Thu Jan 1 01:00:00 1970 Mmmm, that date looks suspicious! -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Same here, at least on my desktop. Fresh Edgy Final installed. No problems with Dapper. Samsung SP1604N /dev/hda1 10 Gb - ntfs /dev/hda2 5 Gb - ntfs /dev/hda3 1 kb - extended /dev/hda4 18,6 Gb - ext3 /dev/hda5 63 Gb - ntfs /dev/hda6 52,4 Gb - ext3 Samsung SP1604N (yep, another one) /dev/hdb1 203,9 Mb - vfat /dev/hdb2 1 kb - extended /dev/hdb3 14,6 - ext3 /dev/hdb4 1,5 Gb - swap /dev/hda5 40 Gb - vfat /dev/hda6 50 Gb - ext3 /dev/hda7 10,3 Gb - ext3 No problems on my notebook, HP nx6110. Fresh Edgy Final. /dev/hda1 7,9 GB - ntfs /dev/hda2 9,8 GB - ext3 /dev/hda3 1 kb - extended /dev/hda4 18,1 GB - ext3 /dev/hda5 475,2 Mb - vfat /dev/hda6 949,1 Mb - swap -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
I confirm this bug: Gigabyte 7VTXE+ WDC WD1200JB 120 gb /dev/hda1 21Gb - fat32 /media/hda1 /dev/hda5 46Gb - fat32 /media/hda5 /dev/hda5 40Gb - fat32 /media/hda6 /dev/hda7 6,1Gb - ext3 / /dev/hda8 512Mb - swap -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
I can add myself: Asus K8N-E Athlon 64 2800+ 1 GB RAM 1x 160 GB Samsung P-ATA drive 1x 250 GB Samsung S-ATA drive Partitions: /dev/hda1 56GB /media/windows - Windows System Disk (ntfs) /dev/hda2 32GB /root (ext3) /dev/hda5 60GB /home (ext3) /dev/hda6 2GB swap /dev/sda1 128GB /media/daten (FAT32) - shared between Windows and Linux /dev/sda2 56GB/media/ablage - Windows data pile for everything (ntfs) /dev/sda3 49GB/tmp I am running Edgy final (32bit) with -generic kernel. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Same problem here. Abit NF7-S AMD Athlon XP 2600+ mobile 1 GB RAM NVidia 6600Gt Kernel: 2.6.17-10-generic IDE 30GB 2x SATA 80GB Partitions: hda1 1GB /boot md0 14GB / (raid0) md1 144GB /home (raid0) md2 2GB swap (raid0) All formated with ReiserFS. The Filesystems are clean. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Same problem on an Asus W3V notebook. IDE 60GB HDD Intel Pentium M 1.86 1.5Gh RAM Partitions: 29gig windows (fat32) 21gig home (ext3) 6gig root (ext3) no swap -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Here is a bootchart from my system. ** Attachment added: "chart" http://librarian.launchpad.net/4918059/edgy-20061021-1.png -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Happens here, 32bit. One 160gb drive Partitions: * 1gig swap * 20gig root (ext3) * 20gig /home (ext3) * rest a data partition (vfat) Two 250gb drives * one partiion, in RAID1 array with mdadm -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
** Changed in: e2fsprogs (Ubuntu) Importance: Undecided => Medium -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Same problem. On amd64 with jfs fs. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
** Changed in: Ubuntu Sourcepackagename: None => e2fsprogs ** Changed in: e2fsprogs (Ubuntu) Status: Unconfirmed => Confirmed -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Same here -- I exerienced this issue with both the 32 & 64 bit beta's. Running on a Dell Optiplex GX620 with Nvidia card being the only change to the standard build. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
Same problem here, fresh edgy beta install. Fsck checks every boot all mounted partitions (2 fat32, 2 ext3, 1 xfs). On dapper before there were no problems, check runs clean every time. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63175] Re: Edgy Beta -- fsck on every (re)boot
I am also experiencing the same problem. I used "upgrade-manager -c -d" to install Edgy Beta (amd64), and now fsck checks both partitions (/boot and /, both ext3) on every single reboot. To the original reporter: the usplash bug is at https://launchpad.net/distros/ubuntu/+source/usplash/+bug/56587/ -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
