Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2527
Views
0
Helpful
4
Replies

HyperFlex Installer 3.5 deploy error "Installing Software Packages on Storage Controller VM"

Go to solution
songklod suwannaphichat
Level 1
Level 1

‎08-02-2019 05:42 AM

Hi.
Does anyone experience this issue during HyperFlex 3.5 installation?
The error message is

Installing Software Packages on Storage Controller VM
failed in Task: 'Checking and Clearing Disk information if requested.' with Error: 'Disk Clean Operation is failed: Command '['blockdev', '--rereadpt', '/dev/sdl']' returned non-zero exit status 1'

Note:
1.Installer version v3.5.2d-31738-esx
2.Clean up disk partitions Option checked
3.Only Server 1 failed ,Server 2-8 success
4.Attached error screenshot 

Thank You.

Labels:
Preview file
101 KB
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Kirk J
Cisco Employee
Cisco Employee
In response to songklod suwannaphichat

‎08-06-2019 02:39 PM

Can you pull output of # cat /var/log/springpath/diskslotmap-v2.txt?

You are welcome to xxxxx out the serial numbers if you like ;)

I am wondering if it references drive dev /dev/sdl which fdisk output didn't list.

 

Kirk...

View solution in original post

0 Helpful
4 Replies 4

Go to solution
Kirk J
Cisco Employee
Cisco Employee

‎08-02-2019 12:46 PM - edited ‎08-02-2019 12:47 PM

Were the drives used in a previous HX install attempt, or from another HX node/cluster?

If not, then you don't need the checkbox for 'clean up'.  Not sure if there is issue with that drive's hardware.

 

If you log into the storage controller in it's current state, see what the output of fdisk -l shows for /dev/sdl

 

Kirk...

0 Helpful

Go to solution
songklod suwannaphichat
Level 1
Level 1
In response to Kirk J

‎08-04-2019 08:02 PM

@Kirk J wrote:

Were the drives used in a previous HX install attempt, or from another HX node/cluster?

If not, then you don't need the checkbox for 'clean up'.  Not sure if there is issue with that drive's hardware.

 

If you log into the storage controller in it's current state, see what the output of fdisk -l shows for /dev/sdl

 

Kirk...

Hi Kirk.
below is the output as you mentioned.

root@SpringpathController6ICAV7R4VL:~# fdisk -l
Disk /dev/sda: 2.5 GiB, 2684354560 bytes, 5242880 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: 0x3633852c

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 5240831 5238784 2.5G 83 Linux


Disk /dev/sdd: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sde: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdf: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdb: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdg: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdh: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdi: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdj: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

 


Disk /dev/sdm: 2.9 TiB, 3200631791616 bytes, 6251233968 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/sdn: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdc: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdk: 223.6 GiB, 240057409536 bytes, 468862128 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
Disklabel type: gpt
Disk identifier: 923C6C95-FBAB-424D-AB6A-9835B45850F3

Device Start End Sectors Size Type
/dev/sdk1 2048 335546367 335544320 160G Linux filesystem
/dev/sdk2 335548416 402657279 67108864 32G Linux filesystem
root@SpringpathController6ICAV7R4VL:~#

root@SpringpathController6ICAV7R4VL:~# fdisk -l | grep Disk
Disk /dev/sda: 2.5 GiB, 2684354560 bytes, 5242880 sectors
Disklabel type: dos
Disk identifier: 0x3633852c
Disk /dev/sdd: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sde: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sdf: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sdb: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sdg: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sdh: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sdi: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sdj: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sdm: 2.9 TiB, 3200631791616 bytes, 6251233968 sectors
Disk /dev/sdn: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sdc: 7.3 TiB, 8001563222016 bytes, 1953506646 sectors
Disk /dev/sdk: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Disklabel type: gpt
Disk identifier: 923C6C95-FBAB-424D-AB6A-9835B45850F3

root@SpringpathController6ICAV7R4VL:~# blockdev --rereadpt /dev/sdl
blockdev: ioctl error on BLKRRPART: Input/output error






0 Helpful

Go to solution
Kirk J
Cisco Employee
Cisco Employee
In response to songklod suwannaphichat

‎08-06-2019 02:39 PM

Can you pull output of # cat /var/log/springpath/diskslotmap-v2.txt?

You are welcome to xxxxx out the serial numbers if you like ;)

I am wondering if it references drive dev /dev/sdl which fdisk output didn't list.

 

Kirk...

0 Helpful

Go to solution
songklod suwannaphichat
Level 1
Level 1
In response to Kirk J

‎08-23-2019 09:30 AM

@Kirk J wrote:

Can you pull output of # cat /var/log/springpath/diskslotmap-v2.txt?

You are welcome to xxxxx out the serial numbers if you like ;)

I am wondering if it references drive dev /dev/sdl which fdisk output didn't list.

 

Kirk...

Thank you so much.
The issue was fixed by replacing the fail disk drive.

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents