Comment 6 for bug 183426

Ok, it finally finished installing and after it rebooted it took a while at the secondary fsck item. I think it was running fsck on /dev/sda6 (vfat fat32). Is that what is happening during the install process also? And if so how does it know if a vfat fat32 partition is clean or dirty. I don't recall it taking a long time to install in the past when there was a fat32 partition on a system.

I manually ran fsck.vfat on the partition after it finished booting and it seemed to be fine.

Chris

root@laptop-c2d:~# fsck.vfat -v /dev/sda6
dosfsck 2.11 (12 Mar 2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "MSWIN4.1"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
     65536 bytes per cluster
        32 reserved sectors
First FAT starts at byte 16384 (sector 32)
         2 FATs, 32 bit entries
   4525568 bytes per FAT (= 8839 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 9067520 (sector 17710)
   1131314 data clusters (74141794304 bytes)
63 sectors/track, 255 heads
 167750793 hidden sectors
 144825912 sectors total
Checking for unused clusters.
Checking free cluster summary.
/dev/sda6: 214325 files, 887049/1131314 clusters