Differences

This shows you the differences between two versions of the page.

--- server:hpe:raid [2021/03/26 19:46] – gsys
+++ server:hpe:raid [2024/02/17 19:03] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Raiderweiterung ======
 ===== ESXi =====
+==== RAID Erweitern und Logical Disk vergrößern ====
 **Voraussetzung: HPE Custom ESXi Image ab 6.0**
@@ Line 6: / Line 8: @@
 /opt/smartstorageadmin/ssacli/bin/ssacli ctrl all show config                   #Gesamte Konfig anzeigen
 /opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=0 show detail                #Konfig von Controller in Slot 0
-/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=0 ld 1 add drives=2I:1:5     #Platte Cage 2 Bay 5 zu vDisk 1
+/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=0 ld 1 add drives=2I:1:5     #Platte Bay 5 zu vDisk 1
 /opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=0 ld all show status
 /opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=0 ld 1 show
-/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=1 ld 1 modify size=max forced #muss mit forced ausgeführt werden
+/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=0 ld 1 modify size=max forced #muss mit forced ausgeführt werden
 </code>
 https://kallesplayground.wordpress.com/useful-stuff/hp-smart-array-cli-commands-under-esxi/
+<code>
+esxcli storage core adapter rescan --all
+</code>
+==== Datastore-Partition erweitern ====
+<code bash>
+[root@localhost:~] vmkfstools -P /vmfs/volumes/datastore1/
+VMFS-5.60 file system spanning 1 partitions.
+File system label (if any): datastore1
+Mode: public
+Capacity 891742584832 (850432 file blocks * 1048576), 46912241664 (44739 blocks) avail, max supported file size 69201586814976
+UUID: 5565abe4-01c934e4-3075-9c8e995cf9c2
+Partitions spanned (on "lvm"):
+        naa.600508b1001ce56fa87b49c15607756e:3
+Is Native Snapshot Capable: YES
+[root@localhost:~] partedUtil get /vmfs/devices/disks/naa.600508b1001ce56fa87b49
+c15607756e
+naa.600508b1001ce56fa87b49c15607756e    naa.600508b1001ce56fa87b49c15607756e:6
+naa.600508b1001ce56fa87b49c15607756e:1  naa.600508b1001ce56fa87b49c15607756e:7
+naa.600508b1001ce56fa87b49c15607756e:2  naa.600508b1001ce56fa87b49c15607756e:8
+naa.600508b1001ce56fa87b49c15607756e:3  naa.600508b1001ce56fa87b49c15607756e:9
+naa.600508b1001ce56fa87b49c15607756e:5
+[root@localhost:~] partedUtil get /vmfs/devices/disks/naa.600508b1001ce56fa87b49
+c15607756e
+Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)? This will also fix the last usable sector as per the new size. diskSize (2343486044) AlternateLBA (1757614683) LastUsableLBA (1757614650)
+Warning: Not all of the space available to /dev/disks/naa.600508b1001ce56fa87b49c15607756e appears to be used, you can fix the GPT to use all of the space (an extra 585871360 blocks) or continue with the current setting? This will also move the backup table at the end if is is not at the end already. diskSize (2343486044) AlternateLBA (1757614683) LastUsableLBA (1757614650) NewLastUsableLBA (2343486010)
+255 63 2343486044
+64 8191 0 128
+8224 520191 0 0
+520224 1032191 0 0
+1032224 1257471 0 0
+1257504 1843199 0 0
+1843200 7086079 0 0
+7086080 15472639 0 0
+15472640 1757614650 0 0
+[root@localhost:~] partedUtil get /vmfs/devices/disks/naa.600508b1001ce56fa87b49
+c15607756e
+naa.600508b1001ce56fa87b49c15607756e    naa.600508b1001ce56fa87b49c15607756e:6
+naa.600508b1001ce56fa87b49c15607756e:1  naa.600508b1001ce56fa87b49c15607756e:7
+naa.600508b1001ce56fa87b49c15607756e:2  naa.600508b1001ce56fa87b49c15607756e:8
+naa.600508b1001ce56fa87b49c15607756e:3  naa.600508b1001ce56fa87b49c15607756e:9
+naa.600508b1001ce56fa87b49c15607756e:5
+[root@localhost:~] partedUtil get /vmfs/devices/disks/naa.600508b1001ce56fa87b49
+c15607756e:3
+255 63 1742142011
+[root@localhost:~] partedUtil fixGpt /vmfs/devices/disks/naa.600508b1001ce56fa87
+b49c15607756e
+FixGpt tries to fix any problems detected in GPT table.
+Please ensure that you do not run this on any RDM (Raw Device Mapping) disk.
+Are you sure you want to continue (Y/N): Y
+Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)? This will also fix the last usable sector as per the new size. diskSize (2343486044) AlternateLBA (1757614683) LastUsableLBA (1757614650)
+Fix/Ignore/Cancel? Fix
+gpt
+255 63 2343486044
+64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
+8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
+520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
+1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
+1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
+1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
+7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
+15472640 1757614650 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
+[root@localhost:~] partedUtil getUsableSectors /vmfs/devices/disks/naa.600508b10
+ce56fa87b49c15607756e
+2343486010
+[root@localhost:~] partedUtil resize /vmfs/devices/disks/naa.600508b1001ce56fa87
+b49c15607756e 3 15472640 2343486010
+[root@localhost:~] vmkfstools --growfs /vmfs/devices/disks/naa.600508b1001ce56fa
+b49c15607756e:3 /vmfs/devices/disks/naa.600508b1001ce56fa87b49c15607756e:3
+[root@localhost:~] vmkfstools -V
+</code>