Re: hd 160GB problem
Ron Johnson <[EMAIL PROTECTED]> wrote: | On Fri, 2006-02-10 at 12:59 -0800, Robert Kopp wrote: | > | > --- mess-mate <[EMAIL PROTECTED]> wrote: | > | > > Hi, | > > i don't know if i've to config something to have a | > > normal accès to a | > > HD of 160GB. | > > | > > I've setted 'hdparm -d0 /dev/hdb' = no DMA; without | > > that couldn't | > > accès the HD. | > > I've also a message 'Warning: could not read block | > > 0: Attempt to | > > read block from filesystem resulted in short read' | > > on a mkfs.ext3 ... | > > | > > And after mounting a partition on it, can't no more | > > unmount it. | > > The activity hd-led remains on. | > > | > > The hd is a western Digital with 2MB cache geometry | > > 19457/255/63 | > > | > > Any help would be very appreciated | > > | > I think most large-disk problems are due to BIOS | > limitations. You need to have LBA48 support, or get a | > controller that provides such support. I'm using a | > 160GB drive right now, with no special precautions. | | You'd have to have a *really* old mobo for it not to have LBA48 | support in 2006. | | I wouldn't be surprised if you aren't having issues with the chipset | driver. | | What mobo do you have, what chipset is in it, and what kernel and | version are you running? kernel-image, kernel-sourse, kernel.org? | Thanks for the reply Ron, Mobo asus P4 kernel-2.6.12. Found the problem: the HD is dead :( best regards mess-mate -- Never laugh at live dragons. -- Bilbo Baggins [J.R.R. Tolkien, "The Hobbit"]
Re: hd 160GB problem
On Fri, 2006-02-10 at 12:59 -0800, Robert Kopp wrote: > > --- mess-mate <[EMAIL PROTECTED]> wrote: > > > Hi, > > i don't know if i've to config something to have a > > normal accès to a > > HD of 160GB. > > > > I've setted 'hdparm -d0 /dev/hdb' = no DMA; without > > that couldn't > > accès the HD. > > I've also a message 'Warning: could not read block > > 0: Attempt to > > read block from filesystem resulted in short read' > > on a mkfs.ext3 ... > > > > And after mounting a partition on it, can't no more > > unmount it. > > The activity hd-led remains on. > > > > The hd is a western Digital with 2MB cache geometry > > 19457/255/63 > > > > Any help would be very appreciated > > > I think most large-disk problems are due to BIOS > limitations. You need to have LBA48 support, or get a > controller that provides such support. I'm using a > 160GB drive right now, with no special precautions. You'd have to have a *really* old mobo for it not to have LBA48 support in 2006. I wouldn't be surprised if you aren't having issues with the chipset driver. What mobo do you have, what chipset is in it, and what kernel and version are you running? kernel-image, kernel-sourse, kernel.org? -- - Ron Johnson, Jr. Jefferson, LA USA "I went home with a waitress the way I always do. How was I to know she was with the Russians, too?"
Re: hd 160GB problem
--- mess-mate <[EMAIL PROTECTED]> wrote: > Hi, > i don't know if i've to config something to have a > normal accès to a > HD of 160GB. > > I've setted 'hdparm -d0 /dev/hdb' = no DMA; without > that couldn't > accès the HD. > I've also a message 'Warning: could not read block > 0: Attempt to > read block from filesystem resulted in short read' > on a mkfs.ext3 ... > > And after mounting a partition on it, can't no more > unmount it. > The activity hd-led remains on. > > The hd is a western Digital with 2MB cache geometry > 19457/255/63 > > Any help would be very appreciated > I think most large-disk problems are due to BIOS limitations. You need to have LBA48 support, or get a controller that provides such support. I'm using a 160GB drive right now, with no special precautions. Robert "Tim" Kopp http://analytic.tripod.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: hd 160GB problem
On Friday 10 February 2006 14:44, mess-mate wrote: >Hi, >i don't know if i've to config something to have a normal accès to a >HD of 160GB. > >I've setted 'hdparm -d0 /dev/hdb' = no DMA; without that couldn't >accès the HD. >I've also a message 'Warning: could not read block 0: Attempt to >read block from filesystem resulted in short read' on a mkfs.ext3 ... > >And after mounting a partition on it, can't no more unmount it. >The activity hd-led remains on. > >The hd is a western Digital with 2MB cache geometry 19457/255/63 > Linux's compatibilty with hard drives is legendary IME. Such activity, or should I say lack of it would make me reboot to the os the drives maintainance utilities on the accompanying cd expects to work with, and run the diagnostics contained on the cd. I'd very nearly bet a bottle of Rock Green Lite (I'm diabetic) that its toasted, and stale toast should be warrantied, or if new, returned for credit against a Seagate with its 5 year warranty. That said, I currently have at least 4 wd's spinning merrily away in this room, some of them over 5 years old. Newest is a 200GBer. >Any help would be very appreciated > >mess-mate -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hd 160GB problem
Hi, i don't know if i've to config something to have a normal accès to a HD of 160GB. I've setted 'hdparm -d0 /dev/hdb' = no DMA; without that couldn't accès the HD. I've also a message 'Warning: could not read block 0: Attempt to read block from filesystem resulted in short read' on a mkfs.ext3 ... And after mounting a partition on it, can't no more unmount it. The activity hd-led remains on. The hd is a western Digital with 2MB cache geometry 19457/255/63 Any help would be very appreciated mess-mate -- You will be singled out for promotion in your work.
