-
It is recommended not to use the contents of cat proc partitions to view the hard disk and partitions, it is recommended to use fdisk -l to view the hard disk and partitions, because using fdisk -l can not only see the size of each hard disk, but also the specific situation of the partition.
Of course, you can also check the devices in the ls dev directory to see if each hard disk partition exists.
In addition, your mount command is also problematic, do not use mount dev sdb mnt 1. Because dev sdb refers to the entire hard disk, not a specific partition, when mounted, only one partition can be mounted. The partitions on the hard disk are named sdb1, sdb2, sdb3, and so on.
So you should use mount dev sdb1 mnt 1 when mounting.
Pay attention to the file format of the disk, if it is a special partition, you need to specify the partition type, and some file formats also need to add some special parameters.
There is also whether the directory 1 has been created in the mnt directory, if not, then there will be an error when mounting. You can use the mkdir command to create a directory.
Based on these questions raised above, correct it to the following action:
1.Check the size of the disk: fdisk -l
2.Create a directory to be mounted to; mkdir -p mnt 1 (after using the -p parameter, if there is a directory of 1 in the mnt directory, you do not need to create this directory again, it will automatically exit the creation operation).
3.Mount the file system: mount -t file format dev sdb1 mnt 1 (sdb1 is just an example, you can mount any disk partition for this use case).
-
It is recommended to use the standard command:
mount -t auto dev sda1 mnt 1 must determine that mnt 1 exists.
Look at you like this should hang SDD, some versions he recognizes the hard disk as a different name!
Generally speaking, the hard disk with more drive letters may be left in advance, sata, mobile hard disk and other equipment! You can view the partition information:
fdisk -l Check the disk partitions!
-
|grep ntfs confirms that kernel-module-ntfs is loaded, if not, use modprobe ntfs to manually load the skin for early testing. The words should be mount -t ntfs-3g dev hdd5 mnt stove scattered d
-
Send me an email and I'll send you detailed documentation and packages!
-
Because you don't have the ncompress package installed:
yum install ncompress -y
-
First question.
When starting, try adding noapic to the kernel's options as prompted, and it should solve the problem.
Second question.
To set the disk type of the virtual machine to "IDE", do not use "SCSI". Because the RHEL5 installation disk does not support SCSI type hard disks, you must compile the kernel yourself to support it.
Note: To set to "Custom" in the first option of creating a new virtual machine, do not use "Typical" to have the option to select the disk type.
-
How long has it been here?
I recommend that you don't mount an ISO when creating a VM. Select Add ISO manually later.
You can try. This configuration is no problem with running RHEL5.
Also, why mount two optical drives? It's useless. It is recommended to remove one.
I wish you a speedy solution.
-
Why use two cd devs, you can choose one of your images.
-
This error message indicates that the Redhat installer did not recognize your virtual machine's hard drive. Two possible reasons for this problem together.
1.Your version of redhat is too old.
I don't know if your Redhat Linux 5 is a Redhat 5 or a Redhat Enterprise Linux 5 that is more than nine years old. Not this issue in the case of Redhat Enterprise 5. In the case of Redhat 5, if your virtual machine's hard drive is set to HDD, your hard drive will not be recognized.
Because the SATA ( interface of hard disks is only available in recent years. At that time, the hard disk interface was IDE, so Redhat5 only supported hard disks. The solution is to replace your hard drive with an IDE hard drive in the virtual machine.
2.You don't have a hard disk enabled in your virtual machine.
Let's say you create a new VM and don't set up a hard disk for the VM, or if the VM doesn't automatically enable the hard disk when you boot it up. Then when you run the Redhat installer, the installer will not be able to find the hard drive. The solution is to make sure that your virtual machine is in the shutdown state, then select the virtual machine, right-click, select the virtual machine, go to the virtual machine device manager, and add an IDE hard disk to the virtual machine (assuming your virtual machine software is VMware).
-
Hello, it's because you set the properties of the virtual hard disk of the virtual machine, the default setting is the SCSI hard disk, and the installation disk can't recognize the device After you delete it, re-establish and add a hard disk, and set it to the IDE structure.
-
Do you choose automatic partitioning? Players move points! How big is the hard drive you gave?
-
Red Hat Enterprise Linux 6 is the first to do without a graphical interface, and 5 is to enter Linux text on the start screen to be text!
-
Is your graphics card hardware not detected, so a text mode is installed.
-
There is a problem with the bootstrap area, you can carefully check the relevant information of grup, it may be possible to modify it.
There is a configuration file under boot grub, probably because the file is broken, or there is something wrong with your disk. If it's a disk issue, it's not easy. If it's a profile issue, there should be a way.
-
I didn't recognize the hard drive, I guess it was a virtual machine you transferred from somewhere else.
tar jxvf and then enter the directory that has just been extracted, and execute the following command. >>>More
Method 2: Find a related book and read it, you can take a look at "Linux Should Be Learned This Way", the address is 3w(dot)linuxprobe(dot)com, good luck