Subject: followup Re: loading kernel fails w/ 'read text: Input/output error'
To: None <port-i386@netbsd.org>
From: David Young <dyoung@pobox.com>
List: port-i386
Date: 11/05/2006 03:20:35
Luke found a solution, below. I do not quite understand what the
problem was; a mismatch of disklabel fsize/bsize and the filesystem's
actual parameters?
Dave
----- Forwarded message from Lu-chuan Kung <kung@uiuc.edu> -----
To: cu-wireless-dev@lists.cuwireless.net
From: Lu-chuan Kung <kung@uiuc.edu>
Date: Thu, 2 Nov 2006 22:39:18 +0000 (UTC)
Subject: [CUWiN-Dev] Re: Fail to boot after upgrade
Lu-chuan Kung <kung <at> uiuc.edu> writes:
> 5 partitions:
> # size offset fstype [fsize bsize cpg/sgs]
> a: 62512 32 4.2BSD 0 0 0 # (Cyl. 0*-
> 488*)
> c: 62512 32 unused 0 0 # (Cyl. 0*-
> 488*)
> d: 125056 0 unused 0 0 # (Cyl. 0 -
976)
> e: 62512 62544 4.2BSD 1024 8192 7816 # (Cyl. 488*-
976)
> [snap]
> I noticed that in the output of disklabel. The number of total sectors of
BIOS
> disk geometry is negative. However, the individual parameters
(Cyl,Head,S/Cyl)
> seem to be correct and thus I couldn't fix it in disklabel.
>
> And by the way, why do we need disk geometry when using "/sbin/upgrade"? I
> didn't notice anything related to disk geometry in the source of the script.
>
> Luke
>
Hi Dave,
I actually solved the problem by myself and want to share this information
here. The problem is actually caused by wrong block-size and fragment-size
setting on /dev/wd0e. I changed the line that executes newfs in /sbin/upgrade
to:
newfs -b 4096 -f 512
and then everything works.
Luke
_______________________________________________
CU-Wireless-Dev mailing list
CU-Wireless-Dev@lists.cuwireless.net
http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-dev
----- End forwarded message -----
--
David Young OJC Technologies
dyoung@ojctech.com Urbana, IL * (217) 278-3933