Subject: Ultra5 installation
To: port-sparc64@netbsd.org <port-sparc64@netbsd.org>
From: Andrea Franceschini <andrea@cs.tin.it>
List: port-sparc64
Date: 11/24/2000 03:56:30
Hi!(sorry for my english)
After the installation of bootstrap code on my ultra5 booted via
network,i lost the partition table and
ability to access to disk.
Any attempt to access the disk generate the following error message:
type: ata tc_bcount: 512 tc_skip: 0
Nov 24 02:50:19 marlboro /netbsd: pciide0:0:0: lost interrupt
Nov 24 02:50:19 marlboro /netbsd: type: ata tc_bcount: 512
tc_skip: 0
pciide0:0:0: lost interrupt
type: ata tc_bcount: 512 tc_skip: 0
wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
Nov 24 02:50:20 marlboro /netbsd: pciide0:0:0: lost interrupt
Nov 24 02:50:20 marlboro /netbsd: type: ata tc_bcount: 512
tc_skip: 0
Nov 24 02:50:20 marlboro /netbsd: wd0c: device timeout reading fsbn 0
(wd0 bn 0;
cn 0 tn 0 sn 0), retrying
type: ata tc_bcount: 512 tc_skip: 0
Nov 24 02:50:30 marlboro /netbsd: pciide0:0:0: lost interrupt
Nov 24 02:50:30 marlboro /netbsd: type: ata tc_bcount: 512
tc_skip: 0
pciide0:0:0: lost interrupt
type: ata tc_bcount: 512 tc_skip: 0
Nov 24 02:50:31 marlboro /netbsd: pciide0:0:0: lost interrupt
Nov 24 02:50:31 marlboro /netbsd: type: ata tc_bcount: 512
tc_skip: 0
pciide0:0:0: lost interrupt
type: ata tc_bcount: 512 tc_skip: 0
Nov 24 02:50:32 marlboro /netbsd: pciide0:0:0: lost interrupt
Nov 24 02:50:32 marlboro /netbsd: type: ata tc_bcount: 512
tc_skip: 0
pciide0:0:0: lost interrupt
type: ata tc_bcount: 512 tc_skip: 0
wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
Nov 24 02:50:33 marlboro /netbsd: pciide0:0:0: lost interrupt
Nov 24 02:50:33 marlboro /netbsd: type: ata tc_bcount: 512
tc_skip: 0
Nov 24 02:50:33 marlboro /netbsd: wd0c: device timeout reading fsbn 0
(wd0 bn 0;
cn 0 tn 0 sn 0), retrying
Now i wonder which is the correct procedure to install bootstrap code.
Using bootinstall in the following way doesn't works:
# bootinstall -n /tar/installation/misc/bootblk wd0a
Is the bootblock file provided with the latest snapshot bogus?
This is my partition table:
# /dev/rwd0c:
type: ESDI
disk: ST39140A
label: Linux custom cyl
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 17660
total sectors: 17801280
rpm: 5400
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg]
a: 2097648 0 4.2BSD 1024 8192 16 # (Cyl. 0 -
2080)
b: 525168 2097648 swap # (Cyl. 2081 -
2601)
c: 17801280 0 unknown # (Cyl. 0 -
17659)
d: 15178464 2622816 4.2BSD 1024 8192 16
Note that before installing boot-block all worked fine.
I successfully initialized the partion and even mounted it under my
nfs-root fs.
Actually the only way to recover the HD is to rewrite the disklabel by
another-OS (e.g. Solaris).
There's another way to clean-up the disklabel? (note that any form of
disklabel fail).
Hope someone can help...
Bye!