mjm@foster.avid.oz.au (Mike McBain) (02/12/91)
I am having considerable difficulty adding a second hard disk to my
ISC 2.0.2 installation. I hope someone has some experience which can
help me.
Setup:
Micronics 486-25, 4MB memory.
Hard disk: Primary WD APXXXX (209MB), IDE controller
Secondary: Maxtor XT4380S, Future Domain TMC8XX controller
Tseng Labs VGA+ card and Nec 4D Multisync.
The kernel has been modified using kconfig so that it knows there
is a SCSI controller in the system. The system boots normally off
the IDE drive. I have once or twice seen a message which says
tmc_init: no drives online
The Maxtor has been formatted under DOS. If the machine
is booted with DOS from the floppy drive, the Maxtor is accessible as drive C,
which tells me that it's electrically (and logically?) correctly installed.
However, when I try to add the Maxtor on its controller using the addharddisk
option under sysadm, I notice a few things:
1. I select the format disk option having indicated the drive is drive
0 on controller 1. It returns very quickly, and does not format
the disk.
2. My reading of the config files indicates that the minor number for
the drive under these conditions should be 64. This seems sometimes
to be OK, in that the /dev/dsk/c1d0s0 numbers have at times been 0, 64.
I could do a mknod by hand, of course. However, should the second controller
have a major number of 0? At the moment I'm letting addharddisk do all
the work. Manual mknod with 0, 64-70 as the major and minor numbers
for the c1d0s0-6 devices and 0, 192-6 for the c1d0p0-4 devices didn't get me
anywhere.
3. Since it doesn't format the drive at all, it doesn't have a lot of success
with mkfs and fdisk either.
I haven't put an entry into BIOS about this controller, since it's a SCSI one.
What else should I have tried? I have an Adaptec 1542B available to try if
that is likely to be better, but why doesn't it work as things are now? Anyone
seen this problem and solved it?
Mike McBain
--
Mike McBain | DOMAIN: mjm@foster.avid.oz.au
Avid Systems Pty Ltd | UUCP: {pyramid,uunet}!munnari!foster.avid.oz.au!mjm
St Kilda, Australia 3182| Tel: +61 3 534 2293
---- Is it possible to knit during a space walk? ----brando@uicsl.csl.uiuc.edu (Brandon Brown) (02/12/91)
mjm@foster.avid.oz.au (Mike McBain) writes: >Micronics 486-25, 4MB memory. >Hard disk: Primary WD APXXXX (209MB), IDE controller > Secondary: Maxtor XT4380S, Future Domain TMC8XX controller >Tseng Labs VGA+ card and Nec 4D Multisync. >The Maxtor has been formatted under DOS. If the machine >is booted with DOS from the floppy drive, the Maxtor is accessible as drive C, >which tells me that it's electrically (and logically?) correctly installed. Hold the phone.... The Maxtor on the secondary controller (SCSI) is being recognized as C: ??? Shouldn't the IDE controller's first drive be required to have a C: partition? It sounds like to me preliminarily that the IDE controller is not setup correctly... >However, when I try to add the Maxtor on its controller using the addharddisk >option under sysadm, I notice a few things: >1. I select the format disk option having indicated the drive is drive > 0 on controller 1. It returns very quickly, and does not format > the disk. I have noticed on a couple of my drives that this happens also. I think some manufactures preformat their drives and figure that you won't need to re-format them. I have a drive that works fine and returns immediately from a format with no errors... >I haven't put an entry into BIOS about this controller, since it's a SCSI one. >What else should I have tried? I have an Adaptec 1542B available to try if >that is likely to be better, but why doesn't it work as things are now? Anyone >seen this problem and solved it? Well, speaking from experience, if you try to use a primary "AT" style controller with an Adaptec secondary controller with ISC 2.0.2, it won't work. I had the exact same problem before I upgraded to ISCv 2.2. Good luck, Mike.. +-----------------------------------------------------------------------------+ | Brandon Brown | Internet: brando@uicsl.csl.uiuc.edu | | Coordinated Science Laboratory | UUCP: uiucuxc!addamax!brando!brown | | University of Illinois | CompuServe: 73040,447 | | Urbana, IL 61801 | GEnie: xmg23356, macbrando | +-----------------------------------------------------------------------------+
chris@endgame.gsfc.nasa.gov (Chris Shenton) (02/13/91)
In article <1991Feb12.150008.3737@ux1.cso.uiuc.edu> brando@uicsl.csl.uiuc.edu (Brandon Brown) writes:
Well, speaking from experience, if you try to use a primary "AT" style
controller with an Adaptec secondary controller with ISC 2.0.2, it won't
work. I had the exact same problem before I upgraded to ISCv 2.2.
Arrrrg. I've got ISC 2.0.2 with a WD AT style controller, and I've been
thinking of getting a SCSI controller and big Conner disk. You're saying
this won't work?
What if I make the SCSI primary, and the AT secondary?
--
chris@asylum.gsfc.nasa.gov, ...!uunet!asylum.gsfc.nasa.gov!chris, PITCH::CHRISrfarris@rfengr.com (Rick Farris) (02/13/91)
In article <CHRIS.91Feb12151909@endgame.gsfc.nasa.gov> chris@endgame.gsfc.nasa.gov (Chris Shenton) writes: > I've been thinking of getting a SCSI controller and big > Conner disk... Has Conner begun making big disks? Great! All I've seen are the 200 MB jobbies and they are very reliable and reasonably priced. I would love to see a *big* Conner disk. What is it? A GB drive in a 3.5" 1/2 ht form-factor? $1500? -- Rick Farris RF Engineering POB M Del Mar, CA 92014 voice (619) 259-6793 rfarris@rfengr.com ...!ucsd!serene!rfarris serenity bbs 259-7757
alexb@cfctech.cfc.com (Alex Beylin) (02/14/91)
In article <CHRIS.91Feb12151909@endgame.gsfc.nasa.gov> chris@endgame.gsfc.nasa.gov (Chris Shenton) writes: >In article <1991Feb12.150008.3737@ux1.cso.uiuc.edu> brando@uicsl.csl.uiuc.edu (Brandon Brown) writes: > >Arrrrg. I've got ISC 2.0.2 with a WD AT style controller, and I've been >thinking of getting a SCSI controller and big Conner disk. You're saying >this won't work? > >What if I make the SCSI primary, and the AT secondary? >-- >chris@asylum.gsfc.nasa.gov, ...!uunet!asylum.gsfc.nasa.gov!chris, PITCH::CHRIS That won't work even with ISC 2.2. As specified in the manual (and tried), MFM must be the primary controller. There is a possibility of adding the MFM controller after the system is loaded, but no-one that I know of have tried that yet. -- Alex Beylin alexb@cfctech.cfc.com
larry@nstar.rn.com (Larry Snyder) (02/14/91)
alexb@cfctech.cfc.com (Alex Beylin) writes: >That won't work even with ISC 2.2. As specified in the manual (and tried), >MFM must be the primary controller. There is a possibility of adding >the MFM controller after the system is loaded, but no-one that I know of have >tried that yet. we at one time were booting off a 1542A (SCSI) and had a 2372B (RLL) installed as the secondary controller (secondary addressing, secondary interrupts - and floppy controller disabled by cutting traces). We had to change some of the addressing in /etc/conf/sdevices.d to match what we had done - but it is possible with a little work (we did this only once with 2.02 about 14 months ago).. -- Larry Snyder, NSTAR Public Access Unix 219-289-0287 (HST/PEP/V.32/v.42bis) regional UUCP mapping coordinator {larry@nstar.rn.com, ..!uunet!nstar!larry, larry%nstar@iuva
paulg@hparc0.HP.COM (Paul Gillingwater) (02/15/91)
>/ hparc0:comp.unix.sysv386 / chris@endgame.gsfc.nasa.gov (Chris Shenton) / 7:19 am Feb 13, 1991 / >>In article <1991Feb12.150008.3737@ux1.cso.uiuc.edu> brando@uicsl.csl.uiuc.edu (Brandon Brown) writes: >>Well, speaking from experience, if you try to use a primary "AT" style >>controller with an Adaptec secondary controller with ISC 2.0.2, it won't >>work. I had the exact same problem before I upgraded to ISCv 2.2. >Arrrrg. I've got ISC 2.0.2 with a WD AT style controller, and I've been >thinking of getting a SCSI controller and big Conner disk. You're saying >this won't work? I have ISC 2.02, and have successfully installed an ESDI controller as the primary (boot) controller, and the Adaptec 1542A SCSI controller as secondary, with two drives and tape.
nvk@ddsw1.MCS.COM (Norman Kohn) (02/17/91)
In article <1991Feb12.150008.3737@ux1.cso.uiuc.edu> brando@uicsl.csl.uiuc.edu (Brandon Brown) writes: >Well, speaking from experience, if you try to use a primary "AT" style >controller with an Adaptec secondary controller with ISC 2.0.2, it won't >work. I had the exact same problem before I upgraded to ISCv 2.2. Seems to work for me (Adaptec RLL controller primary, Adaptec SCSI secondary) -- Norman Kohn | ...ddsw1!nvk Chicago, Il. | days/ans svc: (312) 650-6840 | eves: (312) 373-0564
fortin@zap.uucp (Denis Fortin) (02/17/91)
In <1991Feb16.185144.29485@ddsw1.MCS.COM> nvk@ddsw1.MCS.COM (Norman Kohn) writes: >In article <1991Feb12.150008.3737@ux1.cso.uiuc.edu> brando@uicsl.csl.uiuc.edu (Brandon Brown) writes: >>Well, speaking from experience, if you try to use a primary "AT" style >>controller with an Adaptec secondary controller with ISC 2.0.2, it won't >>work. I had the exact same problem before I upgraded to ISCv 2.2. >Seems to work for me (Adaptec RLL controller primary, Adaptec SCSI secondary) zap is running with an old MFM "AT-style" controller as the primary (with a 70MB Micropolis disk), and an Adaptec AHA-1542B SCSI controller as the secondary (with a 345MB Micropolis disk). It worked like a charm, I just plugged everything in and voila`! No interrupt conflicts, no funny software problems, just six times the amount of disk space I had before :-) :-) -- Denis Fortin, DMR Group Inc, (514) 877-3301 (All of these opinions are my own) fortin@zap.uucp uunet!sobeco!zap!fortin fortin%zap@larry.mcrcim.mcgill.edu
gws@n8emr.uucp (Gary Sanders) (02/18/91)
In article <3440010@hparc0.HP.COM> paulg@hparc0.HP.COM (Paul Gillingwater) writes: >>/ hparc0:comp.unix.sysv386 / chris@endgame.gsfc.nasa.gov (Chris Shenton) / 7:19 am Feb 13, 1991 / >>>In article <1991Feb12.150008.3737@ux1.cso.uiuc.edu> brando@uicsl.csl.uiuc.edu (Brandon Brown) writes: > > >>Well, speaking from experience, if you try to use a primary "AT" style > >>controller with an Adaptec secondary controller with ISC 2.0.2, it won't > >>work. I had the exact same problem before I upgraded to ISCv 2.2. > MY primary controllers is a WD1007 with a couple of 160mb drives and two floppys hanging off of it. I would like to add a second controller, (mfm or rll) Will this work? Any specific requirments needed by the controller for this to work. > >I have ISC 2.02, and have successfully installed an ESDI controller >as the primary (boot) controller, and the Adaptec 1542A SCSI controller >as secondary, with two drives and tape. -- Gary W. Sanders (gws@n8emr or ...!osu-cis!n8emr!gws), 72277,1325 N8EMR @ W8CQK (ip addr) 44.70.0.1 [Ohio AMPR address coordinator] HAM BBS (1200/2400/9600/V.32/PEP/MNP=L5) 614-895-2553 Voice: 614-895-2552 (eves/weekends)
randy@chinet.chi.il.us (Randy Suess) (02/18/91)
In article <1991Feb17.164248.7856@n8emr.uucp> gws@n8emr.uucp (Gary Sanders) writes: > MY primary controllers is a WD1007 with a couple of >160mb drives and two floppys hanging off of it. I would like to >add a second controller, (mfm or rll) Will this work? Any specific >requirments needed by the controller for this to work. > Yes, no problem whatsoever. The ISC docs cover it completely. You just need another controller with configurable i/o port and interrupt jumpers. And no floppy controller. I have an Adaptec ESDI controller with 2 158 meg drives and a WD RLL controller with 2 110 meg drives. Works like a champ. -- Randy Suess randy@chinet.chi.il.us
tmh@prosun.first.gmd.de (Thomas Hoberg) (03/06/91)
I really didn't want to post this one, 'cause it's sooo long, but all my mail to Mike McBain bounced.... -- In article <1991Feb12.065726.5497@foster.avid.oz.au> you write: |> I am having considerable difficulty adding a second hard disk to my |> ISC 2.0.2 installation. I hope someone has some experience which can |> help me. |> |> Setup: |> |> Micronics 486-25, 4MB memory. |> Hard disk: Primary WD APXXXX (209MB), IDE controller |> Secondary: Maxtor XT4380S, Future Domain TMC8XX controller |> Tseng Labs VGA+ card and Nec 4D Multisync. |> |> The kernel has been modified using kconfig so that it knows there |> is a SCSI controller in the system. The system boots normally off |> the IDE drive. This sounds like the IDE drive is considered the first physical drive (as I would expect). |> I have once or twice seen a message which says |> tmc_init: no drives online |> |> The Maxtor has been formatted under DOS. If the machine |> is booted with DOS from the floppy drive, the Maxtor is accessible as drive C, |> which tells me that it's electrically (and logically?) correctly installed. What this tells me, is that the two controllers can't agree on who should be first. Drive C is usally used for the first physical drive, which should be the IDE. I don't know what happens, if there is no DOS partition on the first drive. If there is a DOS partition on the IDE drive, this means that the Future Domain and the IDE don't get along. |> |> However, when I try to add the Maxtor on its controller using the addharddisk |> option under sysadm, I notice a few things: |> |> 1. I select the format disk option having indicated the drive is drive |> 0 on controller 1. It returns very quickly, and does not format |> the disk. You might have formatted the IDE drive instead--be glad! |> 2. My reading of the config files indicates that the minor number for |> the drive under these conditions should be 64. This seems sometimes |> to be OK, in that the /dev/dsk/c1d0s0 numbers have at times been 0, 64. |> I could do a mknod by hand, of course. However, should the second controller |> have a major number of 0? YES |> At the moment I'm letting addharddisk do all |> the work. Manual mknod with 0, 64-70 as the major and minor numbers |> for the c1d0s0-6 devices and 0, 192-6 for the c1d0p0-4 devices didn't get me |> anywhere. c1d0s0 will point nowwhere, if the VTOC isn't initialized correctly, see below. |> 3. Since it doesn't format the drive at all, it doesn't have a lot of success |> with mkfs and fdisk either. |> |> I haven't put an entry into BIOS about this controller, since it's a SCSI one. |> What else should I have tried? I have an Adaptec 1542B available to try if |> that is likely to be better, but why doesn't it work as things are now? Anyone |> seen this problem and solved it? I think the Adaptec 1542B is a better choice anyway, and why not use it when you have it? I have tried MFM/RLL/ESDI drives as primaries and Adaptec SCSI as secondary controllers without any problems. Since SCSI drives tend to be faster than MFM/RLL/ESDI (though not necessarily IDE and perhaps not 20Mbit ESDI) it would really be interesting to have the SCSI as primary drives. It should be possible to jumper the non-SCSI controller to the secondary address (0x17f and IRQ 15) and hand patch it into the kernel (kconfig doesn't support that combination directly). The non-SCSI drives would be lost for DOS, though. Doing mknod is only doing half the job. I don't trust 'addharddisk' all that much and I don't like having to format the second hard disk (especially when it's a SCSI disk, that doesn't like to be formatted). I have had my first disk wiped out several times and doing a re-install for the first hard disk is bad enough. But addharddisk want's to destroy the second disk, when there is no need for doing that. For Unix to be able to access the second disk's partitions it needs a correct VTOC (volume table of contents) on the *second* disk which also describes the physical characteristics of the device. There are some *really* messy IOCTL's to do that, but there is also the rather cryptic program 'mkpart'. The VTOC and the 'partition stanzas' are usually put on the disks via 'mkpart' during formatting. They can also be put there by hand using 'mkpart -b'. '/etc/partitions' has to be edited to include the pysical characteristics of the second drive. On one of my machines this currently looks like this: (ESDI primary, RLL secondary) disk0: heads = 8, cyls = 966, sectors = 34, bpsec = 512, physheads = 8, physcyls = 969, physsectors = 35, physbpsec = 512, vtocsec = 29, altsec = 30, boot = "/etc/boot", device = "/dev/rdsk/0p0" root: partition = 1, start = 172720, size = 89760, tag = ROOT, perm = REMAP, perm = VALID swap0: partition = 2, start = 152864, size = 19856, tag = SWAP, perm = NOMOUNT, perm = REMAP, perm = VALID reserved0: partition = 8, start = 152320, size = 34, tag = BOOT, perm = NOMOUNT, perm = VALID alts0: partition = 9, start = 152592, size = 272, tag = ALTSCTR, perm = NOMOUNT, perm = VALID disk10: heads = 9, cyls = 925, sectors = 26, bpsec = 512, physheads = 9, physcyls = 925, physsectors = 35, physbpsec = 512, vtocsec = 29, altsec = 30, boot = "/etc/boot", device = "/dev/rdsk/c1d0p0", badsec = ( 11376, 72473, 78901, 97592, 114017, 119107, 137021, 140121, 140791, 156145, 170162, 190651, 190803, 195297, 203714, 206391, 209220, 211209) local10: partition = 2, start = 468, size = 215748, tag = USR, perm = REMAP, perm = VALID rsrvd10: partition = 8, start = 234, size = 34, tag = BOOT, perm = NOMOUNT, perm = VALID alts10: partition = 9, start = 286, size = 182, tag = ALTS, perm = NOMOUNT, perm = VALID |> |> Mike McBain |> -- |> Mike McBain | DOMAIN: mjm@foster.avid.oz.au |> Avid Systems Pty Ltd | UUCP: {pyramid,uunet}!munnari!foster.avid.oz.au!mjm |> St Kilda, Australia 3182| Tel: +61 3 534 2293 |> ---- Is it possible to knit during a space walk? ---- Hope this helps somewhere... :-> tom ---- Thomas M. Hoberg | UUCP: tmh@bigfoot.first.gmd.de or tmh%gmdtub@tub.UUCP c/o GMD Berlin | ...!unido!tub!gmdtub!tmh (Europe) or D-1000 Berlin 12 | ...!unido!tub!tmh Hardenbergplatz 2 | ...!pyramid!tub!tmh (World) Germany | BITNET: tmh%DB0TUI6.BITNET@DB0TUI11 or +49-30-254 99 160 | tmh@tub.BITNET