fdisk -l - messaggio: doesn't contain a valid partition table

Ciao a tutti,
Scusate se vi stresso come al solito ma ho notato questo messaggio mentre aggiungevo un disco nuovo su 3 server,

La macchina sembra funzionare ma ho paura che in caso di reboot dia problemi.

[code]fdisk -l

Disk /dev/sda: 15.0 GB, 15032385536 bytes
255 heads, 63 sectors/track, 1827 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 1827 14570955 8e Linux LVM

Disk /dev/sdb: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn’t contain a valid partition table

Disk /dev/sdc: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdc doesn’t contain a valid partition table

Disk /dev/sdd: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdd1 1 652 5237189+ 8e Linux LVM

Disk /dev/dm-0: 6274 MB, 6274678784 bytes
255 heads, 63 sectors/track, 762 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-0 doesn’t contain a valid partition table

Disk /dev/dm-1: 2281 MB, 2281701376 bytes
255 heads, 63 sectors/track, 277 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn’t contain a valid partition table

Disk /dev/dm-2: 3892 MB, 3892314112 bytes
255 heads, 63 sectors/track, 473 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-2 doesn’t contain a valid partition table

Disk /dev/dm-3: 2415 MB, 2415919104 bytes
255 heads, 63 sectors/track, 293 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-3 doesn’t contain a valid partition table

Disk /dev/dm-4: 97.7 GB, 97710505984 bytes
255 heads, 63 sectors/track, 11879 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-4 doesn’t contain a valid partition table

Disk /dev/dm-5: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-5 doesn’t contain a valid partition table

Disk /dev/sde: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sde1 1 13054 104856223+ 83 Linux
[[email protected] admin]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/rootvg-rootvol
5935604 3894504 1734720 70% /
/dev/mapper/rootvg-homevol
2158408 1142988 904024 56% /home
/dev/mapper/rootvg-varvol
3682008 762844 2729128 22% /var
/dev/mapper/rootvg-optvol
93923256 9854692 79298696 12% /opt
/dev/sda1 101086 26971 68896 29% /boot
tmpfs 4087224 0 4087224 0% /dev/shm
/dev/mapper/rootvg-installvol
5160576 379284 4519148 8% /opt/install
/eetu_pre5/data
50233344 3291008 46942336 7% /mnt/data[/code]

Sembra che i dischi /dev/sdb e /dev/sdc non presentino alcuna partition table. Sono nuovi? Ti risulta che dovrebbero contenere dati?
Per maggiore scrupolo possiamo vedere

[code]

parted /dev/sd** print

mdadm -E /dev/sd**

mdadm --detail --scan --verbose

lvmdiskscan

pvscan

vgscan

lvscan

[/code]****

non sono nuovi, io me ne sono accorto per caso dovendo aggiungerne un altro per aumentare lo spazio:

[[email protected]]# mdadm -E /dev/sd** mdadm: No md superblock detected on /dev/sdb. mdadm: No md superblock detected on /dev/sdc. [[email protected]]# mdadm --detail --scan --verbose [[email protected]]# lvmdiskscan /dev/ramdisk 16.00 MB] /dev/root 5.84 GB] /dev/ram 16.00 MB] /dev/sda1 101.94 MB] /dev/rootvg/homevol 2.12 GB] /dev/ram2 16.00 MB] /dev/sda2 13.90 GB] LVM physical volume /dev/rootvg/varvol 3.25 GB] /dev/ram3 16.00 MB] /dev/rootvg/swap 2.25 GB] /dev/ram4 16.00 MB] /dev/rootvg/optvol 34.00 GB] /dev/ram5 16.00 MB] /dev/rootvg/installvol 5.00 GB] /dev/ram6 16.00 MB] /dev/ram7 16.00 MB] /dev/ram8 16.00 MB] /dev/ram9 16.00 MB] /dev/ram10 16.00 MB] /dev/ram11 16.00 MB] /dev/ram12 16.00 MB] /dev/ram13 16.00 MB] /dev/ram14 16.00 MB] /dev/ram15 16.00 MB] /dev/sdb 2.00 GB] LVM physical volume /dev/sdc 100.00 GB] LVM physical volume 8 disks 15 partitions 2 LVM physical volume whole disks 1 LVM physical volume [[email protected]]# pvscan PV /dev/sda2 VG rootvg lvm2 [13.88 GB / 0 free] PV /dev/sdb VG rootvg lvm2 [1.97 GB / 0 free] PV /dev/sdc VG rootvg lvm2 [99.97 GB / 63.34 GB free] Total: 3 [115.81 GB] / in use: 3 [115.81 GB] / in no VG: 0 [0 ] [[email protected]]# vgscan Reading all physical volumes. This may take a while... Found volume group "rootvg" using metadata type lvm2 [[email protected]]# lvscan ACTIVE '/dev/rootvg/rootvol' [5.84 GB] inherit ACTIVE '/dev/rootvg/homevol' [2.12 GB] inherit ACTIVE '/dev/rootvg/varvol' [3.25 GB] inherit ACTIVE '/dev/rootvg/swap' [2.25 GB] inherit ACTIVE '/dev/rootvg/optvol' [34.00 GB] inherit ACTIVE '/dev/rootvg/installvol' [5.00 GB] inherit **

Scusate credo di aver inserito la VM sbagliata in precedenza

[quote][[email protected] admin]# mdadm -E /dev/sd**
mdadm: No md superblock detected on /dev/sdb.
mdadm: No md superblock detected on /dev/sdc.
[[email protected] admin]# mdadm --detail --scan --verbose
[[email protected] admin]# lvmdiskscan
/dev/ramdisk 16.00 MB]
/dev/root 5.84 GB]
/dev/ram 16.00 MB]
/dev/sda1 101.94 MB]
/dev/rootvg/homevol 4.12 GB]
/dev/ram2 16.00 MB]
/dev/sda2 13.90 GB] LVM physical volume
/dev/rootvg/varvol 3.25 GB]
/dev/ram3 16.00 MB]
/dev/rootvg/swap 2.25 GB]
/dev/ram4 16.00 MB]
/dev/rootvg/optvol 40.00 GB]
/dev/ram5 16.00 MB]
/dev/rootvg/installvol 5.00 GB]
/dev/ram6 16.00 MB]
/dev/ram7 16.00 MB]
/dev/ram8 16.00 MB]
/dev/ram9 16.00 MB]
/dev/ram10 16.00 MB]
/dev/ram11 16.00 MB]
/dev/ram12 16.00 MB]
/dev/ram13 16.00 MB]
/dev/ram14 16.00 MB]
/dev/ram15 16.00 MB]
/dev/sdb 2.00 GB] LVM physical volume
/dev/sdc 100.00 GB] LVM physical volume
8 disks
15 partitions
2 LVM physical volume whole disks
1 LVM physical volume
[[email protected] admin]# pvscan
PV /dev/sda2 VG rootvg lvm2 [13.88 GB / 0 free]
PV /dev/sdb VG rootvg lvm2 [1.97 GB / 0 free]
PV /dev/sdc VG rootvg lvm2 [99.97 GB / 55.34 GB free]
Total: 3 [115.81 GB] / in use: 3 [115.81 GB] / in no VG: 0 [0 ]
[[email protected] admin]# vgscan
Reading all physical volumes. This may take a while…
Found volume group “rootvg” using metadata type lvm2
[[email protected] admin]# lvscan
ACTIVE ‘/dev/rootvg/rootvol’ [5.84 GB] inherit
ACTIVE ‘/dev/rootvg/homevol’ [4.12 GB] inherit
ACTIVE ‘/dev/rootvg/varvol’ [3.25 GB] inherit
ACTIVE ‘/dev/rootvg/swap’ [2.25 GB] inherit
ACTIVE ‘/dev/rootvg/optvol’ [40.00 GB] inherit
ACTIVE ‘/dev/rootvg/installvol’ [5.00 GB] inherit
[[email protected] admin]#
[/quote]**

Analizzando gli output forniti possiamo ragionevolmente concludere che i dischi /dev/sdb e /dev/sdc non presentano partition table dal momento che sono stati marcati nella loro interezza come Physical Volumes.
Le indicazioni fornite dai comandi pvs e lvmdiskscan sono congruenti in tal senso e non sembra essere presente alcun refuso di eventuale ex impiego di tali unità disco in volumi raid.

Personalmente preferisco partizionare comunque i dischi che prevedo di utilizzare in un contesto di LVM e successivamente marcare le partizioni come type 8e (LVM Physical Volume) quindi configurarle come PV per mezzo del comando pvcreate; questo accorgimento consente inoltre di assegnare all’occorrenza lo spazio disponibile in Volume Groups differenti.

Tuttavia LVM permette anche di utilizzare interi dischi (come nel tuo caso) come Physical Volumes, senza procedere necessariamente ad un preliminare partizionamento degli stessi.

Confido quindi nel fatto che il tuo server non ti giochi qualche brutto scherzo al prossimo reboot :wink:

Ciao

Cupo

Grazie Cupo,
Scherzi non me ne ha fatto per ora, sono stati gia reboottati un paio di volte, sono servers di test, non so chi sia stata la bestia che ha configurato cosi ma spero che non decidano mai di metterli in produzione :smiley: