LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 10-24-2014, 02:07 PM   #1
Miranden
Member
 
Registered: May 2012
Distribution: Slackware 64 14.1
Posts: 211

Rep: Reputation: 20
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.
 
Old 10-24-2014, 02:12 PM   #2
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,838

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
Have you checked dmesg or /var/log/messages?
 
1 members found this post helpful.
Old 10-24-2014, 02:15 PM   #3
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,258

Rep: Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947
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
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-431.23.3.el6.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Black
Device Model:     WDC WD6401AALS-00L3B2
Serial Number:    WD-WCASY4000673
LU WWN Device Id: 5 0014ee 2ad223d57
Firmware Version: 01.03B01
User Capacity:    640,135,028,736 bytes [640 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Fri Oct 24 12:16:05 2014 MDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84)	Offline data collection activity
					was suspended by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(12000) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 140) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x303f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   163   162   021    Pre-fail  Always       -       4816
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       121
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   048   048   000    Old_age   Always       -       38465
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       119
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       53
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       121
194 Temperature_Celsius     0x0022   111   100   000    Old_age   Always       -       36
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   186   186   000    Old_age   Always       -       1465
198 Offline_Uncorrectable   0x0030   187   186   000    Old_age   Offline      -       1458
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   001   001   000    Old_age   Offline      -       27012

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
And here is the output of a failing drive:
Code:
# smartctl -a /dev/sdc
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-431.23.3.el6.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11
Device Model:     ST31500341AS
Serial Number:    9VS1M25C
LU WWN Device Id: 5 000c50 014915305
Firmware Version: CC1H
User Capacity:    1,500,301,910,016 bytes [1.50 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri Oct 24 12:14:53 2014 MDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  617) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 297) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x103f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   120   099   006    Pre-fail  Always       -       243343290
  3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       117
  5 Reallocated_Sector_Ct   0x0033   015   015   036    Pre-fail  Always   FAILING_NOW 3504
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       240786188
  9 Power_On_Hours          0x0032   047   047   000    Old_age   Always       -       46459
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       117
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   018   018   000    Old_age   Always       -       82
190 Airflow_Temperature_Cel 0x0022   062   040   045    Old_age   Always   In_the_past 38 (0 9 38 33 0)
194 Temperature_Celsius     0x0022   038   060   000    Old_age   Always       -       38 (0 17 0 0 0)
195 Hardware_ECC_Recovered  0x001a   041   023   000    Old_age   Always       -       243343290
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       1
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       263079631828346
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       1243531508
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2290119712

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Notice the high reallocated sector count and the FAILING_NOW status.

Last edited by suicidaleggroll; 10-24-2014 at 02:16 PM.
 
1 members found this post helpful.
Old 10-24-2014, 02:26 PM   #4
Miranden
Member
 
Registered: May 2012
Distribution: Slackware 64 14.1
Posts: 211

Original Poster
Rep: Reputation: 20
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
smartctl 6.2 2013-07-26 r3841 [i686-linux-3.13.0-37-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Blue Serial ATA
Device Model:     WDC WD800AAJS-22PSA0
Serial Number:    WD-WCAP98129821
LU WWN Device Id: 5 0014ee 1ab6502cc
Firmware Version: 05.06H05
User Capacity:    80,026,361,856 bytes [80.0 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-7 (minor revision not indicated)
Local Time is:    Fri Oct 24 14:21:04 2014 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84)	Offline data collection activity
					was suspended by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		( 1980) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  30) minutes.
Conveyance self-test routine
recommended polling time: 	 (   6) minutes.
SCT capabilities: 	       (0x103f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   200   198   051    Pre-fail  Always       -       542
  3 Spin_Up_Time            0x0003   163   159   021    Pre-fail  Always       -       2850
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1413
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000e   200   200   051    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   087   087   000    Old_age   Always       -       9870
 10 Spin_Retry_Count        0x0012   100   100   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0012   100   100   051    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       1413
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       609
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1413
194 Temperature_Celsius     0x0022   105   088   000    Old_age   Always       -       38
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   051    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 540 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 540 occurred at disk power-on lifetime: 2370 hours (98 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 64 18 45 40  Error: UNC at LBA = 0x00451864 = 4528228

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 60 38 a0 18 45 00 08      01:54:31.792  READ FPDMA QUEUED
  60 40 30 60 18 45 00 08      01:54:31.792  READ FPDMA QUEUED
  60 88 28 e0 08 4a 00 08      01:54:31.792  READ FPDMA QUEUED
  60 48 20 70 09 4a 00 08      01:54:31.792  READ FPDMA QUEUED
  60 b8 18 d0 09 4a 00 08      01:54:31.792  READ FPDMA QUEUED

Error 539 occurred at disk power-on lifetime: 2370 hours (98 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 64 18 45 40  Error: UNC at LBA = 0x00451864 = 4528228

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 10 38 50 20 37 00 08      01:54:29.770  READ FPDMA QUEUED
  60 18 30 f8 10 37 00 08      01:54:29.770  READ FPDMA QUEUED
  60 70 28 90 0a 4a 00 08      01:54:29.769  READ FPDMA QUEUED
  60 b8 20 d0 09 4a 00 08      01:54:29.769  READ FPDMA QUEUED
  60 48 18 70 09 4a 00 08      01:54:29.769  READ FPDMA QUEUED

Error 538 occurred at disk power-on lifetime: 2370 hours (98 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 64 18 45 40  Error: UNC at LBA = 0x00451864 = 4528228

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 60 38 a0 18 45 00 08      01:54:27.747  READ FPDMA QUEUED
  60 40 30 60 18 45 00 08      01:54:27.747  READ FPDMA QUEUED
  60 88 28 e0 08 4a 00 08      01:54:27.746  READ FPDMA QUEUED
  60 48 20 70 09 4a 00 08      01:54:27.746  READ FPDMA QUEUED
  60 b8 18 d0 09 4a 00 08      01:54:27.746  READ FPDMA QUEUED

Error 537 occurred at disk power-on lifetime: 2370 hours (98 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 64 18 45 40  Error: UNC at LBA = 0x00451864 = 4528228

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 10 38 50 20 37 00 08      01:54:25.724  READ FPDMA QUEUED
  60 18 30 f8 10 37 00 08      01:54:25.724  READ FPDMA QUEUED
  60 70 28 90 0a 4a 00 08      01:54:25.724  READ FPDMA QUEUED
  60 b8 20 d0 09 4a 00 08      01:54:25.723  READ FPDMA QUEUED
  60 48 18 70 09 4a 00 08      01:54:25.723  READ FPDMA QUEUED

Error 536 occurred at disk power-on lifetime: 2370 hours (98 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 64 18 45 40  Error: UNC at LBA = 0x00451864 = 4528228

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 60 50 a0 18 45 00 08      01:54:23.676  READ FPDMA QUEUED
  60 40 48 60 18 45 00 08      01:54:23.676  READ FPDMA QUEUED
  60 10 40 80 93 44 00 08      01:54:23.676  READ FPDMA QUEUED
  60 88 38 e0 08 4a 00 08      01:54:23.676  READ FPDMA QUEUED
  60 48 30 70 09 4a 00 08      01:54:23.676  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 
Old 10-24-2014, 02:29 PM   #5
Miranden
Member
 
Registered: May 2012
Distribution: Slackware 64 14.1
Posts: 211

Original Poster
Rep: Reputation: 20
Sorry, cross posted with your edit showing the examples. My drive does not have those elements. So it's good?
 
Old 10-24-2014, 02:34 PM   #6
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,258

Rep: Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947Reputation: 1947
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.

Last edited by suicidaleggroll; 10-24-2014 at 02:37 PM.
 
1 members found this post helpful.
Old 10-24-2014, 02:45 PM   #7
Miranden
Member
 
Registered: May 2012
Distribution: Slackware 64 14.1
Posts: 211

Original Poster
Rep: Reputation: 20
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.
 
Old 10-24-2014, 04:01 PM   #8
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,838

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
The command would be
Quote:
cat /var/log/messages |less
 
Old 10-24-2014, 04:53 PM   #9
Miranden
Member
 
Registered: May 2012
Distribution: Slackware 64 14.1
Posts: 211

Original Poster
Rep: Reputation: 20
Quote:
Originally Posted by EDDY1 View Post
The command would be
Honestly, it isn't there.

Code:
root@northstar:/home# cat /var/log/messages | less
cat: /var/log/messages: No such file or directory
I assumed it was an Ubuntu thing.
 
Old 10-24-2014, 06:33 PM   #10
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,838

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
cd /var/log
ls
 
Old 10-25-2014, 01:04 AM   #11
Miranden
Member
 
Registered: May 2012
Distribution: Slackware 64 14.1
Posts: 211

Original Poster
Rep: Reputation: 20
Code:
root@northstar:~$ cd /var/log
root@northstar:/var/log$ ls
alternatives.log    bootstrap.log   gpu-manager.log     syslog.3.gz
alternatives.log.1  btmp            hp                  syslog.4.gz
apport.log          btmp.1          installer           syslog.5.gz
apport.log.1        ConsoleKit      kern.log            syslog.6.gz
apport.log.2.gz     cups            kern.log.1          syslog.7.gz
apport.log.3.gz     dist-upgrade    kern.log.2.gz       udev
apport.log.4.gz     dmesg           kern.log.3.gz       unattended-upgrades
apport.log.5.gz     dmesg.0         kern.log.4.gz       upstart
apport.log.6.gz     dmesg.1.gz      lastlog             wtmp
apport.log.7.gz     dmesg.2.gz      lightdm             wtmp.1
apt                 dmesg.3.gz      pm-powersave.log    Xorg.0.log
auth.log            dmesg.4.gz      pm-powersave.log.1  Xorg.0.log.old
auth.log.1          dpkg.log        samba               Xorg.1.log
auth.log.2.gz       dpkg.log.1      speech-dispatcher   Xorg.1.log.old
auth.log.3.gz       faillog         syslog
auth.log.4.gz       fontconfig.log  syslog.1
boot.log            fsck            syslog.2.gz
root@northstar:/var/log$
 
Old 10-25-2014, 03:19 AM   #12
EDDY1
LQ Addict
 
Registered: Mar 2010
Location: Oakland,Ca
Distribution: wins7, Debian wheezy
Posts: 6,838

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
cat /var/log/syslog
 
Old 10-25-2014, 12:20 PM   #13
Miranden
Member
 
Registered: May 2012
Distribution: Slackware 64 14.1
Posts: 211

Original Poster
Rep: Reputation: 20
Attached.
Attached Files
File Type: txt syslog.txt (200.2 KB, 5 views)
 
Old 10-25-2014, 12:40 PM   #14
kilgoretrout
Senior Member
 
Registered: Oct 2003
Posts: 2,472

Rep: Reputation: 189Reputation: 189
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.
 
Old 10-25-2014, 01:27 PM   #15
Miranden
Member
 
Registered: May 2012
Distribution: Slackware 64 14.1
Posts: 211

Original Poster
Rep: Reputation: 20
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
java takes very long time abd_bela Programming 4 01-09-2012 08:34 AM
GDM takes a *long* time to start first time grumpybuffalo Linux From Scratch 2 09-09-2007 01:17 PM
Login takes a very long time Jensens Linux - Networking 2 03-23-2006 04:24 AM
login takes long time doorman007 Linux - Software 2 04-25-2005 01:56 AM
Bzipping takes a really long time sometimes scott_R General 0 10-10-2004 01:47 AM


All times are GMT -5. The time now is 02:18 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration