Subject: Re: Indy harddisk problems
To: Hubert Feyrer <hubert.feyrer@informatik.fh-regensburg.de>
From: Hendrik Scholz <hscholz@perikles.toppoint.de>
List: port-sgimips
Date: 10/26/2001 12:15:25
Hi!
On Fri, 26 Oct 2001 02:08:23 +0200 (MEST)
Hubert Feyrer <hubert.feyrer@informatik.fh-regensburg.de> wrote:
[...]
> This looks vaguely familiar... *dig*
> Using the latest snapshot from ftp.netbsd.org, unpacking michael's
> sgiboot.tgz in /sys/arch/sgimips, and building "boot" and "sgivol" and
> installing and booting it works for me... Can you try the bootloader at
> www.feyrer.de/Misc/sgiboot and let us know if it does something different?
I'm using the latest snapshot (10/02/2001 iirc) and a custom kernel to
support scsi.
Here is the output of sgivol sd0 after another sgivol -i sd0:
root@phobos:/usr/src/sys/arch/sgimips/stand > ./sgivol/sgivol sd0
disklabel shows 4228848 sectors
checksum: 00000000
root part: 0
swap part: 1
bootfile:
Volume header files:
SGI partitions:
0:a blocks 4225713 first 3135 type 7 (EFS)
8:i blocks 3135 first 0 type 0 (Volume Header)
10:k blocks 4228848 first 0 type 6 (Volume)
root@phobos:/usr/src/sys/arch/sgimips/stand >
Writing the boot loader:
root@phobos:/usr/src/sys/arch/sgimips/stand > ./sgivol/sgivol -w boot boot/boot sd0
Writing file boot/boot
File boot/boot has 256131 bytes
disklabel shows 4228848 sectors
checksum: 00000000
root part: 0
swap part: 1
bootfile:
Volume header files:
boot offset 2 blocks, length 256131 bytes (501 blocks)
SGI partitions:
0:a blocks 4225713 first 3135 type 7 (EFS)
8:i blocks 3135 first 0 type 0 (Volume Header)
10:k blocks 4228848 first 0 type 6 (Volume)
Do you want to update volume (y/n)? y
root@phobos:/usr/src/sys/arch/sgimips/stand > ./sgivol/sgivol -r boot /tmp/boot sd0
Reading file boot
root@phobos:/usr/src/sys/arch/sgimips/stand > diff /tmp/boot boot/boot
root@phobos:/usr/src/sys/arch/sgimips/stand >
Booting the SGI:
>> boot
NetBSD/sgimips 1.5Y Bootstrap, Revision 1.0
(hscholz@phobos, Fri Oct 26 05:04:11 UTC 2001)
Mem block: type 0 base 0x0 size 0x1000
Mem block: type 1 base 0x1000 size 0x1000
Mem block: type 3 base 0x8002000 size 0x73e000
Mem block: type 6 base 0x8740000 size 0xc0000
Mem block: type 3 base 0x8800000 size 0x800000
Mem block: type 5 base 0x9000000 size 0xc000
Mem block: type 3 base 0x900c000 size 0xaff4000
Local storage 887fe168
argv[0]: scsi(0)disk(4)rdisk(0)partition(8)/boot
argv[1]: ConsoleIn=serial(0)
argv[2]: ConsoleOut=serial(0)
argv[3]: SystemPartition=scsi(0)disk(4)rdisk(0)partition(8)
argv[4]: OSLoader=boot
argv[5]: OSLoadPartition=scsi(0)disk(4)rdisk(0)partition(0)
argv[6]: OSLoadFilename=/netbsd
Boot: scsi(0)disk(4)rdisk(0)partition(0)/netbsd
devopen: scsi(0)disk(4)rdisk(0)partition(0) type scsi file /netbsd
diskopen: 0,2,0 scsi(0)disk(4)rdisk(0)partition(0)
open scsi(0)disk(4)rdisk(0)partition(0)/netbsd: No such file or directory
Boot failed! Halting...
>> hinv
System: IP22
Processor: 200 Mhz R4400, with FPU
Primary I-cache size: 16 Kbytes
Primary D-cache size: 16 Kbytes
Secondary cache size: 1024 Kbytes
Memory size: 192 Mbytes
Graphics: Indy 24-bit
SCSI Disk: scsi(0)disk(4)
Audio: Iris Audio Processor: version A2 revision 4.1.0
>> version
PROM Monitor SGI Version 5.3 Rev B7 R4X00 IP24 Feb 16, 1995 (BE)
>>
I'm not sure if my partition settings in OSLoadPartition and SystemPartition
are correct. Here is the disklabel sd0 output:
# disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SEAGATE ST32430
label: mydisk
flags:
bytes/sector: 512
sectors/track: 117
tracks/cylinder: 9
sectors/cylinder: 1053
cylinders: 4016
total sectors: 4228848
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 3276800 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 3111*)
b: 262144 3276800 swap # (Cyl. 3111*- 3360*)
c: 4196720 0 unknown # (Cyl. 0 - 3985*)
d: 102400 3538944 4.2BSD 0 0 0 # (Cyl. 3360*- 3458*)
e: 587504 3641344 4.2BSD 0 0 0 # (Cyl. 3458*- 4015)
#
I just figured out that my sd0a is corrupt.
I was running fsck and now test if the boot loader and sd0a make trouble:
Extracting the sgiboot bootloader and using diff it shows that there are
differences between the installed loader and the loader on the disk.
Maybe my disk setup is wrong so there are overlapping areas overwriting
each other.
Do I need to reserve any special diskspace for the boot loader or is my
setup shown above usable ?
Thanks a lot, Hendrik
--
Hendrik Scholz <hendrik@scholz.net>
http://www.toppoint.de/~hscholz/
Where do you want to be tomorrow ?