Re: Question on extended LBA (48Bit) adressing of HDD
Hi, > I have been fiddling around with the options a little bit. fdisk has a > somewhat strange behaviour (to me ...) > - if I start fdisk, say "s" (make a new sun-disklabel), walk through the > manual disk-recognition, make a "p" at the end, I > see the disk partitioned. Hum, i remember to have the same feelings. I just play a while with the Dell under winxp and format, and debian under x86 (on the dell). Since it recognise well the hdd under the dell computer, i can make my fs ext3 on it and i got no problem after on the Sun. Here more infos from my sun & the hdd #> cat /etc/fstab # ... /dev/hdb1 /mnt/data ext3defaults0 0 ... #> fdisk /dev/hdb Disk /dev/hdb (Sun disk label): 255 heads, 63 sectors, 30399 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/hdb1 0 30393 244131772+ 83 Linux native /dev/hdb2 u 30393 30399 48195 82 Linux swap /dev/hdb3 0 30399 244179967+ 5 Whole disk #> dmesg |grep DMA CMD646: chipset revision 0x03, MultiWord DMA Force Limited ide0: BM-DMA at 0x1fe02c00020-0x1fe02c00027, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0x1fe02c00028-0x1fe02c0002f, BIOS settings: hdc:pio, hdd:pio hda: 17803297 sectors (9115 MB) w/512KiB Cache, CHS=17662/16/63, (U)DMA hdb: 488397168 sectors (250059 MB) w/7938KiB Cache, CHS=30401/255/63, (U)DMA I did it a while ago, and in a rush time ;-) so i don't remember "exactly" what/how i did right, but the idea is here. Hope it helps. Take care Lorenzo
RE: Question on extended LBA (48Bit) adressing of HDD
Dear Listmembers,
der Lorenzo,
I have been fiddling around with the options a little bit. fdisk has a somewhat
strange behaviour (to me ...)
- if I start fdisk, say "s" (make a new sun-disklabel), walk through the manual
disk-recognition, make a "p" at the end, I see the disk partitioned.
- if I save this ("w") without further actions, all partitions are gone again
after the next call to fdisk. Formatting of the disk is impossible, because
i.e. mkfs.ext3 tells me there is nothing to format.
- if I start fdisk again, make a new sun-disklabel, delete partition 1 and
create some /one new partition/s, save this, everything works fine. I can use
the disk, I can make filesystems.
Maybe, Lorenzo, you can test this on your site if you have the time to do it!
Let me know about your mileage.
- finally: as readily stated, udma2 is the max choice speedwise. My suggestion
would be to always include ide=nodma for sparc and set the dma-mode later on.
The defaults definitively override the (U60 (?)) capabilities.
What about you, Lorenzo? What udma (if any) mode can you use on your U10?
Take care
Dieter
-Original Message-
From: Lorenzo [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 16, 2004 12:43 PM
To: debian-sparc@lists.debian.org
Subject: Re: Question on extended LBA (48Bit) adressing of HDD
Hi,
I've got almost same problem on my Ultra10 workstation with Debian on it
with my an Hitachi Deskstar 250GB.
I succed to make my hdd works, by
1) put the hdd on a Dell PC
2) make it recognise by the bios
3) format it by windows
4) put it back on the Sun Ultra10
5) play a little with fdisk / mkfs
Here a part of my logs about dmsg and the drive
...
hdb: HDS722525VLAT80, ATA DISK drive
hdb: 268435455 sectors (137439 MB) w/7938KiB Cache, CHS=266305/16/63, (U)DMA
Hope it's help.
Regards.
Lorenzo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
***
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe
dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and delete this e-mail. Any unauthorized copying,
disclosure or distribution of the contents in this e-mail is strictly forbidden.
***
Re: Question on extended LBA (48Bit) adressing of HDD
Hi, I've got almost same problem on my Ultra10 workstation with Debian on it with my an Hitachi Deskstar 250GB. I succed to make my hdd works, by 1) put the hdd on a Dell PC 2) make it recognise by the bios 3) format it by windows 4) put it back on the Sun Ultra10 5) play a little with fdisk / mkfs Here a part of my logs about dmsg and the drive ... hdb: HDS722525VLAT80, ATA DISK drive hdb: 268435455 sectors (137439 MB) w/7938KiB Cache, CHS=266305/16/63, (U)DMA Hope it's help. Regards. Lorenzo
Re: Question on extended LBA (48Bit) adressing of HDD
JD> FYI: I upgraded the bios of my Promise TX2 - 133 without success (what was = JD> in accordance with my expectations. I had had build 14, now it's build 15).= If it was not a F-code ROM for OpenFirmware, it does not change anything since PC ROMs are not run on sparcs (obviously). -- Meelis Roos
RE: Question on extended LBA (48Bit) adressing of HDD
Dear Daniel,
dear all,
FYI: I upgraded the bios of my Promise TX2 - 133 without success (what was in
accordance with my expectations. I had had build 14, now it's build 15). Some
more fiddling around led to the following results:
pio - modes and udma - modes up to udma mode 2 work on my U60 SMP. When
switching to higher speed udma modes the problems start to occur:
Sep 13 10:56:17 localhost kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 13 10:56:17 localhost kernel: hde: dma_intr: error=0x84 { DriveStatusError
BadCRC }
Sep 13 10:56:17 localhost kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 13 10:56:17 localhost kernel: hde: dma_intr: error=0x84 { DriveStatusError
BadCRC }
Sep 13 10:56:17 localhost kernel: PDC202XX: Primary channel reset.
Sep 13 10:56:17 localhost kernel: ide2: reset: success
the error=0x84 might also be error=0x04. I use a short 80 pin cable. The same
errors occur for different drives and different cables.
If those errors occur, the system starts messing data on the disk, failures are
the result.
Maybe there is a FM that says "you should not use udma modes faster than udma2
on Ultra Sparc", but I did not find until now. I do not mind, this works for me
now. However, I simply want to point out that there (might ...) be something
wrong.
For everybody else: boot with ide=nodma and turn it back on afterwards using
hdparm seems a good solution for now. I have a boot.local file in /etc/init.d
saying:
/sbin/hdparm -d1 -X udma2 /dev/hde
for now. Not to forget: I use 2.4.26 on Debian Sarge, U60 SMP @ 360 MHz.
Take care
Dieter Jurzitza
-Original Message-
From: Daniel J. Priem [mailto:[EMAIL PROTECTED]
Sent: Friday, September 10, 2004 5:17 PM
To: Jurzitza, Dieter
Cc: sparcliste
Subject: RE: Question on extended LBA (48Bit) adressing of HDD
Am Fr, den 10.09.2004 schrieb Daniel J. Priem um 17:05:
if its before 2.20.0.12( was mine) then you need to flash it to a newer
***
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und
loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe
dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and delete this e-mail. Any unauthorized copying,
disclosure or distribution of the contents in this e-mail is strictly forbidden.
***
RE: Question on extended LBA (48Bit) adressing of HDD
Am Fr, den 10.09.2004 schrieb Daniel J. Priem um 17:05: > Am Fr, den 10.09.2004 schrieb Jurzitza, Dieter um 16:42: > > Dear listmembers, > > dear Daniel, > > the formatting works now, this has been my fault (as always ...). However, > > I am running into severe file-system corruption. > > > > I have been initializing a 40GByte Maxtor hdd, copied files to it, and I > > could boot. Everything runs just smooth. > > > > Doing the same with the new 400G Hitachi drive results in massive > > file-system corruption. Copying seems to work ok, but after trying to boot > > from this disk I get a total mess. > > > > DMA is turned off in all cases (at the boot prompt). This ought to be a > > pickyness of the controler, isn't it > > (Promise 133 TX2 PCI-Device) ah. forgot something important what is the bios revision on your controller? if its before 2.20.0.12( was mine) then you need to flash it to a newer version > > i use the promise 133 ultra tx2 with chipset pdc20269 > works here really fine with some 200GB and 160GB Hardrives connected > one thing you can check is if you need to enable lba48 somwhere in the > drive with a manufacter tool. > example: > i recived a set of samsung sp1604n wich is udma6/133 capable. > but my controller tells me that all my drives are only using udma5 > so i contacted the manufacter and the told me that i need hutil from > samsung-website to set the harddrive(bios inside HD) to enable udma6. > i know udma is not responsible for size but just as example > > regards > daniel > > > > > > > Any ideas? > > > > Again, many thanks for your help, > > take care > > > > > > > > Dieter Jurzitza > > > > -Original Message- > > From: Daniel J. Priem [mailto:[EMAIL PROTECTED] > > *** > > ide: limit drive capacity to 137GB if host doesn't support LBA48 > > > > this looks for me that if you host does not support lba48 the you can > > > > > > > > *** > > Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte > > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > > irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und > > loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte > > Weitergabe dieser Mail ist nicht gestattet. > > > > This e-mail may contain confidential and/or privileged information. If you > > are not the intended recipient (or have received this e-mail in error) > > please notify the sender immediately and delete this e-mail. Any > > unauthorized copying, disclosure or distribution of the contents in this > > e-mail is strictly forbidden. > > *** signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
RE: Question on extended LBA (48Bit) adressing of HDD
Am Fr, den 10.09.2004 schrieb Jurzitza, Dieter um 16:42: > Dear listmembers, > dear Daniel, > the formatting works now, this has been my fault (as always ...). However, I > am running into severe file-system corruption. > > I have been initializing a 40GByte Maxtor hdd, copied files to it, and I > could boot. Everything runs just smooth. > > Doing the same with the new 400G Hitachi drive results in massive file-system > corruption. Copying seems to work ok, but after trying to boot from this disk > I get a total mess. > > DMA is turned off in all cases (at the boot prompt). This ought to be a > pickyness of the controler, isn't it (Promise 133 TX2 PCI-Device) i use the promise 133 ultra tx2 with chipset pdc20269 works here really fine with some 200GB and 160GB Hardrives connected one thing you can check is if you need to enable lba48 somwhere in the drive with a manufacter tool. example: i recived a set of samsung sp1604n wich is udma6/133 capable. but my controller tells me that all my drives are only using udma5 so i contacted the manufacter and the told me that i need hutil from samsung-website to set the harddrive(bios inside HD) to enable udma6. i know udma is not responsible for size but just as example regards daniel > > Any ideas? > > Again, many thanks for your help, > take care > > > > Dieter Jurzitza > > -Original Message- > From: Daniel J. Priem [mailto:[EMAIL PROTECTED] > *** > ide: limit drive capacity to 137GB if host doesn't support LBA48 > > this looks for me that if you host does not support lba48 the you can > > > > *** > Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und > loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte > Weitergabe dieser Mail ist nicht gestattet. > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) please > notify the sender immediately and delete this e-mail. Any unauthorized > copying, disclosure or distribution of the contents in this e-mail is > strictly forbidden. > *** signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
RE: Question on extended LBA (48Bit) adressing of HDD
Dear listmembers, dear Daniel, the formatting works now, this has been my fault (as always ...). However, I am running into severe file-system corruption. I have been initializing a 40GByte Maxtor hdd, copied files to it, and I could boot. Everything runs just smooth. Doing the same with the new 400G Hitachi drive results in massive file-system corruption. Copying seems to work ok, but after trying to boot from this disk I get a total mess. DMA is turned off in all cases (at the boot prompt). This ought to be a pickyness of the controler, isn't it (Promise 133 TX2 PCI-Device) Any ideas? Again, many thanks for your help, take care Dieter Jurzitza -Original Message- From: Daniel J. Priem [mailto:[EMAIL PROTECTED] *** ide: limit drive capacity to 137GB if host doesn't support LBA48 this looks for me that if you host does not support lba48 the you can *** Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden. ***
Re: Question on extended LBA (48Bit) adressing of HDD
Am Fr, den 10.09.2004 schrieb Jurzitza, Dieter um 14:51: > Dear listmembers, > does anyone of you know how to get a 400 GByte AT - drive formatted to it's > full capacity? I am limited to 137GByte, whatever I try to do. My main > problem is to understand what is the root cause for this limitation. fdisk > does not allow me to assign values crossing this limit. hdparm returns this > limit - even though I know exactly that the device is larger than that. > Is this a controler issue? A driver issue? > Many thanks for helping, under ggole i found something like this Linux 2.6.0-test4* ide: limit drive capacity to 137GB if host doesn't support LBA48 this looks for me that if you host does not support lba48 the you can not use drives bigger than 137gb so no its up to you. does your host support lba48? regards daniel > take care > > > Dieter Jurzitza > signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
