Linux - NewbieThis 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!
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.
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.
A formatted a disk originally meant that the disk has header/checksum sectors written on the disk that can be used to locate blocks of data to read/write, and contains a couple of blocks to record references to bad spots on the disk, as well as a reserve set of blocks to substitute for the bad spots. Currently this is done by the manufacturer, and systems don't have to do it themselves - and the formatter board on the disk itself does the substitution. This provides the appearance of a "perfect" disk to the host computer. Unfortunately, it also means that once the reserve set of substitution blocks is used up, the formatter board identifies itself as a failing disk, and you start getting read/write errors.
As a side effect of the host system doing the formatting, you used to be able to reformat a disk, give it a larger reserve set, and continue using the disk for a couple of more years. You can't do it anymore, but then, disks don't cost $14,000 US either.
A partitioned disk has had certain blocks of the disk written with standardized information that identifies parts of the disk. This "partition table" contains information about the starting block number, length, some flag bits, and an identification number. The exact values depend on the standard used.
Note: this doesn't address any filesystems that might be on the disk (called "formatting" by Microsoft). Creating filesystems on a disk writes a data structure on the partition that allows the operating system to know where data has been stored, what blocks are available, what a directory is, and allows the operating system to ensure that things don't get mixed up during use.
There are many different filesystems used by various operating systems.
In the context of the error message "unformatted disk or raw device" can mean several things. Either the disk is really blank i.e. raw with no partitions and not formatted with a file system, partitioned and formatted with a file system the operating does not understand or the file system has become corrupted.
In a nutshell partitioned and formatted as stated is to divide the disk into sections and create a file system on that section like FAT32, NTFS, ext4 etc.
External disks are partitioned and formatted with a file system from the manufacture. And typically they are formatted as FAT32, NTFS or exFAT. I would guess the drive is formatted as NTFS which RHEL does include support by default. If you do not need to use the drive on a windows system then reformat with a linux file system.
"Nature" isn't involved in it. A disk may be formatted or not when you purchase it. In order to be of any use, it must be formatted with some type of filesystem.
As per unix term, NTFS will not support to unix file systems.
A more accurate description would be the windows operating system does not support and will not read/write to a Linux filesystem. This is a business decision of microsoft. ntfs is just another filesystem.
Unformatted disk is called raw partition or raw devices
Accurate, although an operating system reporting a device is 'raw' isn't always accurate. It may simply mean the operating system in use does not recognize the filesystem and hence reports it as a 'raw' device.
Mounting a disk mean basically to make it accessible and this needs to be done with internal and external devices with whichever operating system is being used.
Should i need to reformat D:\ drive to use in Linux ?
No. Your Linux system is a virtual machine, which means it has no physical drive access. When it writes to its drive, it's actually writing to a virtual drive in VMWare, which turns around and sticks it in a file on your host system. The VM never interacts directly with the filesystem on the host drive, it doesn't care what it is.
Originally Posted by Joy Stick
If i do reformat , do i loose all ms-docs and images from D:\ drive ?
You would, yes, but reformatting a drive for a VM is pointless.
My answer was based on a bad assumption that what you meant by procure and external was a physical USB drive and not an additional created virtual disk.
If the external drive from your original post is the same as the 25GB drive then it does need to be partitioned and formatted from within Red Hat. As stated by suicidaleggroll the drive as seen by the linux guest is just a file on the host.
If you're trying to add a second virtual disk through VMWare, then the physical drive on which you choose to store this virtual disk does not matter, and neither does its filesystem type, because the virtual machine will never interact directly with the physical drive. Once created, the virtual machine will see a raw, unpartitioned, unformatted "disk", and you'll need to use the VM to format it with whatever filesystem you choose.
If you're trying to pass a USB drive straight through to the VM so that it can manage it (which means you will NOT be able to see or interact with the drive in Windows, ONLY the Linux VM will have access to it), then the VM will have full access to the drive and you will need to format it to a filesystem the Linux OS can understand.
Last edited by suicidaleggroll; 12-28-2015 at 02:35 PM.