Re: rootfs goes full during installation of 5.0.1 on NWS-1460

Thanks for replies.

> Is there any file in /tmp (or other directories) after crash?
> Did you enable logging in the utility menu, for example?
I found nothing in /tmp, and I didn't enable logging.
When the same process is tried with mfs mounted on /tmp and the logging
on, the log says only `installation started' before sysinst quits.
I think what David says is right, and that the problem isn't really  
about
disk full.

Even though I was almost sure that the 9GB disk I used earlier is good  
and
working, I replaced it with another working 1.2GB Quantum drive to see  
if
the situation changes. Not really.

> another possibility is that the NetBSD kernel was
> confused by existing old disklabel on your sd0 disk.
> What "disklabel sd0" on the ramdisk prompt shows?
It's like this:

# /dev/rsd0c:
type: SCSI
disk: FIREBALL_TM1280S
label: fictitious
flags:
bytes/sector: 512
sectors/track: 183
tracks/cylinder: 2
sectors/cylinder: 366
cylinders: 6810
total sectors: 2503872
rpm: 4500
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0		# microseconds
track-to-track seek: 0	# microseconds
drivedata: 0

3 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
  a:   2503872         0     4.2BSD      0     0     0  # (Cyl.      0  
-   6841*)
  c:   2503872         0     unused      0     0        # (Cyl.      0  
-   6841*)
disklabel: boot block size 0
disklabel: super block size 0

I also tried to reset the disklabel and start over:
> # dd if=/dev/zero of=/dev/rsd0c bs=512 count=8192
> sd0: no disk label
> 8192+0 records in
> 8192+0 records out
> 4194304 bytes transferred in 86.090 secs (48719 bytes/sec)
> #
Then reboot and label disk:
...
sd0 at scsibus0 target 0 lun 0: <QUANTUM, FIREBALL_TM1280S, 300L> disk  
fixed
sd0: 1222 MB, 6810 cyl, 2 head, 183 sec, 512 bytes/sect x 2503872  
sectors
sd0: async, 8-bit transfers
...
Terminal type? [vt100]
Erase is backspace.
(I)nstall, (S)hell or (H)alt ? s
# disklabel -i -I sd0
sd0: no disk label
uvm_fault(0x28a810, 0xe1280000, 0x2) -> 0xe
   type 8, code [mmu,,ssw]: 4010715
trap type 8, code = 0x4010715, v = 0xe1280000
kernel program counter = 0x154
pid = 0, lid = 26, pc = 00000154, ps = 2704, sfc = 1, dfc = 1
Registers:
              0        1        2        3        4        5         
6        7
dreg: 00000000 029EB780 00000000 00000000 00002000 003E5600 50000001  
00000000
areg: 000FC4AE 03767000 029F57E0 029EBC80 00297FF0 00000000 00000000  
FFEFFFFC

Kernel stack (000FBF98):
0FBF98: 000C944C 000FC01C 00000080 00000000 00000000 00002000 003E5600  
50000001
0FBFB8: 00000000 029F57E0 029EBC80 00297FF0 00000000 00000000 00000000  
00000001
0FBFD8: 00000000 00000000 00000000 00000001 00000000 00000000 00000008  
00000000
0FBFF8: 00000000 00000000
panic: MMU fault

It seems like a hardware failure? I'll be able to provide the core dumps
in the next weekend.


--
TOMARI, Hisanobu