On Sat, Jul 10, 2010 at 02:46:11AM -0700, patrick keshishian wrote:
> On Sat, Jul 10, 2010 at 2:21 AM, J.C. Roberts <list-...@designtools.org>
> wrote:
> > On Fri, 9 Jul 2010 17:29:18 +0200 Renzo <rfabr...@nerdshack.com> wrote:
> >>
> >> On Friday 09 July 2010 08:54:15 patrick keshishian wrote:
> >> > Hi,
> >> >
> >> > I recently attempted an installation from a usb memory stick, where
> >> > installation of xfont47.tgz failed consistently due to "crc
> >> > error"[0]. The stick was prepared following steps from OBSD FAQ[1].
> >> >
> >> > I recopied xfont47.tgz file to the stick, and confirmed (or so I
> >> > thought) that the source and new copy of this file were identical
> >> > using cmp(1).
> >> >
> >> > Restarting the install bombed on the same file. So I stuck the stick
> >> > in my source computer and mounted it and ran md5(1) on it. Sure
> >> > enough the checksum is different from the source. I did a umount(8)
> >> > and a mount(8), then ran md5(1) again, and this time yet a new
> >> > value was reported. While mounted, running md5(1) again reports the
> >> > same value
> >> > -- i assume this is because the file is cached at this point --
> >> > explaining why cmp(1) initially failed to raise a flag. Every
> >> > umount(8), mount(8) and md5(1) gives a new result:
> >> >
> >>
> >> In adition to previous answers:
> >> http://www.undeadly.org/cgi?action=article&sid=20100404103735
> >
> >
> > The article didn't stress enough how important it is to fsck.
> >
> > Hmmm... I should probably rephrase that, but it's true either way. ;)
>
> that was a great article. thanks for the reference.
>
> running fsck on that stick doesn't show any issues. I ran it twice.
>
> --patrick
Only a small portion of blocks are used for meta data and directories,
so fsck only checks consistency of a small part of a filesystem.
-Otto
