|
|
|
|
| Author |
Message |
da9000
Guest
|
 Posted: Wed May 30, 2007 12:14 am Post subject: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext'd r |
 |
|
I have the above mentioned hard drive, and according to intelligent-
peripheral.com/manuals/quantum_ucg.pdf (because, believe me, neither
Seagate nor Maxtor seem to know or have anything to do with this disk
and many other Quantum disks, even though they paid lots of millions
to buy out the company, even if indirectly), has more than 17,000,000
LBA sectors (that's 17 million plus 512byte sectors), giving a
capacity of 9.1GB or so. More than 8GB, that's the point.
Anyways, I've not been able to have *any* of the PC SCSI cards that I
have to recognize it as a greater than 8GB drive, and they all *do*
have int 13h extended support (which shouldn't matter, because all I
want to do is low level format it -- aka: I'm not dealing with any OS
at the moment nor trying to boot from it).
Cards I've tried: Adaptec ISA: AHA-1542B, PCI: AHA-2940, AHA-2940AU,
AHA-2940U, Buslogic BT-930, and Ami MegaRAID (I forget the model, but
it's been happily working with 18GB drives just fine).
I also used the SCU tool from http://www.scsifaq.org, and the "show
capacity" command, and I also get back only 16777216 sectors (which is
2^24 = 8GB limit) for the drive.
I've also tried it on an older PowerPC Mac, a 7200, which has an
NCR53c96 SCSI controller I believe, and it also sees this drive as
having only 16777216 sectors.
Any ideas or suggestions anyone? Am I doing something wrong?
Thanks in advance
PS. Anyone else with this drive: does yours sound like a hurricane or
airport, when turned on? |
|
| Back to top |
|
 |
|
|
Michael Baeuerle
Guest
|
| Posted: Wed May 30, 2007 3:29 pm Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
da9000 wrote:
| Quote: |
[...]
I also used the SCU tool from http://www.scsifaq.org, and the "show
capacity" command, and I also get back only 16777216 sectors (which is
2^24 = 8GB limit) for the drive.
|
The READ CAPACITY commands (even the 10Byte version) don't have a 24Bit
Limit. Looks like the drive really have 2^24 blocks. Maybe it's an OEM
version with special limitation in the firmware (to workaround BIOS bugs
in the OEMs machines).
If Quantum had implemented it the simple way by only returning a smaller
capacity, the rest of the blocks may still be available. Try to execute
a READ(10) command on LBA 16777216 ...
Micha |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted: Wed May 30, 2007 4:10 pm Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
And your question is?
"da9000" <4donis@gmail.com> wrote in message news:1180478616.791970.32400@r19g2000prf.googlegroups.com
| Quote: | I have the above mentioned hard drive, and according to intelligent-
peripheral.com/manuals/quantum_ucg.pdf (because, believe me, neither
Seagate nor Maxtor seem to know or have anything to do with this disk
and many other Quantum disks, even though they paid lots of millions
to buy out the company, even if indirectly), has more than 17,000,000
LBA sectors (that's 17 million plus 512byte sectors), giving a
capacity of 9.1GB or so. More than 8GB, that's the point.
Anyways, I've not been able to have *any* of the PC SCSI cards that I
have to recognize it as a greater than 8GB drive, and they all *do*
have int 13h extended support (which shouldn't matter, because
all I want to do is low level format it
|
So what's keeping you (rethorical).
Btw, never Low Level Format a drive unless you need a different sector size.
| Quote: | -- aka: I'm not dealing with any OS at the moment nor trying to boot from it).
Cards I've tried: Adaptec ISA: AHA-1542B, PCI: AHA-2940, AHA-2940AU,
AHA-2940U, Buslogic BT-930, and Ami MegaRAID (I forget the model, but
it's been happily working with 18GB drives just fine).
I also used the SCU tool from http://www.scsifaq.org, and the "show
capacity" command, and I also get back only 16777216 sectors (which is
2^24 = 8GB limit) for the drive.
I've also tried it on an older PowerPC Mac, a 7200, which has an
NCR53c96 SCSI controller I believe, and it also sees this drive as
having only 16777216 sectors.
|
So it has been shortstroked.
| Quote: |
Any ideas or suggestions anyone? Am I doing something wrong?
|
Try: set device {capacity value} ; help set device
I've never used it so you are on your own there.
Or Try WDBench or codeupdt to set it back to full capacity.
WD's SCSI Workbench is easiest but requires Windows9x/ME.
codeupdt: select mode sense/select, header and block descriptor,
and change the number of blocks. DOS or Win9x/ME NT?
WD Bench and codeupdt are linked from www.nu2.nu/scsitool page
WD Bench has moved: http://support.wdc.com/download/?cxml=n&pid=24&swid=25
| Quote: |
Thanks in advance
PS. Anyone else with this drive: does yours sound like a hurricane or
airport, when turned on? |
|
|
| Back to top |
|
|
da9000
Guest
|
| Posted: Thu May 31, 2007 2:46 am Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
On May 30, 3:29 am, Michael Baeuerle <michael.baeue...@stz-e.de>
wrote:
| Quote: | The READ CAPACITY commands (even the 10Byte version) don't have a 24Bit
Limit. Looks like the drive really have 2^24 blocks. Maybe it's an OEM
version with special limitation in the firmware (to workaround BIOS bugs
in the OEMs machines).
|
Oh! Perhaps that's it, because LaCie branded one, even though it's
Quantum. Perhaps they did that... But on the other hand it does say
"Atlas 9gb" on the LaCie label.
| Quote: | capacity, the rest of the blocks may still be available. Try to execute
a READ(10) command on LBA 16777216 ...
|
Could you please assist me a little with this, as I couldn't figure
out how to send SCSI commands directly through SCU...
Thanks in advance! |
|
| Back to top |
|
|
da9000
Guest
|
| Posted: Thu May 31, 2007 2:55 am Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
On May 30, 4:10 am, "Folkert Rienstra" <see_reply...@myweb.nl> wrote:
| Quote: | So it has been shortstroked.
|
I've not heard the term, but I assume it means it's been logically
capped (as in HPA/UNHPA for IDE drives)
| Quote: | Try: set device {capacity value} ; help set device
I've never used it so you are on your own there.
Or Try WDBench or codeupdt to set it back to full capacity.
WD's SCSI Workbench is easiest but requires Windows9x/ME.
codeupdt: select mode sense/select, header and block descriptor,
and change the number of blocks. DOS or Win9x/ME NT?
WD Bench and codeupdt are linked fromwww.nu2.nu/scsitoolpage
WD Bench has moved:http://support.wdc.com/download/?cxml=n&pid=24&swid=25
|
Alright, I'll try those two. Thanks for the links and your input! |
|
| Back to top |
|
|
Fix your Windows Problems - FAST.
FREE Safe Scan Registry Check. Locate & Fix Errors in Minutes!
|
|
da9000
Guest
|
| Posted: Thu May 31, 2007 2:58 am Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
On May 30, 4:10 am, "Folkert Rienstra" <see_reply...@myweb.nl> wrote:
| Quote: | So it has been shortstroked.
|
I've not heard the term, but I assume it means it's been logically
capped (as in HPA/UNHPA for IDE drives)
| Quote: | Try: set device {capacity value} ; help set device
I've never used it so you are on your own there.
Or Try WDBench or codeupdt to set it back to full capacity.
WD's SCSI Workbench is easiest but requires Windows9x/ME.
codeupdt: select mode sense/select, header and block descriptor,
and change the number of blocks. DOS or Win9x/ME NT?
WD Bench and codeupdt are linked fromwww.nu2.nu/scsitoolpage
WD Bench has moved:http://support.wdc.com/download/?cxml=n&pid=24&swid=25
|
Alright, I'll try those two. Thanks for the links and your input! |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted: Thu May 31, 2007 2:58 am Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
"Robert Heller" <heller@deepsoft.com> wrote in message news:331ba$465dffdf$404a99a1$28480@news.news-service.com
| Quote: | At 30 May 2007 14:46:25 -0700 da9000 <4donis@gmail.com> wrote:
On May 30, 3:29 am, Michael Baeuerle <michael.baeue...@stz-e.de
wrote:
The READ CAPACITY commands (even the 10Byte version) don't have a 24Bit
Limit. Looks like the drive really have 2^24 blocks. Maybe it's an OEM
version with special limitation in the firmware (to workaround BIOS bugs
in the OEMs machines).
Oh! Perhaps that's it, because LaCie branded one, even though it's
Quantum. Perhaps they did that... But on the other hand it does say
"Atlas 9gb" on the LaCie label.
Something to note: disk makers 'play games' with how they label/market
disk capacity.
|
No, they don't.
| Quote: | Quantum could be indicating that the disk is
(truthfully!) 9g in *unformatted* capacity (including 'spare' sectors,
etc.), but it probably works to 8gig in actually usable disk space after
low-level formatting and setting aside spare sectors, timing tracks, and
so on.
|
What exactly did you not get from the specifications he presented in his first post, Heller?
intelligent-peripheral.com/manuals/quantum_ucg.pdf
What part of "Formatted Capacity" dit you not understand.
Are you completely braindead or is it just a pose.
| Quote: |
capacity, the rest of the blocks may still be available. Try to execute
a READ(10) command on LBA 16777216 ...
Could you please assist me a little with this, as I couldn't figure
out how to send SCSI commands directly through SCU...
Thanks in advance! |
|
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted: Thu May 31, 2007 2:58 am Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
"Michael Baeuerle" <michael.baeuerle@stz-e.de> wrote in message news:j800j4-05v.ln1@micha.freeshell.org
| Quote: | da9000 wrote:
[...]
I also used the SCU tool from http://www.scsifaq.org, and the "show
capacity" command, and I also get back only 16777216 sectors (which is
2^24 = 8GB limit) for the drive.
The READ CAPACITY commands (even the 10Byte version) don't have a 24Bit
Limit.
|
No, really? Who would have thought that.
All these incredible stories about SCSI's 2TiB limit being true afterall.
Actually, the socalled 8GiB CHS limit is 1024*256*63=16515072 sectors.
16777216 would be an LBA error(-limit).
| Quote: | Looks like the drive really have 2^24 blocks.
|
Oh, what makes you think that?
| Quote: | Maybe it's an OEM version with special limitation in the firmware (to
workaround BIOS bugs in the OEMs machines).
If Quantum had implemented it the simple way by only returning a
smaller capacity, the rest of the blocks may still be available.
|
"returning a smaller capacity" *is* the simple way.
Anyone can set it with the proper configuration tools.
It comes with a smaller usable capacity, as intended.
Returning a smaller capacity without actually curtailing the usable
capacity is not actually that simple. It requires a firmware change.
| Quote: | Try to execute a READ(10) command on LBA 16777216 ...
Micha |
|
|
| Back to top |
|
|
Robert Heller
Guest
|
| Posted: Thu May 31, 2007 2:58 am Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
At 30 May 2007 14:46:25 -0700 da9000 <4donis@gmail.com> wrote:
| Quote: |
On May 30, 3:29 am, Michael Baeuerle <michael.baeue...@stz-e.de
wrote:
The READ CAPACITY commands (even the 10Byte version) don't have a 24Bit
Limit. Looks like the drive really have 2^24 blocks. Maybe it's an OEM
version with special limitation in the firmware (to workaround BIOS bugs
in the OEMs machines).
Oh! Perhaps that's it, because LaCie branded one, even though it's
Quantum. Perhaps they did that... But on the other hand it does say
"Atlas 9gb" on the LaCie label.
|
Something to note: disk makers 'play games' with how they label/market
disk capacity. Quantum could be indicating that the disk is
(truthfully!) 9g in *unformatted* capacity (including 'spare' sectors,
etc.), but it probably works to 8gig in actually usable disk space after
low-level formatting and setting aside spare sectors, timing tracks, and
so on.
| Quote: |
capacity, the rest of the blocks may still be available. Try to execute
a READ(10) command on LBA 16777216 ...
Could you please assist me a little with this, as I couldn't figure
out how to send SCSI commands directly through SCU...
Thanks in advance!
|
--
Robert Heller -- 978-544-6933
Deepwoods Software -- Linux Installation and Administration
http://www.deepsoft.com/ -- Web Hosting, with CGI and Database
heller@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted: Thu May 31, 2007 2:59 am Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
"da9000" <4donis@gmail.com> wrote in message news:1180562119.563157.301100@o11g2000prd.googlegroups.com
| Quote: | On May 30, 4:10 am, "Folkert Rienstra" <see_reply...@myweb.nl> wrote:
So it has been shortstroked.
I've not heard the term, but I assume it means it's been logically capped
|
Yup.
| Quote: | (as in HPA/UNHPA for IDE drives)
|
Never heard of it ;-)
Presumably HPA stands for Host Protected Area?
Better known by Set Max Address command. Yeah, like that.
| Quote: |
Try: set device {capacity value} ; help set device
I've never used it so you are on your own there.
Or Try WDBench or codeupdt to set it back to full capacity.
WD's SCSI Workbench is easiest but requires Windows9x/ME.
codeupdt: select mode sense/select, header and block descriptor,
and change the number of blocks. DOS or Win9x/ME NT?
WD Bench and codeupdt are linked fromwww.nu2.nu/scsitoolpage
WD Bench has moved:http://support.wdc.com/download/?cxml=n&pid=24&swid=25
Alright, I'll try those two. Thanks for the links and your input! |
|
|
| Back to top |
|
|
Fix your Windows Problems - FAST.
FREE Safe Scan Registry Check. Locate & Fix Errors in Minutes!
|
|
Michael Baeuerle
Guest
|
| Posted: Thu May 31, 2007 2:19 pm Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
Folkert Rienstra wrote:
| Quote: |
Michael Baeuerle wrote:
[...]
I also used the SCU tool from http://www.scsifaq.org, and the "show
capacity" command, and I also get back only 16777216 sectors (which is
2^24 = 8GB limit) for the drive.
The READ CAPACITY commands (even the 10Byte version) don't have a 24Bit
Limit.
No, really? Who would have thought that.
All these incredible stories about SCSI's 2TiB limit being true afterall.
|
There is a READ CAPACITY(16) command without this limit, but what has
this to do with the current problem?
| Quote: | Actually, the socalled 8GiB CHS limit is 1024*256*63=16515072 sectors.
16777216 would be an LBA error(-limit).
|
Or no error at all - as it seems the case here.
| Quote: | Looks like the drive really have 2^24 blocks.
Oh, what makes you think that?
|
16777216 blocks is no SCSI limit (and as you stated above no CHS Limit),
so I assume the drive really reported 16777216 blocks ("have" this
number of blocks).
| Quote: | Maybe it's an OEM version with special limitation in the firmware (to
workaround BIOS bugs in the OEMs machines).
If Quantum had implemented it the simple way by only returning a
smaller capacity, the rest of the blocks may still be available.
"returning a smaller capacity" *is* the simple way.
Anyone can set it with the proper configuration tools.
|
A standard command for this purpose like SET MAX ADDRESS for ATA don't
exist for SCSI (please correct me if this is wrong). So a special tool
for _this_ disk is required ...
| Quote: | It comes with a smaller usable capacity, as intended.
Returning a smaller capacity without actually curtailing the usable
capacity is not actually that simple. It requires a firmware change.
|
Both methods must be implemented in the firmware. Every proper written
firmware will always check the real LBA limit before executing a
command, so a constant like LBA_MAX should already exist.
Modifying only the READ CAPACITY command to return always 16777216 is
trivial (1 line of code in best case). That the rest of the medium is
still accessable is IMHO no drawback. Changing of the limit to arbitrary
values using a vendor specific command will be no problem at any time.
Changing the global LBA limit in the firmware would be trivial too, but
may have unwanted side effects like:
- The defect lists may now contain nonexistant LBAs
- A FORMAT UNIT don't format the whole medium any more
.... and possibly others. Changing the limit using this method without
following LL-format may lead to undesired behaviour. This can be
prevented, but such changes are non-trivial if the original firmware was
not designed for variable capacity.
Micha |
|
| Back to top |
|
|
Michael Baeuerle
Guest
|
| Posted: Thu May 31, 2007 2:53 pm Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
da9000 wrote:
| Quote: |
Michael Baeuerle wrote:
Try to execute a READ(10) command on LBA 16777216 ...
Could you please assist me a little with this, as I couldn't figure
out how to send SCSI commands directly through SCU...
Thanks in advance!
|
I have never used SCU before, so the other people may help you better.
But only reading a block seems to be as simple as:
---------------------------------------------------------------
[root@WStation2:/tmp]# scu -f /dev/sdc read media lba 0 compare off
Reading 1 block (0 - 0) on /dev/sdc (FIREBALL ST3.2S)...
[root@WStation2:/tmp]# scu -f /dev/sdc read media lba 777777777 compare
off
scu: Starting block 777777777 exceeds valid range of (0 - 6385695)
blocks.
---------------------------------------------------------------
The first attempt to LBA 0 was successful, the second attempt to
nonexistant LBA 777777777 was rejected. I can't tell you if the program
or the disk has rejected the second attempt, maybe the tool is too
intelligent for this purpose. I don't have read the whole documentation
and the source code was not included in my package ...
Micha |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted: Fri Jun 01, 2007 3:21 am Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
"Michael Baeuerle" <michael.baeuerle@stz-e.de> wrote in message news:ehg2j4-hh1.ln1@micha.freeshell.org
| Quote: | Folkert Rienstra wrote:
Michael Baeuerle wrote:
[...]
I also used the SCU tool from http://www.scsifaq.org, and the "show
capacity" command, and I also get back only 16777216 sectors (which is
2^24 = 8GB limit) for the drive.
The READ CAPACITY commands (even the 10Byte version) don't have a 24Bit
Limit.
No, really? Who would have thought that.
All these incredible stories about SCSI's 2TiB limit being true afterall.
There is a READ CAPACITY(16) command without this limit, but what has
this to do with the current problem?
|
Exactly my point. So why did you mention it at all, you started it.
| Quote: |
Actually, the socalled 8GiB CHS limit is 1024*256*63=16515072 sectors.
16777216 would be an LBA error(-limit).
Or no error at all - as it seems the case here.
|
Yes, though I seriously doubt that you know what case that is.
| Quote: |
Looks like the drive really have 2^24 blocks.
Oh, what makes you think that?
16777216 blocks is no SCSI limit
|
Not by specification, anyway. Doesn't mean that BIOSes
or drivers can't have limitations, deliberate or accidental.
| Quote: | (and as you stated above no CHS Limit),
|
Huh?
| Quote: | so I assume the drive really reported 16777216 blocks
|
It will happily report 100 blocks if you limit it to 100.
| Quote: | ("have" this number of blocks).
|
Would you still think that such a drive would actually have a capacity of
50kB? This Heller virus appears catching.
| Quote: |
Maybe it's an OEM version with special limitation in the firmware (to
workaround BIOS bugs in the OEMs machines).
If Quantum had implemented it the simple way by only returning a
smaller capacity, the rest of the blocks may still be available.
"returning a smaller capacity" *is* the simple way.
Anyone can set it with the proper configuration tools.
A standard command for this purpose like SET MAX ADDRESS for ATA don't
exist for SCSI
|
No!!! Really?
| Quote: | (please correct me if this is wrong).
|
Hereby corrected. Obviously, like Heller you have not been paying attention.
| Quote: | So a special tool for _this_ disk is required ...
|
Like it isn't for IDE drives.
Btw, 3 such tools have been mentioned already. Please pay attention.
| Quote: |
It comes with a smaller usable capacity, as intended.
Returning a smaller capacity without actually curtailing the usable
capacity is not actually that simple. It requires a firmware change.
Both methods must be implemented in the firmware.
|
Duh-uh! As if all the rest of the SCSI commands aren't. Of course it does.
Point is that being able to limit the capacity is standard in all SCSI drives
so no new firmware is necessary. Modifying standard behaviour requires a
firmware change. A firmware change means more firmwares to support.
| Quote: | Every proper written firmware will always check
the real LBA limit
|
Whatever that is supposed to mean.
| Quote: | before executing a command, so a constant like LBA_MAX should already exist.
|
Duh! Now think out of the box and think how this value can be changed.
| Quote: |
Modifying only the READ CAPACITY command to return always 16777216 is
trivial (1 line of code in best case).
|
The point of the read capacity command is to report the capacity such as it has
been set. Setting it fixed defeats it's purpose.
| Quote: | That the rest of the medium is still accessable is IMHO no drawback.
|
It's pointless.
No properly designed bios or driver will use it, since that's the whole point
of the exercise, to avoid hitting a problem by making the system not go there.
| Quote: | Changing of the limit to arbitrary values using a vendor specific command
will be no problem at any time.
|
It's unnecessary.
| Quote: |
Changing the global LBA limit in the firmware would be trivial too, but
may have unwanted side effects like:
- The defect lists may now contain nonexistant LBAs
|
Ooh, that is bad.
| Quote: | - A FORMAT UNIT don't format the whole medium any more
|
Och, imagine that.
| Quote: | ... and possibly others.
|
Like all the mode and status and whatnot pages code need rechecked?
| Quote: | Changing the limit using this method without
following LL-format may lead to undesired behaviour.
|
Yeah, the bad blocks beyond the limit may stage an uprising and you
would never know about it. I can see how that is totally intolerable.
| Quote: | This can be prevented, but such changes are non-trivial if the original
firmware was not designed for variable capacity.
|
Waffle. This Heller virus is catching on fast.
|
|
| Back to top |
|
|
da9000
Guest
|
| Posted: Fri Jun 01, 2007 8:27 am Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
On May 30, 3:59 pm, "Folkert Rienstra" <see_reply...@myweb.nl> wrote:
| Quote: | Never heard of it ;-)
Presumably HPA stands for Host Protected Area?
|
Yup! :)
| Quote: | Better known by Set Max Address command. Yeah, like that.
Try: set device {capacity value} ; help set device
I've never used it so you are on your own there.
Or Try WDBench or codeupdt to set it back to full capacity.
|
You're GOOD! It was indeed "short stroked" or capped or limited or
however one wants to say it!
I tried WDBench first, and it automatically found the true max LBA
limit (17,781,520). Set it, rebooted, and then the SCSI cards were
able to see more than 8192MB (about 8600MB I believe).
I then also tried it with SCU and the "set device capacity value"
command and it worked just the same. Good stuff!!
Now a couple more general questions:
1) I spent hours trying to find out how to get the true max LBA limit
with SCU, but no luck  "show capacity" returns the imposed limit.
Showing the mode pages doesn't have anything either... Anyone know?
(I'll try Michael Baeuerle's method of reading a sector that's out of
bounds to see what that returns, but I have a feeling that it will
return the capped limit, not the true max LBA limit... because that
makes more sense from a programming standpoint - current setting vs
permanent setting)
2) According to the mode pages (and from the noise of this beast),
it's a 7200RPM drive, yet doing a low-level format takes 5-6 (maybe
more, not sure, I fell asleep) hours. Isn't this way too slow?
3) After the low-level format is done, and I use dd if=/dev/sda of=/
dev/null bs=16k (Linux, MacOSX, *BSD) to exercise the drive, I only
get 1.1 - 1.5MB/sec. Tad bit low for a 7200RPM drive with 10 (!)
platters and with a FastSCSI card (either 10MB/sec or 20MB/sec
settings without complaints), in synchronus mode, isn't it? |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted: Fri Jun 01, 2007 2:09 pm Post subject: Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h ext |
|
|
"da9000" <4donis@gmail.com> wrote in message news:1180668450.176934.109690@g37g2000prf.googlegroups.com
| Quote: | On May 30, 3:59 pm, "Folkert Rienstra" <see_reply...@myweb.nl> wrote:
Never heard of it ;-)
Presumably HPA stands for Host Protected Area?
Yup! :)
Better known by Set Max Address command. Yeah, like that.
Try: set device {capacity value} ; help set device
I've never used it so you are on your own there.
Or Try WDBench or codeupdt to set it back to full capacity.
You're GOOD!
|
Yes, I know. Creates quite a bit of envy in this group too.
Baeuerle et all, are you paying attention !? Rob Turk, eat ***.
| Quote: | It was indeed "short stroked" or capped or limited or however one wants
to say it!
I tried WDBench first, and it automatically found the true max LBA
limit (17,781,520). Set it, rebooted, and then the SCSI cards were
able to see more than 8192MB (about 8600MB I believe).
|
17,781,520*512 = 9.104 GB or 8682 MiB
| Quote: |
I then also tried it with SCU and the "set device capacity value"
command and it worked just the same. Good stuff!!
Now a couple more general questions:
1) I spent hours trying to find out how to get the true max LBA limit
with SCU, but no luck "show capacity" returns the imposed limit.
Showing the mode pages doesn't have anything either... Anyone know?
|
No, but I vaguely remember that there was a trick to it, I just can't quite re-
member what it was and whether it was application or drive specific or not.
Something like inputting -1 (in binarie equivalent) or something similarly clever.
The Header and Block descriptor page in codeupdt has current, default
and saved settings but once you change the number, they all change.
| Quote: | (I'll try Michael Baeuerle's method of reading a sector that's out of
bounds to see what that returns, but I have a feeling that it will return the
capped limit, not the true max LBA limit... because that makes more sense
from a programming standpoint - current setting vs permanent setting)
2) According to the mode pages (and from the noise of this beast),
it's a 7200RPM drive,
yet doing a low-level format takes 5-6
|
Woosh, out the window went my warning.
| Quote: | (maybe more, not sure, I fell asleep) hours. Isn't this way too slow?
|
Depends.
With verification enabled it does it twice, once writing, once reading.
If so and with 1 MB/s, 5 hours sounds reasonable.
| Quote: | 3) After the low-level format is done, and I use dd if=/dev/sda of=/
dev/null bs=16k (Linux, MacOSX, *BSD) to exercise the drive, I only
get 1.1 - 1.5MB/sec. Tad bit low for a 7200RPM drive with 10 (!)
platters and with a FastSCSI card (either 10MB/sec or 20MB/sec
settings without complaints), in synchronus mode, isn't it?
|
The drive can do 9.5/8/5.5 MB/s (max/med/min) on a narrow Ultra card.
Read cache enabled? Disabled, it is about 10 times slower.
If cache is enabled the drive may have suffered severe physical shock.
That might also explain the noisyness. That or the 10 platters. |
|
| Back to top |
|
|
Fix your Windows Problems - FAST.
FREE Safe Scan Registry Check. Locate & Fix Errors in Minutes!
|
|
|
|
| |
Watched Topics
Search
Register
Log in to check your private messages
Profile
Log in
Memberlist
Usergroups