Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Just wondering if you can help me. I've recently bought a new hard drive (seagate) which I am planning to use for backup only.
So far I have been unsuccessful in partitioning the hard dive. Following is a snapshot.
[root@ax-backup ~]# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0xbd994891.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): n
p primary partition (1-4)
Partition number (1-4): 1
First cylinder (1-1024, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1024, default 1024):
Using default value 1024
Command (m for help): w
The partition table has been altered!
I disagree! 'fdisk' is reliable when used properly. I like to write the partition table to disk then reboot to insure that the kernel partition table is updated.
If you want a curses based disk tool then 'cfdisk' is the one to use. I would still reboot after writing the partition table to insure the update of the kernel partition table. I have not experienced any problems with either.
I always make my filesystems manually therefore I can be insured that the hdd partition will be valid. I even create my swaps manually before a install to insure that the space is contiguous and without error.
Logical max current
cylinders 2303 2303
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16451600
device size with M = 1024*1024: 8033 MBytes
device size with M = 1000*1000: 8423 MBytes (8 GB)
Ooohhh - that doesn't look real good. That isn't LBA geometry.
As an aside, here's a cite from the fdisk manpage
cfdisk is a beautiful program that has strict requirements on the par‐tition tables it accepts, and produces high quality partition tables. Use it if you can. fdisk is a buggy program that does fuzzy things -usually it happens to produce reasonable results.
Dunno - is this external or internal. If internal, what does the BIOS have set for it ?.
At a minimum, the [cs]fdisk suite all allow setting the geometry, as does grub - but you need to know the numbers to plug in. Better to play with the BIOS settings and see if the disk resets itself correctly I would think.
Most modern motherboard BIOS has hard disk detection. If this is a internal you should setup with your geometry with the 'user' settings. Your drive information is not complete so I would look at your drives documentation to get the proper geometry.
You could have a bad hdd system. The warranty still valid?