问题原文
原帖链接 · Roger Creasy · CC BY-SA 3.0
I have a Linux server running on a VMware virtual machine, with 4 virtual hard drives. After the box ran for a month, I added 2 of the 4 hard drives in the vSphere client; I need more space. I did this step a few weeks ago, then was pulled into another project before creating the file systems and setting up mounts. Now, I do not know which drive is which within Linux. I have /dev/sda , /dev/sda1, /dev/sda2, and /dev/sdb
How do determine which drives have existing data and which are the new? Or, how do I remove drives and start over (I know how to remove the drives in teh vSphere client, but not how to remove the references to them in Linux).
Here are the results of dmesg| grep sd:
[ 1.361162] sd 2:0:0:0: [sda] 16777216 512-byte logical blocks: (8.58 GB/8.00 GiB)
[ 1.361205] sd 2:0:0:0: [sda] Write Protect is off
[ 1.361210] sd 2:0:0:0: [sda] Mode Sense: 61 00 00 00
[ 1.361253] sd 2:0:0:0: [sda] Cache data unavailable
[ 1.361257] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 1.363223] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 1.363398] sda: sda1 sda2
[ 1.363788] sd 2:0:0:0: [sda] Attached SCSI disk
[ 1.364425] sd 2:0:1:0: [sdb] 1572864000 512-byte logical blocks: (805 GB/750 GiB)
[ 1.364466] sd 2:0:1:0: [sdb] Write Protect is off
[ 1.364471] sd 2:0:1:0: [sdb] Mode Sense: 61 00 00 00
[ 1.364512] sd 2:0:1:0: [sdb] Cache data unavailable
[ 1.364515] sd 2:0:1:0: [sdb] Assuming drive cache: write through
[ 1.370673] sd 2:0:1:0: Attached scsi generic sg2 type 0
[ 1.405886] sdb: unknown partition table
[ 1.406228] sd 2:0:1:0: [sdb] Attached SCSI disk
[ 4.493214] Installing knfsd (copyright (C) 1996 [email omitted]).
[ 4.493849] SELinux: initialized (dev nfsd, type nfsd), uses genfs_contexts
[ 5.933636] EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: (null)
[ 5.933649] SELinux: initialized (dev sdb, type ext4), uses xattr
[ 6.099670] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 6.108488] SELinux: initialized (dev sda1, type ext4), uses xattr
Output from fdisk -l
Disk /dev/sda: 8 GiB, 8589934592 bytes, 16777216 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: 0x000dfc09
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 1026047 512000 83 Linux
/dev/sda2 1026048 16777215 7875584 8e Linux LVM
Disk /dev/sdb: 750 GiB, 805306368000 bytes, 1572864000 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
Disk /dev/mapper/fedora_dataserv-swap: 820 MiB, 859832320 bytes, 1679360 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
Disk /dev/mapper/fedora_dataserv-root: 6.7 GiB, 7201619968 bytes, 14065664 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
已采纳解答
原帖链接 · Roger Creasy · CC BY-SA 3.0
Thanks to everyone who answered. Everyone who did so, helped me track down the issue, and taught me much!
For some reason, Linux was not recognizing the 2 new drives. (I did not know that until I learned from the others' answers.
The final solution was:
- shut down the vm
- Remove the 2 new drives from in the vm in the vSphere client, without deleting them from the datastore
- Reboot the vm
- Shut down the vm
- add one drive in vSphere
- reboot the vm
- Confirm the os recognizes the new drive (
fdisk -l), which it did - Shut down the vm
- add the other drive in vSphere
- reboot the vm
fdisk -l now shows /dev/sdc and /dev/sdd
Thanks again to everyone for the help!
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
