fdisk -l do not show second hrd

M

mfaridi

Renowned Member
Oct 17, 2015
65
0
71
I install Proxmox VE 4 and I install it on first HDD and my system has two HDD. when I run this command
fdisk -l
I see



second HDD was partitioned by FreeBSD FS, I want use second HDD , for VM , because I can not find enough space on.first HDD
what I must do ?
 

Attachments

  • fdisk.txt
    3.8 KB · Views: 9
sigxcpu said:
Your fdisk output does not show even the first hdd.
Click to expand...
what I must do . I have two HDD. Proxmox install on first HDD, and I want use Second HDD for VM, what I must do ? . I need it for more VM , not for backup.
 
sigxcpu said:
You partition, format & mount the second HDD and add it as a storage type "dir" in UI (in "Datacenter" section, "Storage tab")
Click to expand...
Why I can not do this with UI ?
It was better I can do this during installation .
I need advance installation for Proxmox.
Can I install Debian 8 .and after that install some packages . make my Debian like Proxmox.
 
mfaridi said:
Why I can not do this with UI ?
It was better I can do this during installation .
I need advance installation for Proxmox.
Can I install Debian 8 .and after that install some packages . make my Debian like Proxmox.
Click to expand...

Hi,
about installing pve on jessie 8 see here: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie

But I would not recommend this for you! If you struggle with an second hdd, you should realy realy stay with the standard installer!

Because of the second hdd use the cli (read an good linux book - it's pure linux and has nothing to do with pve) and take a look here: https://pve.proxmox.com/wiki/Storage_Model

Udo
 
udo said:
Hi,
about installing pve on jessie 8 see here: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie

But I would not recommend this for you! If you struggle with an second hdd, you should realy realy stay with the standard installer!

Because of the second hdd use the cli (read an good linux book - it's pure linux and has nothing to do with pve) and take a look here: https://pve.proxmox.com/wiki/Storage_Model

Udo
Click to expand...
Thanks ,
I think I have to boot system with gparted .and partition second HDD and edit fstab.
But I do not why fdisk can not detect second HDD?
 
udo said:
Hi,
are your bios-config correct?

How are your disk named?
do an
Code: 
pvs
to see the device from the pve-VG.

How looks the output of
Code: 
[CODE]dmesg | grep SCSI
[/code]
Udo
Click to expand...
My bios config is correct , during installation , installer can detect my second HDD and I have two HDD , for installation I choose first HDD.
when I run pvs command I see
Code: 
PV                VG   Fmt  Attr PSize  PFree  /dev/cciss/c0d0p3 pve  lvm2 a--  68.21g 8.50g
and when I run this command
Code: 
dmesg | grep SCSI
I see
Code: 
root@aal-prox:~# dmesg | grep SCSI[    0.228361] SCSI subsystem initialized
[    0.734568] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[   29.273248] Loading iSCSI transport class v2.0-870.
ro
 
sigxcpu said:
You still didn't show us the whole fdisk -l output. Your two drives should be there but they are missing.
Click to expand...
when I run fdsik -l
I see
Code: 
root@aal-prox:~# fdisk -l

Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/pve-root: 17 GiB, 18253611008 bytes, 35651584 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/pve-swap: 4 GiB, 4294967296 bytes, 8388608 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/pve-data: 38.7 GiB, 41565552640 bytes, 81182720 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
I show my fdisk -lu in first post.
 
mfaridi said:
My bios config is correct , during installation , installer can detect my second HDD and I have two HDD , for installation I choose first HDD.
when I run pvs command I see
Code: 
PV                VG   Fmt  Attr PSize  PFree  /dev/cciss/c0d0p3 pve  lvm2 a--  68.21g 8.50g
and when I run this command
Code: 
dmesg | grep SCSI
I see
Code: 
root@aal-prox:~# dmesg | grep SCSI[    0.228361] SCSI subsystem initialized
[    0.734568] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[   29.273248] Loading iSCSI transport class v2.0-870.
ro
Click to expand...
Hi,
hmmm HP... my experiences with hp are a long time ago.

But normaly it should be
Code: 
fdisk /dev/cciss/c0d1

and what shows
Code: 
dmesg | grep -i cciss
Udo
 
sigxcpu said:
Stupid fdisk, then.

fdisk -l /dev/cciss/c0d0
fdisk -l /dev/ccis/c0d1 (or use tab completion to find the name of it)
Click to expand...

when I run this command
Code: 
fdisk -l [COLOR=#333333]/dev/cciss/c0d0[/COLOR]

I see
Code: 
root@aal-prox:~# fdisk -l /dev/cciss/c0d0

Disk /dev/cciss/c0d0: 68.3 GiB, 73372631040 bytes, 143305920 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: gpt
Disk identifier: 186F7D6A-24B1-4615-96F2-8D5C11D9C808


Device             Start       End   Sectors  Size Type
/dev/cciss/c0d0p1     34      2047      2014 1007K BIOS boot
/dev/cciss/c0d0p2   2048    262143    260096  127M EFI System
/dev/cciss/c0d0p3 262144 143305886 143043743 68.2G Linux LVM

and when I run
Code: 
fdisk -l /dev/cciss/c0d1

I see
Code: 
root@aal-prox:~# fdisk -l /dev/cciss/c0d1

Disk /dev/cciss/c0d1: 931.5 GiB, 1000171331584 bytes, 1953459632 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: 0x90909090


Device            Boot Start        End    Sectors   Size Id Type
/dev/cciss/c0d1p1 *       63 1953455804 1953455742 931.5G a5 FreeBSD

Thanks again.
I see second disk , I want format this this disk and use it for vm
 
udo said:
Hi,
hmmm HP... my experiences with hp are a long time ago.

But normaly it should be
Code: 
fdisk /dev/cciss/c0d1

and what shows
Code: 
dmesg | grep -i cciss
Udo
Click to expand...
when I run this
Code: 
 [COLOR=#333333]dmesg | grep -i cciss
I see
Code: 
[/COLOR]root@aal-prox:~# dmesg | grep -i cciss[   22.752102] cciss 0000:03:00.0: cciss0: <0x3230> at PCI 0000:03:00.0 IRQ 33 using DAC
[   22.775841]  cciss/c0d0: p1 p2 p3
[   22.781263]  cciss/c0d1: p1
[   22.781768] scsi host4: cciss
ro
 
excellent.

fdisk /dev/cciss/c0d1
t
83
w

...

Code: 
mkfs.ext4 /dev/cciss/c0d1p1

edit /etc/fstab and add at the end of the file
Code: 
/dev/cciss/c0d1p1 /data ext4 defaults 0 0

then

Code: 
mkdir /data
Code: 
mount /data

In Proxmox UI (I told you above where: Datacenter/Storage) add a new storage type "dir" in folder /data and check whatever you want to hold in it (CT, VM, ISO and so on)

Done.
 
sigxcpu said:
excellent.

fdisk /dev/cciss/c0d1
t
83
w

...

Code: 
mkfs.ext4 /dev/cciss/c0d1p1

edit /etc/fstab and add at the end of the file
Code: 
/dev/cciss/c0d1p1 /data ext4 defaults 0 0

then

Code: 
mkdir /data
Code: 
mount /data

In Proxmox UI (I told you above where: Datacenter/Storage) add a new storage type "dir" in folder /data and check whatever you want to hold in it (CT, VM, ISO and so on)

Done.
Click to expand...
Thanks, thanks,
I do that how I test I do correct ?
 
mfaridi said:
when I run this
Code: 
 [COLOR=#333333]dmesg | grep -i cciss
I see
Code: 
[/COLOR]root@aal-prox:~# dmesg | grep -i cciss[   22.752102] cciss 0000:03:00.0: cciss0: <0x3230> at PCI 0000:03:00.0 IRQ 33 using DAC
[   22.775841]  cciss/c0d0: p1 p2 p3
[   22.781263]  cciss/c0d1: p1
[   22.781768] scsi host4: cciss
ro
Click to expand...
My Boss give another HP server for config and this new HP server has four HDD and I install on First HDD Proxmox and I want partitioning other HDDs,
When I type this command
Code: 
 fdisk /dev/cciss/c0d1
and I choose
Code: 
 t
I see this error
Code: 
 No partition is defined yet!
and I can not continue partitioning
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back