LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
Reload this Page [SOLVED] Hard Drive won't mount, fsck didn't fix it
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 06-19-2020, 03:32 PM   #1
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 337
Blog Entries: 2

Rep: Reputation: 39
Unhappy Hard Drive won't mount, fsck didn't fix it

Hey all. I've got a hard drive that I can't get into. It's where /home is(was) mounted, so I still have access to the system. I'll attach a full log, with highlights here.

Code:
# mount /dev/sdb1 /home
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
bash-4.3# dmesg | tail
[  666.452010] ata7.00: status: { DRDY ERR }
[  666.452013] ata7.00: error: { UNC }
[  666.554514] ata7.00: configured for UDMA/133
[  666.554534] sd 6:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 dri
verbyte=0x08
[  666.554540] sd 6:0:0:0: [sdb] tag#0 Sense Key : 0x3 [current] [descriptor] 
[  666.554544] sd 6:0:0:0: [sdb] tag#0 ASC=0x11 ASCQ=0x4 
[  666.554549] sd 6:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 08 08 00 00 
08 00
[  666.554553] blk_update_request: I/O error, dev sdb, sector 2056
[  666.554576] ata7: EH complete
[  666.554688] EXT4-fs (sdb1): can't read group descriptor 0
Ok, let's try fsck:
Code:
# fsck /dev/sdb1
fsck from util-linux 2.27.1
e2fsck 1.43.1 (08-Jun-2016)
/sbin/e2fsck: Attempt to read block from filesystem resulted in short read while
 trying to open /dev/sdb1
Could this be a zero-length partition?
Def not zero-length, it's got all my user files in it. fdisk can see it:
Code:
# fdisk -l
Disk /dev/sdc: 74.5 GiB, 80000000000 bytes, 156250000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e618f55

Device     Boot    Start       End   Sectors  S
ize Id Type
/dev/sdc1           2048  31250431  31248384 14.9G 82 Linux swap
/dev/sdc2       31250432 156248063 124997632 59.6G 83 Linux


Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa4b57300

Device     Boot Start       End   Sectors   Siz
e Id Type
/dev/sdb1        2048 976773167 976771120 465.8G 83 Linux
Those are my two linux disks, / is the first one and /home is the second. Ok fine, I'll run fsck to copy over whatever bad superblocks it finds:
Code:
# e2fsck -b 32768 /dev/sdb1
e2fsck 1.43.1 (08-Jun-2016)
/dev/sdb1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 87556187 (Attempt to read block from filesystem resulted in 
short read) while getting next inode from scan.  Ignore error<y>? yes
Force rewrite<y>? yes
...
/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: 210795/30531584 files (1.3% non-contiguous), 30718932/122096390 blocks
Those dots indicate many many lines of changes. After a restart.....no change to any of those commands.

It's not really a matter of data recovery, since I do weekly backups. I just wanted to know if anyone has any thoughts before I try something like repartitioning/reformat with fdisk - and also if people think that's unlikely and the drive is totally unusable.
Attached Files
File Type: txt logfile.txt (130.8 KB, 18 views)
 
Old 06-19-2020, 04:17 PM   #2
fatmac
LQ Guru
 
Registered: Sep 2011
Location: Upper Hale, Surrey/Hants Border, UK
Distribution: One main distro, & some smaller ones casually.
Posts: 5,744

Rep: Reputation: Disabled
Maybe copy in a back up super block(?).
 
1 members found this post helpful.
Old 06-19-2020, 04:33 PM   #3
michaelk
Moderator
 
Registered: Aug 2002
Posts: 26,459

Rep: Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216
Check the drive's SMART status via smartctl. I suspect the drive is failing.
 
1 members found this post helpful.
Old 06-19-2020, 05:35 PM   #4
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 337

Original Poster
Blog Entries: 2

Rep: Reputation: 39
Quote:
Originally Posted by fatmac View Post
Maybe copy in a back up super block(?).
My understand is that is what I did:
Code:
# mke2fs -n /dev/sdb1
mke2fs 1.43.1 (08-Jun-2016)
/dev/sdb1 contains `Linux rev 1.0 ext4 filesystem data, UUID=35c21650-fbef-4fe7-8225-df5ae7776c5d (extents) (large files) (huge files)' data
Proceed anyway? (y,n) y
Creating filesystem with 122096390 4k blocks and 30531584 inodes
Filesystem UUID: 91fe8d4e-2883-4fac-9379-bde45a960e33
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
	102400000
 
Old 06-19-2020, 05:36 PM   #5
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 337

Original Poster
Blog Entries: 2

Rep: Reputation: 39
Quote:
Originally Posted by michaelk View Post
Check the drive's SMART status via smartctl. I suspect the drive is failing.
Good call, but it "PASSED" an overall health assessment. I don't know what I'm looking for, but at the end it looks like it's maybe not doing any testing?

Code:
# smartctl -a /dev/sdb 
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.14] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11
Device Model:     ST3500820AS
Serial Number:    9QM3TRRQ
LU WWN Device Id: 5 000c50 00cd7589b
Firmware Version: SD81
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Fri Jun 19 17:21:43 2020 EDT

==> WARNING: There are known problems with these drives,
THIS DRIVE MAY OR MAY NOT BE AFFECTED,
see the following web pages for details:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/207951en
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632758

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
See vendor-specific Attribute list for marginal 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: 		(  642) 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: 	 ( 118) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x103b)	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   084   084   006    Pre-fail  Always       -       133767011
  3 Spin_Up_Time            0x0003   092   084   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   072   072   020    Old_age   Always       -       28744
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       1254
  7 Seek_Error_Rate         0x000f   070   060   030    Pre-fail  Always       -       34445268212
  9 Power_On_Hours          0x0032   026   026   000    Old_age   Always       -       65040
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       51
 12 Power_Cycle_Count       0x0032   098   037   020    Old_age   Always       -       2878
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       1676
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       55835623440
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   070   040   045    Old_age   Always   In_the_past 30 (0 45 30 26 0)
194 Temperature_Celsius     0x0022   030   060   000    Old_age   Always       -       30 (0 12 0 0 0)
195 Hardware_ECC_Recovered  0x001a   030   022   000    Old_age   Always       -       133767011
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       30
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       30
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1703 (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 1703 occurred at disk power-on lifetime: 65040 hours (2710 days + 0 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 0a 08 00 00  Error: UNC at LBA = 0x0000080a = 2058

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 08 08 00 e0 00      02:38:07.557  READ DMA
  27 00 00 00 00 00 e0 00      02:38:07.556  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      02:38:07.553  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      02:38:07.550  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      02:38:07.534  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 1702 occurred at disk power-on lifetime: 65040 hours (2710 days + 0 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 0a 08 00 00  Error: UNC at LBA = 0x0000080a = 2058

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 08 08 00 e0 00      02:38:04.494  READ DMA
  c8 00 08 00 08 00 e0 00      02:38:04.494  READ DMA
  25 00 08 ff ff ff ef 00      02:38:04.492  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:38:04.479  READ DMA EXT
  ea 00 00 ff ff ff af 00      02:38:03.909  FLUSH CACHE EXT

Error 1701 occurred at disk power-on lifetime: 65040 hours (2710 days + 0 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      02:37:19.372  READ DMA EXT
  27 00 00 00 00 00 e0 00      02:37:19.371  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      02:37:19.368  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      02:37:19.365  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      02:37:19.349  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 1700 occurred at disk power-on lifetime: 65040 hours (2710 days + 0 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      02:37:16.373  READ DMA EXT
  27 00 00 00 00 00 e0 00      02:37:16.372  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      02:37:16.369  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      02:37:16.367  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      02:37:16.350  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 1699 occurred at disk power-on lifetime: 65040 hours (2710 days + 0 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      02:37:11.601  READ DMA EXT
  27 00 00 00 00 00 e0 00      02:37:11.600  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      02:37:11.597  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      02:37:11.594  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      02:37:11.577  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     47040         -
# 2  Short offline       Completed without error       00%     47040         -
# 3  Short offline       Completed without error       00%        72         -

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 06-19-2020, 06:06 PM   #6
michaelk
Moderator
 
Registered: Aug 2002
Posts: 26,459

Rep: Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216Reputation: 6216
Well, that might be true but there are a few leading indicators that say its not doing all that well.
Code:
ATA Error Count: 1703 (device log contains only the most recent five errors)

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       1254
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       51
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       1676
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       55835623440
https://en.wikipedia.org/wiki/S.M.A.R.T.

You also might want to go through the Seagate website too.
==> WARNING: There are known problems with these drives,
THIS DRIVE MAY OR MAY NOT BE AFFECTED,
see the following web pages for details:
http://knowledge.seagate.com/article...S/FAQ/207931en
http://knowledge.seagate.com/article...S/FAQ/207951en
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632758
Last edited by michaelk; 06-19-2020 at 06:11 PM.
 
1 members found this post helpful.
Old 06-20-2020, 06:47 AM   #7
fatmac
LQ Guru
 
Registered: Sep 2011
Location: Upper Hale, Surrey/Hants Border, UK
Distribution: One main distro, & some smaller ones casually.
Posts: 5,744

Rep: Reputation: Disabled
Quote:
Originally Posted by thethinker View Post
My understand is that is what I did:
Sorry, my mistake, I missed that you actually installed a new super block.
Last edited by fatmac; 06-20-2020 at 06:51 AM.
 
Old 06-21-2020, 10:54 PM   #8
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 337

Original Poster
Blog Entries: 2

Rep: Reputation: 39
Thanks for ideas everyone, I'm gonna trash it, pull from the back up a few days ago.
 
Old 06-22-2020, 09:31 AM   #9
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 337

Original Poster
Blog Entries: 2

Rep: Reputation: 39
Quote:
Originally Posted by michaelk View Post
Well, that might be true but there are a few leading indicators that say its not doing all that well.
Code:
ATA Error Count: 1703 (device log contains only the most recent five errors)

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       1254
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       51
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       1676
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       55835623440
https://en.wikipedia.org/wiki/S.M.A.R.T.

You also might want to go through the Seagate website too.
==> WARNING: There are known problems with these drives,
THIS DRIVE MAY OR MAY NOT BE AFFECTED,
see the following web pages for details:
http://knowledge.seagate.com/article...S/FAQ/207931en
http://knowledge.seagate.com/article...S/FAQ/207951en
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632758
Wow the Wikipedia site was unexpectedly technical - it actually discusses each of those attributes. Thanks!

This, combined with the fact that running Hard Drive Sentinel (under Windows) was not able to work with the drive at all, lead me to the conclusion that I need to give up, get a new drive and copy from backup.

[I did check out the links, and they are basically unrelated]

Thanks all!
 
Old 06-27-2020, 05:11 AM   #10
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,211

Rep: Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538Reputation: 2538
Agree a new drive is required.

I have persisted with drives in poor condition in the past, but what you find is that whereas only certain sectors are marked bad, sectors in the vicinity are in very poor shape and die quickly. So your backup really becomes your drive. I have a rather extreme example of this - a 16G microsd card where everything set to write/read on it pukes. It's only value is in causing frustration.
 
2 members found this post helpful.
  


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
How long will Fsck take to fix my flash drive? -- vfat drive, Fedora 20 computer. People'spoet Linux - Software 4 05-21-2014 05:54 AM
FSCK or similar help please. Must fix corrupted drive. AbeFM Linux - Hardware 11 12-19-2012 03:56 AM
ext4 won't mount - fsck required - 2nd fsck in less than a week td3201 Linux - General 1 09-10-2012 01:07 AM
Removed bad hard drive from computer, now flash drive won't mount. checkmate3001 Linux - Hardware 6 08-15-2008 01:03 AM
automatic fsck on boot. fsck errors. nixel Slackware 1 05-17-2004 08:51 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 11:12 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
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
Open Source Consulting | Domain Registration