This is a discussion on Seagate Format.dat Information? within the Sun Solaris Hardware forums, part of the Solaris Operating System category; --> Any ideas where can I find information to generate an entry in the /etc/format.dat for a Segate ST118202LC drive ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Any ideas where can I find information to generate an entry in the /etc/format.dat for a Segate ST118202LC drive (Is it even compatible with???) running on a Sun 630MP w/Solaris 2.5.1? I found a couple of the older Cheetah 10K 18gb drives and want to try to use them on my old Sparc system. I checked the Seagate web page and I could not find any of the information I need. Thanks, Mike |
| |||
| In article <e60d72ed.0405252355.349202b6@posting.google.com >, msargent100@hotmail.com (Mike) writes: > Any ideas where can I find information to generate an entry in the > /etc/format.dat for a Segate ST118202LC drive (Is it even compatible > with???) running on a Sun 630MP w/Solaris 2.5.1? > > I found a couple of the older Cheetah 10K 18gb drives and want to try > to use them on my old Sparc system. > > I checked the Seagate web page and I could not find any of the > information I need. > > > Thanks, > Mike You dont need format.dat. Start format, select the disk and say yes to auto-label. I think that Solaris 2.5.1 supports only <= 2GB UFS partitions, so you should prefer Solaris 2.6. -- Michael Tosch IT Specialist HP Managed Services Germany Phone +49 2407 575 313 Mail: michael.tosch:hp.com |
| |||
| msargent100@hotmail.com (Mike) writes: >Any ideas where can I find information to generate an entry in the >/etc/format.dat for a Segate ST118202LC drive (Is it even compatible >with???) running on a Sun 630MP w/Solaris 2.5.1? >I found a couple of the older Cheetah 10K 18gb drives and want to try >to use them on my old Sparc system. >I checked the Seagate web page and I could not find any of the >information I need. You really don't need format.dat for SCSI drives, not even for Solaris 2.5.1. Casper |
| |||
| Thanks all you were right - no format.dat needed. Just a boot -r at least to see the drive. Now the problem is that the system will just randomly drop to the OK prompt with no fore warning! Just bang the system stops responding to my telnet connection (happens with direct console login also). When I look at the console window I see a "Type go to resume" message and the OK prompt. Sometimes typing "go" the system will respond and continue, but it is usually dead and needs a power cycle. On the internal scsi bus I have an old Sun cdrom OEM type so it is probably a speedy 2x or something like that (but hey it works!). And 2 of the 18.2GB lvd drives. Nothing external and I have a terminator on the extra connector. The only jumpers I have set on the drives are to set the SCSI id ( 1 & 2 ). I had heard that the most the system would support was 26gb total but that sounded a little bogus so I tried anyway. Could this flakey operation be a result of exceeding the max capacity of the host adapter? Or mixing lvd and non-lvd (cdrom) on the same scsi bus cable? Is it a SE jumper setting issue? Or ??? I also have a couple older 9gb drives would it be easier to just fall back to those? Any help would be gratelty appreciated! Thanks, Mike msargent100@hotmail.com (Mike) wrote in message news:<e60d72ed.0405252355.349202b6@posting.google. com>... > Any ideas where can I find information to generate an entry in the > /etc/format.dat for a Segate ST118202LC drive (Is it even compatible > with???) running on a Sun 630MP w/Solaris 2.5.1? > > I found a couple of the older Cheetah 10K 18gb drives and want to try > to use them on my old Sparc system. > > I checked the Seagate web page and I could not find any of the > information I need. > > > Thanks, > Mike |
| |||
| Mike wrote: > Thanks all you were right - no format.dat needed. Just a boot -r at > least to see the drive. > > Now the problem is that the system will just randomly drop to the OK > prompt with no fore warning! Just bang the system stops responding to > my telnet connection (happens with direct console login also). When I > look at the console window I see a "Type go to resume" message and the > OK prompt. Sometimes typing "go" the system will respond and continue, > but it is usually dead and needs a power cycle. Are you sure there's nothing in the log files? > > On the internal scsi bus I have an old Sun cdrom OEM type so it is > probably a speedy 2x or something like that (but hey it works!). And 2 > of the 18.2GB lvd drives. Nothing external and I have a terminator on > the extra connector. > > The only jumpers I have set on the drives are to set the SCSI id ( 1 & > 2 ). > > I had heard that the most the system would support was 26gb total but > that sounded a little bogus so I tried anyway. > > Could this flakey operation be a result of exceeding the max capacity > of the host adapter? Or mixing lvd and non-lvd (cdrom) on the same > scsi bus cable? Is it a SE jumper setting issue? Or ??? > > I also have a couple older 9gb drives would it be easier to just fall > back to those? > > Any help would be gratelty appreciated! > > > Thanks, > Mike > > > msargent100@hotmail.com (Mike) wrote in message news:<e60d72ed.0405252355.349202b6@posting.google. com>... > >>Any ideas where can I find information to generate an entry in the >>/etc/format.dat for a Segate ST118202LC drive (Is it even compatible >>with???) running on a Sun 630MP w/Solaris 2.5.1? >> >>I found a couple of the older Cheetah 10K 18gb drives and want to try >>to use them on my old Sparc system. >> >>I checked the Seagate web page and I could not find any of the >>information I need. >> >> >>Thanks, >> Mike -- The e-mail address in our reply-to line is reversed in an attempt to minimize spam. Our true address is of the form che...@prodigy.net. |
| |||
| OK in /var/adm/messages I see several of the following type entries: Connected command timeout for Target 1.0 Target 1.0 reducing sync. transfer rate SCSI transport failed: reason 'reset': retrying And several other WARNING messages pointing to sd1 Ideas??? CJT <abujlehc@prodigy.net> wrote in message news:<40C1EE8D.8050101@prodigy.net>... > Mike wrote: > > > Thanks all you were right - no format.dat needed. Just a boot -r at > > least to see the drive. > > > > Now the problem is that the system will just randomly drop to the OK > > prompt with no fore warning! Just bang the system stops responding to > > my telnet connection (happens with direct console login also). When I > > look at the console window I see a "Type go to resume" message and the > > OK prompt. Sometimes typing "go" the system will respond and continue, > > but it is usually dead and needs a power cycle. > > Are you sure there's nothing in the log files? > > > > > On the internal scsi bus I have an old Sun cdrom OEM type so it is > > probably a speedy 2x or something like that (but hey it works!). And 2 > > of the 18.2GB lvd drives. Nothing external and I have a terminator on > > the extra connector. > > > > The only jumpers I have set on the drives are to set the SCSI id ( 1 & > > 2 ). > > > > I had heard that the most the system would support was 26gb total but > > that sounded a little bogus so I tried anyway. > > > > Could this flakey operation be a result of exceeding the max capacity > > of the host adapter? Or mixing lvd and non-lvd (cdrom) on the same > > scsi bus cable? Is it a SE jumper setting issue? Or ??? > > > > I also have a couple older 9gb drives would it be easier to just fall > > back to those? > > > > Any help would be gratelty appreciated! > > > > > > Thanks, > > Mike > > > > > > msargent100@hotmail.com (Mike) wrote in message news:<e60d72ed.0405252355.349202b6@posting.google. com>... > > > >>Any ideas where can I find information to generate an entry in the > >>/etc/format.dat for a Segate ST118202LC drive (Is it even compatible > >>with???) running on a Sun 630MP w/Solaris 2.5.1? > >> > >>I found a couple of the older Cheetah 10K 18gb drives and want to try > >>to use them on my old Sparc system. > >> > >>I checked the Seagate web page and I could not find any of the > >>information I need. > >> > >> > >>Thanks, > >> Mike |
| |||
| After a little more research on Sun.com I found a couple settings to try in /etc/system: set scsi_options=0x58 set scsi_reset_delay=10000 Also after reading a bit more I was curious if I should set the jumper on the drives to force single-ended mode for both drives. Recommendations? msargent100@hotmail.com (Mike) wrote in message news:<e60d72ed.0406060357.43b1c7b0@posting.google. com>... > OK in /var/adm/messages I see several of the following type entries: > > Connected command timeout for Target 1.0 > Target 1.0 reducing sync. transfer rate > SCSI transport failed: reason 'reset': retrying > > And several other WARNING messages pointing to sd1 > > > Ideas??? > > > CJT <abujlehc@prodigy.net> wrote in message news:<40C1EE8D.8050101@prodigy.net>... > > Mike wrote: > > > > > Thanks all you were right - no format.dat needed. Just a boot -r at > > > least to see the drive. > > > > > > Now the problem is that the system will just randomly drop to the OK > > > prompt with no fore warning! Just bang the system stops responding to > > > my telnet connection (happens with direct console login also). When I > > > look at the console window I see a "Type go to resume" message and the > > > OK prompt. Sometimes typing "go" the system will respond and continue, > > > but it is usually dead and needs a power cycle. > > > > Are you sure there's nothing in the log files? > > > > > > > > On the internal scsi bus I have an old Sun cdrom OEM type so it is > > > probably a speedy 2x or something like that (but hey it works!). And 2 > > > of the 18.2GB lvd drives. Nothing external and I have a terminator on > > > the extra connector. > > > > > > The only jumpers I have set on the drives are to set the SCSI id ( 1 & > > > 2 ). > > > > > > I had heard that the most the system would support was 26gb total but > > > that sounded a little bogus so I tried anyway. > > > > > > Could this flakey operation be a result of exceeding the max capacity > > > of the host adapter? Or mixing lvd and non-lvd (cdrom) on the same > > > scsi bus cable? Is it a SE jumper setting issue? Or ??? > > > > > > I also have a couple older 9gb drives would it be easier to just fall > > > back to those? > > > > > > Any help would be gratelty appreciated! > > > > > > > > > Thanks, > > > Mike > > > > > > > > > msargent100@hotmail.com (Mike) wrote in message news:<e60d72ed.0405252355.349202b6@posting.google. com>... > > > > > >>Any ideas where can I find information to generate an entry in the > > >>/etc/format.dat for a Segate ST118202LC drive (Is it even compatible > > >>with???) running on a Sun 630MP w/Solaris 2.5.1? > > >> > > >>I found a couple of the older Cheetah 10K 18gb drives and want to try > > >>to use them on my old Sparc system. > > >> > > >>I checked the Seagate web page and I could not find any of the > > >>information I need. > > >> > > >> > > >>Thanks, > > >> Mike |
| |||
| In article <e60d72ed.0406070209.33c24987@posting.google.com >, msargent100@hotmail.com (Mike) writes: > After a little more research on Sun.com I found a couple settings to > try in /etc/system: > > set scsi_options=0x58 > set scsi_reset_delay=10000 > This might help to get rid of the "Connected command timeout". Maybe 0xf8 works, too, and is less restrictive. > Also after reading a bit more I was curious if I should set the jumper > on the drives to force single-ended mode for both drives. > > Recommendations? > Yes, force single-ended! Also, ensure you have an active non-LVD terminator! Ensure that the (passive) terminator on the CDROM is *not* enabled. If possible, have the fast devices on a different SCSI bus than the slow devices. If your machine randomly drops to the OK prompt there is another sever hardware problem. It might be a broken keyboard or a loose keyboard cable. (The HW break can be disabled with command "kbd -a disable" at least since Solaris 2.6.) It can also be a memory problem; I have seen the message "level [0-9] interrrupt" and drop to the OK prompt. > > > > msargent100@hotmail.com (Mike) wrote in message news:<e60d72ed.0406060357.43b1c7b0@posting.google. com>... > > OK in /var/adm/messages I see several of the following type entries: > > > > Connected command timeout for Target 1.0 > > Target 1.0 reducing sync. transfer rate > > SCSI transport failed: reason 'reset': retrying > > > > And several other WARNING messages pointing to sd1 > > > > > > Ideas??? > > > > > > CJT <abujlehc@prodigy.net> wrote in message news:<40C1EE8D.8050101@prodigy.net>... > > > Mike wrote: > > > > > > > Thanks all you were right - no format.dat needed. Just a boot -r at > > > > least to see the drive. > > > > > > > > Now the problem is that the system will just randomly drop to the OK > > > > prompt with no fore warning! Just bang the system stops responding to > > > > my telnet connection (happens with direct console login also). When I > > > > look at the console window I see a "Type go to resume" message and the > > > > OK prompt. Sometimes typing "go" the system will respond and continue, > > > > but it is usually dead and needs a power cycle. > > > > > > Are you sure there's nothing in the log files? > > > > > > > > > > > On the internal scsi bus I have an old Sun cdrom OEM type so it is > > > > probably a speedy 2x or something like that (but hey it works!). And 2 > > > > of the 18.2GB lvd drives. Nothing external and I have a terminator on > > > > the extra connector. > > > > > > > > The only jumpers I have set on the drives are to set the SCSI id ( 1 & > > > > 2 ). > > > > > > > > I had heard that the most the system would support was 26gb total but > > > > that sounded a little bogus so I tried anyway. > > > > > > > > Could this flakey operation be a result of exceeding the max capacity > > > > of the host adapter? Or mixing lvd and non-lvd (cdrom) on the same > > > > scsi bus cable? Is it a SE jumper setting issue? Or ??? > > > > > > > > I also have a couple older 9gb drives would it be easier to just fall > > > > back to those? > > > > > > > > Any help would be gratelty appreciated! > > > > > > > > > > > > Thanks, > > > > Mike > > > > > > > > > > > > msargent100@hotmail.com (Mike) wrote in message news:<e60d72ed.0405252355.349202b6@posting.google. com>... > > > > > > > >>Any ideas where can I find information to generate an entry in the > > > >>/etc/format.dat for a Segate ST118202LC drive (Is it even compatible > > > >>with???) running on a Sun 630MP w/Solaris 2.5.1? > > > >> > > > >>I found a couple of the older Cheetah 10K 18gb drives and want to try > > > >>to use them on my old Sparc system. > > > >> > > > >>I checked the Seagate web page and I could not find any of the > > > >>information I need. > > > >> > > > >> > > > >>Thanks, > > > >> Mike -- Michael Tosch IT Specialist HP Managed Services Germany Phone: +49 2407 575 313 Mail: michael.tosch:hp.com |
| ||||
| Thanks! Set the jumper to force SE mode and entered the SCSI options in /etc/system file and all appears to be running OK. Coincidentally replace the keyboard because the mouse was not working. And have not had a random drop to the OK since. Life is good once more. Thanks for all the help and recommendations. Now I will just have to start loading software. Thanks, Mike eedmit@NO.eed.SPAM.ericsson.PLS.se (Michael Tosch) wrote in message news:<ca1i6d$l9n$1@aken.eed.ericsson.se>... > In article <e60d72ed.0406070209.33c24987@posting.google.com >, msargent100@hotmail.com (Mike) writes: > > After a little more research on Sun.com I found a couple settings to > > try in /etc/system: > > > > set scsi_options=0x58 > > set scsi_reset_delay=10000 > > > > This might help to get rid of the "Connected command timeout". > Maybe 0xf8 works, too, and is less restrictive. > > > Also after reading a bit more I was curious if I should set the jumper > > on the drives to force single-ended mode for both drives. > > > > Recommendations? > > > > Yes, force single-ended! > Also, ensure you have an active non-LVD terminator! > Ensure that the (passive) terminator on the CDROM is *not* enabled. > If possible, have the fast devices on a different SCSI bus than the > slow devices. > > If your machine randomly drops to the OK prompt there is another sever > hardware problem. > It might be a broken keyboard or a loose keyboard cable. > (The HW break can be disabled with command "kbd -a disable" at least > since Solaris 2.6.) > It can also be a memory problem; I have seen the message > "level [0-9] interrrupt" and drop to the OK prompt. |