fdisk -l takes a REALLY long time; is this hardware related?
Hi,
On a media center desktop machine running Xubuntu, I'm noticing that fdisk -l takes a very long time--as in several minutes--to produce an output. Every other command I have entered is processed immediately. This is just a standalone machine without any complicated networked file systems or anything like that. Could this be a sign of hardware failure? If so, in what components? Thank you in advance. |
Have you checked dmesg or /var/log/messages?
|
In my experience that's usually caused by a failing hard drive. You can check the SMART results of any attached drive with smartctl -a <device>.
For example, here is the output of a healthy drive: Code:
# smartctl -a /dev/sda Code:
# smartctl -a /dev/sdc |
EDDY1 - There is nothing about it in dmesg, and I actually did try /var/log/messages, but apparently Xubuntu doesn't have it. I usually run Slackware . . . that's why I posted in the newbie section, because with Ubuntu, I guess I am one. What happened to /var/log/messages?
suicidaleggroll - I just installed smartmontools and ran the test, but I don't know how to read it. I will try to figure it out and post back. Here is the output, if you are interested: Code:
smartctl -a /dev/sda |
Sorry, cross posted with your edit showing the examples. My drive does not have those elements. So it's good?
|
I don't see anything suspicious in that output. The power-on time is barely over a year, no reallocated sectors. There are 540 logged errors, but they're from long ago (the most recent one was at power-on hour 2370, when you're currently at 9870).
Despite no errors in the SMART results, the drive could still have a physical problem though. |
This computer uses external storage for most things (like I said, it is a media-dedicated machine), but I disconnected the external drives before running the command. The drive that is left is a very old 80 GB internal drive that the OS is installed on. It has lasted at least ten years, probably more. I guess I should try to track down the manufacturer's scan utility? Is there another way to see if it has issues?
What else could be causing the fdisk delay? Actually, the first time I ran it it did produce output after a long time, but I tried it again and hung for 20 minutes. Ctrl+C and Ctrl+Z would not even kill it. I had to use kill -9 on it. |
The command would be
Quote:
|
Quote:
Code:
root@northstar:/home# cat /var/log/messages | less |
cd /var/log
ls |
Code:
root@northstar:~$ cd /var/log |
cat /var/log/syslog
|
1 Attachment(s)
Attached.
|
Just a quick look, but I saw a lot of floppy drive I/O errors(fd0). You might try disconnecting your floppy drive and see if the fdisk problem improves.
|
I don't actually have a floppy drive. Why does it think I do? Does the kernel get this information from the BIOS? If so I can check the configuration there.
|
All times are GMT -5. The time now is 11:54 PM. |