Hi!
----
Does anyone have any experience whether the Ultra 5/360MHz machines
support 180GB ATA drives under Solaris 2.7 ?
----
Bye,
Roland
Hi!
----
Does anyone have any experience whether the Ultra 5/360MHz machines
support 180GB ATA drives under Solaris 2.7 ?
----
Bye,
Roland
(That's twice in 3 days - I wonder how many times I can post that exact
same thing within a week...)
Scott.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
> They don't.
So I have to use Solaris 2.9, right ?
----
Bye,
Roland
--
__ . . __
/O /==\ O\ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
(;O/ \/ \O;) TEL +49 641 99-41370 FAX +49 641 99-41359
This is limited by the controller chip and not the software. Even Solaris 9
would not allow to address the full capacity of the drive.
The physical limit is 137 GB.
Michael
> > >Does anyone have any experience whether the Ultra 5/360MHz machines
> > >support 180GB ATA drives under Solaris 2.7 ?
> > They don't.
> ;-(
> So I have to use Solaris 2.9, right ?
> ----
> Bye,
> Roland
> --
> __ . . __
> /O /==\ O\ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
> (;O/ \/ \O;) TEL +49 641 99-41370 FAX +49 641 99-41359
>> They don't.
>So I have to use Solaris 2.9, right ?
John
> >> They don't.
If you have some evidence or proof that there really is some sortQuote:> >So I have to use Solaris 2.9, right ?
> the Ultra 5 on-board IDE does not support lba48 no matter which
> version of Solaris you use.
Although it's been nearly a year since you last posted that 48-bit LBA
canard, AFAIK it's still wrong. You didn't correct my response
the last time this came up so I've no reason to doubt that it's just as
bogus now as it was then. I bet a year from now, 2.9 still won't support
48-bit LBAs and you'll still be telling people (that Bruce Adler is a major
* and) the U5/10 controller chip can't support 48-bit LBAs.
As I explained previously, it's the driver (not the controller) that's
deficient:
http://www.veryComputer.com/%24n97.127500%40newsre...
" ... AFAIK, adding 48-bit LBA support to an Ultra 5/10 should
simply require updated device drivers for the OS and boot
PROM (OBP). ... "
If the SPARC driver writers at Sun are having trouble figuring out
the 48-bit updates for the SPARC driver, then they should sneak
a peek at 48-bit LBA changes in the current x86 ata driver.
i am implying that it will not use the available capacity.Quote:>Huh??? You're implying that a 180GB driver won't work at all.
my troubles have been with the Sun Blade 100 which is newer than theQuote:>If you have some evidence or proof that there really is some sort
>of inherent problem with the U5/10's on-board controller I'd like
>to hear exactly what it is.
i do not remember calling Bruce Adler a minor * let aloneQuote:>you'll still be telling people (that Bruce Adler is a major
>* and) the U5/10 controller chip can't support 48-bit LBAs.
i wish they would.Quote:>If the SPARC driver writers at Sun are having trouble figuring out
>the 48-bit updates for the SPARC driver, then they should sneak
>a peek at 48-bit LBA changes in the current x86 ata driver.
The hardware is limited to 137GB disks.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
>> >> They don't.
> Huh??? You're implying that a 180GB driver won't work at all.
> AFAIK, that's wrong. I believe the correct answer is that drives larger
[...]
> the drive, and which driver patches were installed. The capacity may be
> reduced to as small as 8GB or, if you're lucky, to the 28-bit LBA limit of
Scott
> >> >> They don't.
> > Huh??? You're implying that a 180GB driver won't work at all.
> > AFAIK, that's wrong. I believe the correct answer is that drives larger
> [...]
> > the drive, and which driver patches were installed. The capacity may be
> > reduced to as small as 8GB or, if you're lucky, to the 28-bit LBA limit of
> Well I don't know about you, but if I had a 180Gb hard disk showing up
> as an 8Gb disk, then I'd consider that the disk in question wasn't supported
> by the host...
For example, if someone has an existing system with a dead drive and they
just want to, as quickly as possible, get it repaired and restored back to
the state it was in prior to the drive failure, then given that you can't
get brand new 8GB drives anymore (the smallest available is about 60GB),
and given that the newer larger drives cost less than half what the 8GB
drives cost when they were available, and given that real soon 180GB is
going to be the smallest available drive, I'm certain that some people
would just use the larger drive and not even care about the "lost" space.
In other words, if you can't get the exact same part, it's useful to
know what kinds of substitute parts are usable.
1. ATA ZIP drive on Solaris 2.7 x86
After posting an inquiry the other day, I experimented some
more. The bottom line is that it seems to behave just like a
a scsi ZIP drive for me.
Perhaps the tipoff is the the device:
/dev/rdsk/c1t1d0s2 ( mine is on sec. ide, as slave device )
which points to
I was able to format and newfs as a Solaris disk (and copy and
read files to it)
and, more importantly, the mtools-3.9.1 package works fine
after the addition of the lines
# # ZIP disk for Solaris86:
# Drive Z is ZIP-100 at ATA-1,1
drive Z: file="/dev/rdsk/c1t1d0s2" partition=4 scsi=1 nodelay exclusive
to /etc/mtools.conf.
If you don't set /usr/local/bin/mtools as suid root, ordinary
users cannot access the zip drive. I assume that there are good
reasons not to run it suid (e.g. unrestricted access to the disk
systems ??)
I don't know all the interactions with the volume manager
( my tests were with this turned off ).
I was not able to mount the zip disk as a pcfs filesystem.
Good luck, Clarence
--
Clarence Wilkerson \ HomePage: http://www.math.purdue.edu/~wilker
Dept. of Mathematics \ Messages: (765) 494-1903, FAX 494-0548
Purdue University, \
W. Lafayette, IN 47907-1395 \
3. Building Apache 1.3.6 or 1.3.9 with DSO Support on Solaris 2.7
4. Apache version for linux 6.0
5. Promise Ultra100 (ATA-100 controller) compatibility w/ OpenBSD 2.7
6. interpretting pmap -x output
7. Add HP Print Support to Solaris 2.7 (Sparc)
8. signal()
9. Solaris 2.7 and IDE Zip drive
10. Support for ATA-2 or ATA-3 transfer modes.
11. can I install ab Solaris 2.5 to Solaris 2.7 x86
12. Updating 2.7 to 2.7-current - error: __warn_references in libcompat
13. Jumpstart for Solaris 2.5.1 versus Solaris 2.6, 2.7, 2.8