Second SuSE HDD No Access
I have just powered up a newly assembled ATX box with a cleanly formatted and SUSE 9 Pro loaded 20g Quantum Fireball Plus LM20.5 HDD as Master and a much-used Maxtor 6E040l0 40g HDD as Slave. The Quantum is seen in YaST as hda1, etc., the Maxtor hdb1, etc. I have tried to set up a desktop icon for the Maxtor but get an "in use" error. I have tried to look at the Maxtor from Konq to no avail. I do notice that the Grub device map only shows hd0 and fd0 but fail to understand why YaST would see both HDD's even though Grub appears to see only one (not to mention that the Grub device map fails to list either the CD reader or the cdrw device. Can someone explain these anomalies, and the solution to getting Konq to see my second HDD, please? I could reverse the cables and the jumpers on the two HDD's and see what happens but I really should be able to see them in either order and access the Maxtor from SuSE 9 Pro booted off the Quantum. Given that the Quantum is a clean load of SuSE 9 Pro and the Maxtor was set up on an older box I think that the Quantum should be my Master HDD. -- dmc ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your journey with God continues here ... Trinity College in Tampa Bay, Florida ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dr. David M. Colburn wrote:
I have just powered up a newly assembled ATX box with a cleanly formatted and SUSE 9 Pro loaded 20g Quantum Fireball Plus LM20.5 HDD as Master and a much-used Maxtor 6E040l0 40g HDD as Slave.
The Quantum is seen in YaST as hda1, etc., the Maxtor hdb1, etc.
I have tried to set up a desktop icon for the Maxtor but get an "in use" error.
I have tried to look at the Maxtor from Konq to no avail.
I do notice that the Grub device map only shows hd0 and fd0 but fail to understand why YaST would see both HDD's even though Grub appears to see only one (not to mention that the Grub device map fails to list either the CD reader or the cdrw device.
Can someone explain these anomalies, and the solution to getting Konq to see my second HDD, please?
I could reverse the cables and the jumpers on the two HDD's and see what happens but I really should be able to see them in either order and access the Maxtor from SuSE 9 Pro booted off the Quantum.
Given that the Quantum is a clean load of SuSE 9 Pro and the Maxtor was set up on an older box I think that the Quantum should be my Master HDD.
Before you do anything else, examine dmesg after booting, to see if the 2nd drive was detected. Then check fstab & mtab for that drive.
There are 2 setups that use more than one hard drive, the master/slave system, and the system that Compaq uses--I don't remember its name, but it depends on which plug you use, IIRC, like in floppies. They gave me a Compaq at work, a couple of years ago, and I was never able to hook up 2 hard drives and a CD rom to this miserable piece of crap. One hd, one cd, or 2 hd's, but not both. I wanted to put Linux on the second hd, but of course, IT was not helpful in this regard. I hope your machine is not a Compaq, or if you haven't had it very long, exchange it for something else. Good luck! --doug At 18:26 03/21/2004 -0500, Dr. David M. Colburn wrote:
I have just powered up a newly assembled ATX box with a cleanly formatted and SUSE 9 Pro loaded 20g Quantum Fireball Plus LM20.5 HDD as Master and a much-used Maxtor 6E040l0 40g HDD as Slave.
The Quantum is seen in YaST as hda1, etc., the Maxtor hdb1, etc.
I have tried to set up a desktop icon for the Maxtor but get an "in use" error.
I have tried to look at the Maxtor from Konq to no avail.
I do notice that the Grub device map only shows hd0 and fd0 but fail to understand why YaST would see both HDD's even though Grub appears to see only one (not to mention that the Grub device map fails to list either the CD reader or the cdrw device.
Can someone explain these anomalies, and the solution to getting Konq to see my second HDD, please?
I could reverse the cables and the jumpers on the two HDD's and see what happens but I really should be able to see them in either order and access the Maxtor from SuSE 9 Pro booted off the Quantum.
Given that the Quantum is a clean load of SuSE 9 Pro and the Maxtor was set up on an older box I think that the Quantum should be my Master HDD.
-- dmc ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your journey with God continues here ... Trinity College in Tampa Bay, Florida ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at <http://lists.suse.com/>http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
At 18:26 03/21/2004 -0500, Dr. David M. Colburn wrote:
I have just powered up a newly assembled ATX box with a cleanly formatted and SUSE 9 Pro loaded 20g Quantum Fireball Plus LM20.5 HDD as Master and a much-used Maxtor 6E040l0 40g HDD as Slave.
The Quantum is seen in YaST as hda1, etc., the Maxtor hdb1, etc.
I have tried to set up a desktop icon for the Maxtor but get an "in use" error.
I have tried to look at the Maxtor from Konq to no avail.
I do notice that the Grub device map only shows hd0 and fd0 but fail to understand why YaST would see both HDD's even though Grub appears to see only one (not to mention that the Grub device map fails to list either the CD reader or the cdrw device.
Can someone explain these anomalies, and the solution to getting Konq to see my second HDD, please?
I could reverse the cables and the jumpers on the two HDD's and see what happens but I really should be able to see them in either order and access the Maxtor from SuSE 9 Pro booted off the Quantum.
Given that the Quantum is a clean load of SuSE 9 Pro and the Maxtor was set up on an older box I think that the Quantum should be my Master HDD.
-- dmc ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your journey with God continues here ... Trinity College in Tampa Bay, Florida ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There are 2 setups that use more than one hard drive, the master/slave system, and the system that Compaq uses--I don't remember its name, but it depends on which plug you use, IIRC, like in floppies. They gave me a Compaq at work, a couple of years ago, and I was never able to hook up 2 hard drives and a CD rom to this miserable piece of crap. One hd, one cd, or 2 hd's, but not both. I wanted to put Linux on the second hd, but of course, IT was not helpful in this regard. I hope your machine is not a Compaq, or if you haven't had it very long, exchange it for something else. Good luck! --doug
No, not a Compaq. I have just tried to boot from the Maxtor (SuSE 9 Pro load on an old PC) and it dumps me to a Bash or Bash-like prompt -- but I get errors when I try to load KDE. What is the most common short list of reasons, please, that moving a HDD from an older K2 box to a new Athlon box might cause SuSE/KDE to fail to boot properly when it had been working fine? Thanks! -- dmc ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your journey with God continues here ... Trinity College in Tampa Bay, Florida ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Monday 22 March 2004 03:47, Dr. David M. Colburn wrote:
What is the most common short list of reasons, please, that moving a HDD from an older K2 box to a new Athlon box might cause SuSE/KDE to fail to boot properly when it had been working fine?
The graphics driver
Anders Johansson wrote:
On Monday 22 March 2004 03:47, Dr. David M. Colburn wrote:
What is the most common short list of reasons, please, that moving a HDD from an older K2 box to a new Athlon box might cause SuSE/KDE to fail to boot properly when it had been working fine?
The graphics driver
Perfect! That is all I needed to know. I had been running through various YaST Install-Upgrade and Repair procedures with no useful information until I at last saw something about Nvidia drivers unavailable via SuSE 9. After your note I pulled the Nvidia agp board and replaced it with an old pci card. Ran Sax2 and changed drivers. All is well. Thanks! -- dmc ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your journey with God continues here ... Trinity College in Tampa Bay, Florida ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Sunday 21 March 2004 08:47 pm, Dr. David M. Colburn wrote:
What is the most common short list of reasons, please, that moving a HDD from an older K2 box to a new Athlon box might cause SuSE/KDE to fail to boot properly when it had been working fine?
For a long time making a Maxtor play nice with another brand was real problematic. Seems like Maxtor only liked being hooked up with Maxtor. Just recently I got one to work with a Quantum, which I believe is now made by Maxtor. Never did get WD or other common hd's to work with Maxtor. I guess the real test would be to try each HD alone and if it works by itself, you may have the answer. ra
Hi, all -- And another late post... ...and then Richard Atcheson said... % % On Sunday 21 March 2004 08:47 pm, Dr. David M. Colburn wrote: % > What is the most common short list of reasons, please, that % > moving a HDD from an older K2 box to a new Athlon box might % > cause SuSE/KDE to fail to boot properly when it had been % > working fine? % % For a long time making a Maxtor play nice with another brand was real % problematic. Seems like Maxtor only liked being hooked up with Maxtor. I've happily mixed Maxtor, Quantum, Seagate, and Western Digital for years. Of course, I never tried to use each vendor's drive setup software, which could have been a part of it. A current example: root@canal:/root # uname -a Linux canal 2.4.20 #8 SMP Sat Apr 12 12:32:39 EDT 2003 i686 unknown root@canal:/root # dmesg | grep hd ide0: BM-DMA at 0xe400-0xe407, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xe408-0xe40f, BIOS settings: hdc:pio, hdd:pio hda: Maxtor 6Y120L0, ATA DISK drive hdc: WDC WD1600JB-00FUA0, ATA DISK drive hda: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=254097/15/63, UDMA(33) hdc: 312581808 sectors (160042 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(33) hda: hda1 hda2 hda3 hda4 < hda5 > hdc: hdc1 hdc2 hdc3 hdc4 < hdc5 > HTH & HAND :-D -- David T-G davidtg@justpickone.org http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The Sunday 2004-03-21 at 21:47 -0500, Dr. David M. Colburn wrote:
I have just tried to boot from the Maxtor (SuSE 9 Pro load on an old PC) and it dumps me to a Bash or Bash-like prompt -- but I get errors when I try to load KDE.
That's probably the grub console, and it is expecting you to input commands to do a manual boot. Read grub's manual.
What is the most common short list of reasons, please, that moving a HDD from an older K2 box to a new Athlon box might cause SuSE/KDE to fail to boot properly when it had been working fine?
If the disk is in the same position (same device name) it should normally boot - except if the kernel is for a diferent processor, and also, the video card is different. -- Cheers, Carlos Robinson
At 21:47 03/21/2004 -0500, Dr. David M. Colburn wrote:
At 18:26 03/21/2004 -0500, Dr. David M. Colburn wrote:
I have just powered up a newly assembled ATX box with a cleanly formatted and SUSE 9 Pro loaded 20g Quantum Fireball Plus LM20.5 HDD as Master and a much-used Maxtor 6E040l0 40g HDD as Slave.
The Quantum is seen in YaST as hda1, etc., the Maxtor hdb1, etc.
I have tried to set up a desktop icon for the Maxtor but get an "in use" error.
I have tried to look at the Maxtor from Konq to no avail.
I do notice that the Grub device map only shows hd0 and fd0 but fail to understand why YaST would see both HDD's even though Grub appears to see only one (not to mention that the Grub device map fails to list either the CD reader or the cdrw device.
Can someone explain these anomalies, and the solution to getting Konq to see my second HDD, please?
I could reverse the cables and the jumpers on the two HDD's and see what happens but I really should be able to see them in either order and access the Maxtor from SuSE 9 Pro booted off the Quantum.
Given that the Quantum is a clean load of SuSE 9 Pro and the Maxtor was set up on an older box I think that the Quantum should be my Master HDD.
-- dmc
my last reply deleted --doug ************************
No, not a Compaq.
I have just tried to boot from the Maxtor (SuSE 9 Pro load on an old PC) and it dumps me to a Bash or Bash-like prompt -- but I get errors when I try to load KDE.
What is the most common short list of reasons, please, that moving a HDD from an older K2 box to a new Athlon box might cause SuSE/KDE to fail to boot properly when it had been working fine?
Thanks!
The boot process on your old drive is trying to access different peripherals than it saw before, and it's getting errors--that's my best guess. You have the same problem with any operating system. That's why they tell you to turn off all your Windows drivers before you make a move like this, and let Windows find the new hardware. I don't know how you do that in Linux, but that still doesn't explain why you can't access the drive when it's set up as a slave. Someone else may know. --doug
-- dmc ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your journey with God continues here ... Trinity College in Tampa Bay, Florida ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at <http://lists.suse.com/>http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Doug, et al -- A bit late in the thread, I know, but I didn't see this covered... ...and then Doug McGarrett said... % % There are 2 setups that use more than one hard drive, the % master/slave system, and the system that Compaq uses--I % don't remember its name, but it depends on which plug you % use, IIRC, like in floppies. They gave me a Compaq at work, Actually, they are both master/slave, but the one that depends on cable position is "cable select". The problem happens when you have one drive forced to master (or slave) and the other drive, obediently selecting based on position, tries to be the same thing. % a couple of years ago, and I was never able to hook up 2 % hard drives and a CD rom to this miserable piece of crap. Well, it is a Compaq, so that's an accurate description, but it doesn't have to be that bad :-) If you're ever in that position again, just have a look at the jumpers on the back of each drive. HTH & HAND :-D -- David T-G davidtg@justpickone.org http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
On Tuesday 06 April 2004 11:13 am, David T-G wrote:
Actually, they are both master/slave, but the one that depends on cable position is "cable select". The problem happens when you have one drive forced to master (or slave) and the other drive, obediently selecting based on position, tries to be the same thing.
% a couple of years ago, and I was never able to hook up 2 % hard drives and a CD rom to this miserable piece of crap.
Well, it is a Compaq, so that's an accurate description, but it doesn't have to be that bad :-) If you're ever in that position again, just have a look at the jumpers on the back of each drive.
CS may well be the way to go to get Maxtor to play with other drives. Just recently, my brother got a big maxtor to play with a big WD using cs. When doing master/slave setup it's sometimes easier to place the disimilar drives on separate controllers. I'll remember to try cs next time. I wont ever have Compaq problems again! I've learned my lesson well! RA
On Monday 22 March 2004 00:26, Dr. David M. Colburn wrote:
I have just powered up a newly assembled ATX box with a cleanly formatted and SUSE 9 Pro loaded 20g Quantum Fireball Plus LM20.5 HDD as Master and a much-used Maxtor 6E040l0 40g HDD as Slave.
The Quantum is seen in YaST as hda1, etc., the Maxtor hdb1, etc.
I have tried to set up a desktop icon for the Maxtor but get an "in use" error.
I have tried to look at the Maxtor from Konq to no avail.
I do notice that the Grub device map only shows hd0 and fd0 but fail to understand why YaST would see both HDD's even though Grub appears to see only one (not to mention that the Grub device map fails to list either the CD reader or the cdrw device.
Can someone explain these anomalies, and the solution to getting Konq to see my second HDD, please?
Grub doesn't enter into it, it's only concerned with things you boot from, and the device map is only in case you want to force the device order to be something other than what the BIOS reports. What exactly did you do with the icon you tried to create to get that error message? What is the output from 'cat /proc/mounts' ? What does your fstab look like? What does 'fdisk -l /dev/hdb' look like?
The Sunday 2004-03-21 at 18:26 -0500, Dr. David M. Colburn wrote:
I have just powered up a newly assembled ATX box with a cleanly formatted and SUSE 9 Pro loaded 20g Quantum Fireball Plus LM20.5 HDD as Master and a much-used Maxtor 6E040l0 40g HDD as Slave.
The Quantum is seen in YaST as hda1, etc., the Maxtor hdb1, etc.
I have tried to set up a desktop icon for the Maxtor but get an "in use" error.
Then it is already mounted and seen, therefore, "in use".
I have tried to look at the Maxtor from Konq to no avail.
I do notice that the Grub device map only shows hd0 and fd0 but fail to understand why YaST would see both HDD's even though Grub appears to see only one (not to mention that the Grub device map fails to list either the CD reader or the cdrw device.
You are confusing things. Grub is for booting the system, has nothing to do with desktop icons or disk access. Post the output of the "mount" command, and the contens of the /etc/fstab file. -- Cheers, Carlos Robinson
participants (7)
-
Anders Johansson -
Carlos E. R. -
David T-G -
Doug McGarrett -
Dr. David M. Colburn -
James Knott -
Richard Atcheson