Re: msdosfs borked

From: Marcel Moolenaar <marcel_at_xcllnt.net>
Date: Wed, 8 Dec 2004 16:17:35 -0800
On Wed, Dec 08, 2004 at 09:48:11AM +0100, Poul-Henning Kamp wrote:
> In message <9EF07AD4-48D0-11D9-BD23-000D93C47836_at_xcllnt.net>, Marcel Moolenaar 
> writes:
> >Permissions seems to have gone out to lunch...
> 
> Hmm, do you know what kind of filesystem it is ?  FAT12/FAT16/FAT32 ?

FAT16:

pluto2# hexdump -C sec0
00000000  eb 3c 90 42 53 44 20 20  34 2e 34 00 02 08 01 00  |.<.BSD  4.4.....|
00000010  02 00 02 00 00 f0 c4 00  3f 00 ff 00 00 00 00 00  |........?.......|
00000020  9a 20 06 00 00 00 29 fe  19 4d 48 4e 4f 20 4e 41  |. ....)..MHNO NA|
00000030  4d 45 20 20 20 20 46 41  54 31 36 20 20 20 fa 31  |ME    FAT16   .1|
00000040  c0 8e d0 bc 00 7c fb 8e  d8 e8 00 00 5e 83 c6 19  |.....|......^...|
00000050  bb 07 00 fc ac 84 c0 74  06 b4 0e cd 10 eb f5 30  |.......t.......0|
00000060  e4 cd 16 cd 19 0d 0a 4e  6f 6e 2d 73 79 73 74 65  |.......Non-syste|
00000070  6d 20 64 69 73 6b 0d 0a  50 72 65 73 73 20 61 6e  |m disk..Press an|
00000080  79 20 6b 65 79 20 74 6f  20 72 65 62 6f 6f 74 0d  |y key to reboot.|
00000090  0a 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000000a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|


This may or may not be related, but I get a bunch of weird output
when booting:

	:
Waiting 2 seconds for SCSI devices to settle
da0 at mpt0 bus 0 target 0 lun 0
da0: <HP 36.4G ST336706LC HP05> Fixed Direct Access SCSI-2 device
da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da0: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C)
kern_symlink  = 0
Trying to mount root from ufs:/dev/da0p2
kernel_vmount = 0
WARNING: preposterous time in filesystem -- CHECK AND RESET THE DATE!
Pre-seeding PRNG: kickstart.
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point kickstart.
swapon: adding /dev/da0p3 as swap device
Starting file system checks:
/dev/da0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/da0p2: clean, 102747 free (587 frags, 12770 blocks, 0.5% fragmentation)
/dev/da0p4: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/da0p4: clean, 322464 free (8664 frags, 39225 blocks, 0.9% fragmentation)
/dev/da0p5: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/da0p5: clean, 114386 free (1186 frags, 14150 blocks, 0.9% fragmentation)
/dev/da0p6: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/da0p6: clean, 126835 free (19 frags, 15852 blocks, 0.0% fragmentation)
/dev/da0p7: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/da0p7: clean, 8100895 free (166671 frags, 991778 blocks, 1.2% fragmentation)
/dev/da0p1: FILESYSTEM CLEAN; SKIPPING CHECKS
Setting hostname: pluto2.freebsd.org.
	:
Dec  9 00:08:17 pluto2 syslogd: kernel boot file is /boot/kernel/kernel
Setting date via ntp.
 9 Dec 00:08:23 ntpdate[278]: step time server 216.136.204.18 offset 0.578687 sec
Starting rpcbind.
	:
Starting mountd.
Dec  9 00:08:23 pluto2 mountd[365]: can't delete exports for /efi: Bad address
Starting nfsd.
	:


The weird messages being:
o  kern_symlink = 0
o  kernel_vmount = 0
o  WARNING: preposterous time in filesystem -- CHECK AND RESET THE DATE!
o  ... mountd[365]: can't delete exports for /efi: Bad address

I don't know what to think of the first two, but the last two shouldn't
be there. And even after a reboot the /efi mount point is without permissions.

I'll sync and rebuild. Maybe I just got a bad mix (kernel & mount)...

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel_at_xcllnt.net
Received on Wed Dec 08 2004 - 23:17:38 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:24 UTC