Date: Sat, 29 Aug 1998 11:14:23 +1000 From: Robert Chalmers <robert@chalmers.com.au> To: freebsd-fs@FreeBSD.ORG Subject: Strange event with filesystem. Cant make Quantum Fireball 3.2 boot? Message-ID: <35E755EF.53BD3DC@chalmers.com.au>
next in thread | raw e-mail | index | archive | help
This is a strange event. I have this Qunatum Fireball SE3.2S SCSI drive. I have this Adaptec-AHA1540CF/1542CF (SCSI 2) controller. I can set the HDD up using disklabel, and and it works fine as a secondary drive. Three or so filesystems, sd2a/b/c/e/f etc. I can now set it up with disklabel -e, using a disktab, or just editing it with -e. I can do a disklable -B -b boot1 -s boot2 sd2, and it appears to take that fine. So in other words, creating filesystems using disklabel appears to work fine. Except that matter what I do, that sucker will not boot.!! It works fine as a secondary drive, the third drive actually, but if I plug it back in as the primary drive - nada! So, taking the bull by the horns, I thought - ok, lets do this the old-fashioned way. Let's play at being a beginner. Disconnect all other drives, and set up the Quantum as the ONLY HDD in the system. Boot from the 2.2SNAP floppy, CD in place, and fingers crossed. Select Beginner install. Set up the fdisk options, slices, and press Q - no sign of activity, then 'panic i/o error, rebooting'. In other words... It appears that nothing can be written to, or read from the bootsector? Now, is this a bodgie drive ??? (brand new) An incompatible card (it works ok if the drive is secondary) or something that needs setting in the Adaptec configuration that I'm missing. It is pretty simple, but thats no indication. Does anyone have any experience with Quantum Fireball SE 3.2S drives and this problem? Thanks Robert -- Support Whirled Peas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35E755EF.53BD3DC>