Difference between revisions of "Hardware Issues History"
From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search (→6/2007) |
(→6/2007) |
||
| Line 3: | Line 3: | ||
* '''SMP, Power''': Taro was only able to run the single-processor kernel, despite having two processors. When taro's power supply was replaced with a better one capable of delivering more power on the necessary lines, taro was able to run the symmetric multiprocessing kernel. The old powersupply was most likely damaged in a power event. It may have been too low a rating to begin with. | * '''SMP, Power''': Taro was only able to run the single-processor kernel, despite having two processors. When taro's power supply was replaced with a better one capable of delivering more power on the necessary lines, taro was able to run the symmetric multiprocessing kernel. The old powersupply was most likely damaged in a power event. It may have been too low a rating to begin with. | ||
* '''SMP''': Gourd was running on just one CPU, despite having two. This was solved by simply telling GRUB to boot the symmetric multiprocessing Linux kernel, which was not the default. Booting gives a warning that RHEL4 Desktop doesn't support more than one CPU. It seems to work with both active, however. We'll need to investigate it further when we begin the distant transition to RHEL5 so that all CPUs work fully, warning-free. | * '''SMP''': Gourd was running on just one CPU, despite having two. This was solved by simply telling GRUB to boot the symmetric multiprocessing Linux kernel, which was not the default. Booting gives a warning that RHEL4 Desktop doesn't support more than one CPU. It seems to work with both active, however. We'll need to investigate it further when we begin the distant transition to RHEL5 so that all CPUs work fully, warning-free. | ||
| − | * '''Odd Behavior''': We noticed Perl scripts on Lentil failing in mysterious ways, which led to our finding a /usr/bin/perl of size 0. After checking the logs, we decided that it wasn't done intentionally, and reinstalled Perl. Later, we couldn't boot lentil. Investigation led us to a /boot/grub/grub.conf of size 0. We decided to do a <code> | + | * '''Odd Behavior''': We noticed Perl scripts on Lentil failing in mysterious ways, which led to our finding a /usr/bin/perl of size 0. After checking the logs, we decided that it wasn't done intentionally, and reinstalled Perl. Later, we couldn't boot lentil. Investigation led us to a /boot/grub/grub.conf of size 0. We decided to do a <code>find -size 0 -print</code> and got a large list of files of size 0. We decided that lentil's installation drive must be going bad, and took it as an opportunity to install RedHat EL5 on another drive. |
Revision as of 20:16, 27 June 2007
6/2007
- RAIDS: A hard drive in gourd's RAID went bad and the array was labeled as "degraded." Around the same time, various login issues appeared, such as long wait times between username and password prompting, and password authentication failing for users. When the drive was replaced, not only was the array fixable, but these other issues went away.
- SMP, Power: Taro was only able to run the single-processor kernel, despite having two processors. When taro's power supply was replaced with a better one capable of delivering more power on the necessary lines, taro was able to run the symmetric multiprocessing kernel. The old powersupply was most likely damaged in a power event. It may have been too low a rating to begin with.
- SMP: Gourd was running on just one CPU, despite having two. This was solved by simply telling GRUB to boot the symmetric multiprocessing Linux kernel, which was not the default. Booting gives a warning that RHEL4 Desktop doesn't support more than one CPU. It seems to work with both active, however. We'll need to investigate it further when we begin the distant transition to RHEL5 so that all CPUs work fully, warning-free.
- Odd Behavior: We noticed Perl scripts on Lentil failing in mysterious ways, which led to our finding a /usr/bin/perl of size 0. After checking the logs, we decided that it wasn't done intentionally, and reinstalled Perl. Later, we couldn't boot lentil. Investigation led us to a /boot/grub/grub.conf of size 0. We decided to do a
find -size 0 -printand got a large list of files of size 0. We decided that lentil's installation drive must be going bad, and took it as an opportunity to install RedHat EL5 on another drive.
