Hi Nick,
Tks for your advice and URL. Finally I figured out the problem coming from one of the RAM sticks. After replacing the questioned stick with another old RAM stick, the old P-II Intel box is now working. Linux LiveCD can start and worked. Ran OBSD 4.1 to start Shell. # disklabel /dev/wd0j # /dev/wd0j: type: ESDI disk: ESDI/IDE disk label: Maxtor 91021U2 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 20010816 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] c: 20010816 0 unused 0 0 # Cyl 0 - 19851 i: 11816721 63 MSDOS # Cyl 0*- 11722 j: 8192961 11816847 MSDOS # Cyl 11723*- 19850 *end* OBSD 4.1 installer found wd0 and started "fdisk." I just stopped there. B.R. Stephen Nick Holland wrote: > > >>> > Old P-II 350 box >>> > IWill motherboard support - ATA-33 HD >>> > Hot Rod ABit ATA-66 PCI Controller >>> > Maxtor HD - ATA-100 10G connected to above Controller >>> > OpenBSD 4.1 CD installer - burned with CD41.iso >> >>> with a dmesg, we would have known all that. >>> AND, we might have believed you. >> >> $ cat /media/disk-1/dmesg.txt > ...[snip mangled dmesg]... >> >> remark: >> 1) the "OpenBSD banner" was not displayed/damaged not because copying on >> to >> the USB pend-drive. > > that wasn't all that was damaged. That whole dmesg was nuked > pretty badly! > >> 2) unable to mount floppy on the P-II Intel box >> # mount /dev/fd0 /mnt >> mount_ffs: /dev/fd0 on /mnt: No such file or directory >> # mount /dev/fd0 /mnt2 >> mount_ffs: /dev/fd0 on /mnt: No such file or directory >> >> Tried several floppy without a solution. > > right. Try using the right floppy drive device. > http://www.openbsd.org/faq/faq4.html#getdmesg > >> 3) During installing OBSD 4.1 on selecting wd0 to install, prompted >> following warnings repeatedly; > > huh????? > You said "disks not found" on the subject line, and yet, you now > say that disks WERE found. > >> chgrp:wd0o:Read-only file system >> chgrp:wd0p:Read-only file system >> .... >> .... >> >> *end* >> >> >> Is the HD having problem? The HD is not empty having a previous OS >> running >> unknown to me. I tried booting it without success. The Controller >> detected >> the HD. > > An alien OS or a strange drive geometry may cause problems with your > system's BIOS. However, in all cases, I've always been able to get > through that problem with native OpenBSD tools on the install disk.. > assuming you can get the machine to boot (it can always choke in the > BIOS and never attempt to boot, of course. OpenBSD can't save you if > the machine won't boot it). > >> The HD which has a OS unknown to me installed was detected by the >> Controller. But I failed to start it just hanging on "Detecting DMI...." >> something like that. >> >> >> Tried to erase the HD without success. >> >> # fdisk /dev/wd0 No such file or directory >> # fdisk /dev/rsd0 No such file or directory >> # fdisk /dev/rd0 No such file or directory > > That error message is very explicit: you are using the wrong > devices. See the FAQ or the man page for proper usage. > > You are providing a lot of conflicting information, some facts, > some interpretation, and we can't tell easily what is what. > Please try again here to let us know EXACTLY what you are doing > and seeing, not what you think is going on. > > Nick. > > > -- View this message in context: http://www.nabble.com/Problem-on-installing-OpenBSD---disks-not-found-tf3692366.html#a10351142 Sent from the openbsd user - misc mailing list archive at Nabble.com.
