Re: debian wheezy netinst questions

2012-07-28 Thread Jude DaShiell
This situation gets funny, so anyone reading further is warned to be 
sitting on the floor or you'll likely get hurt falling off of your chairs.  
The talking arch linux disk and instructions for installing talking 
archlinux had changed but even with that I managed to get archlinux to 
partition and format the seagate baracooda 7200 1500GB drive I have.  
Since I didn't have the current talking arch disk and the brailled 
instructions I wrote no longer apply, I figure why not roll the dice and 
see if debian will thrash the drive like it did before.  So I start over 
with a debian install and this time no disk thrashing and debian installed 
on the Seagate Baracooda 7200 1500GB drive with no problems.  I find it 
funny when a competing Linux ends up doing a critical part of the job yet 
can't complete an installation and then the original desired Linux finally 
does install on the drive.  Archlinux is a small operating system and I 
have many smaller sata drives I can and will install that system on at a 
later time since small systems work well on small drives.  Larger systems 
need larger drives.



 Hardware 
eventually fails; software eventually works, no amount of band width can 
fix poor design

Jude jdashiel-at-shellworld-dot-net
http://www.shellworld.net/~jdashiel/nj.html


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.01.1207281058020.18...@freire1.furyyjbeyq.arg



Re: debian wheezy netinst questions

2012-07-27 Thread Jude DaShiell
Okay, I forgot to mention that archlinux has no trouble installing on 
that same sata controler and same baracooda drive.  I had been told 
earlier today that Seagate did ship some problem baracooda drives out 
but wasn't told what the problem was with them.  I'll see if I can get a 
replacement drive since this one has some warranty left.

On Wed, 25 Jul 2012, Bob Proulx wrote:

 Jude DaShiell wrote:
  Why won't debian wheezy netinst recognize my Seagate Baracooda 7200 1500gb 
  hard drive automatically?
  Since automatic recognition fails, which if any driver is installed that I 
  can select and get the drive partitioned and formatted and finish a debian 
  installation?
 
 It seems very unusual that such a popular drive such as the Seagate
 Baracuda series would be a problem.  I have several of those on my
 systems without trouble.  More than likely if there is a problem it is
 in the SATA device controller on your motherboard.
 
 I would remove and reconnect all of the disk connections and verify
 that they are okay.  A bad SATA cable connector has been the source of
 problems more than once on this mailing list.  If your motherboard has
 multiple SATA controllers or connectors then I would try a different
 one.
 
 I would boot a live disk and then run 'lspci' and look to see what
 SATA controller is being used and then search for issues concerning
 it.  Also during a live cd boot you should be able to query the drive
 and prove that it is working.  Or not working.  Because it is possible
 that you are simply suffering from a hardware problem and not a
 software problem.
 
 Bob
 


Hardware eventually fails; software eventually works, no amount of band
width can fix poor design

Jude jdashiel-at-shellworld-dot-net
http://www.shellworld.net/~jdashiel/nj.html


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.01.1207271805580.91...@freire1.furyyjbeyq.arg



Re: debian wheezy netinst questions

2012-07-26 Thread Camaleón
On Wed, 25 Jul 2012 20:35:29 -0400, Jude DaShiell wrote:

 Why won't debian wheezy netinst recognize my Seagate Baracooda 7200
 1500gb hard drive automatically?

Because of any fancy disk layout is currently in place? Because of a BIOS 
setting (ide/sata/ahci/raid) making noise? Because of U/EFI present? A 
BIOS/UEFI bug? An unrecognized hard disk controller?

 Since automatic recognition fails, which if any driver is installed that
 I can select and get the drive partitioned and formatted and finish a
 debian installation?

From the installer, you can jump to a debug console to discover why it 
fails to recognize the disk. Also, you can check if the disk if detected 
by loading any LiveCD of your liking.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jurlq0$tcf$9...@dough.gmane.org



debian wheezy netinst questions

2012-07-25 Thread Jude DaShiell
Why won't debian wheezy netinst recognize my Seagate Baracooda 7200 1500gb 
hard drive automatically?
Since automatic recognition fails, which if any driver is installed that I 
can select and get the drive partitioned and formatted and finish a debian 
installation?



 Hardware 
eventually fails; software eventually works, no amount of band width can 
fix poor design

Jude jdashiel-at-shellworld-dot-net
http://www.shellworld.net/~jdashiel/nj.html


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.01.1207252030510.93...@freire1.furyyjbeyq.arg



Re: debian wheezy netinst questions

2012-07-25 Thread Bob Proulx
Jude DaShiell wrote:
 Why won't debian wheezy netinst recognize my Seagate Baracooda 7200 1500gb 
 hard drive automatically?
 Since automatic recognition fails, which if any driver is installed that I 
 can select and get the drive partitioned and formatted and finish a debian 
 installation?

It seems very unusual that such a popular drive such as the Seagate
Baracuda series would be a problem.  I have several of those on my
systems without trouble.  More than likely if there is a problem it is
in the SATA device controller on your motherboard.

I would remove and reconnect all of the disk connections and verify
that they are okay.  A bad SATA cable connector has been the source of
problems more than once on this mailing list.  If your motherboard has
multiple SATA controllers or connectors then I would try a different
one.

I would boot a live disk and then run 'lspci' and look to see what
SATA controller is being used and then search for issues concerning
it.  Also during a live cd boot you should be able to query the drive
and prove that it is working.  Or not working.  Because it is possible
that you are simply suffering from a hardware problem and not a
software problem.

Bob


signature.asc
Description: Digital signature