Please enable javascript, or click here to visit my ecommerce web site powered by Shopify.

Community Forum > After Upgrade to v4.4.1.011 Storage Pool Bad and Other Issues

I'm running on Community Edition in the test environment. After I upgraded to v4.4.1.011 from v4.2.x my storage pool is in a degraded state saying that two of my disks and SSD SATA cache is missing.
I fixed that by reimporting the pool and running a scrub just in case. However the two missing disks and SSD is still saying that it is available from the Physical Disk side tab, but those same disks are in the assigned Storage Pool and says functioning.

Also I cannot see to remove my SSD cache while trying to fiddle with this thing. Error says "Specified 'name' is empty, you must specify a valid name containing only alpha-numeric characters and these characters contained within single quotes: '-_.:@ ()' [err=19]"

I also tried from CLI and got below error message when running the below commands.

root@qs4:~# qs pool-device-list

Storage System Storage Pool Name Raid Group ID Size Physical Disk Serial Number Physical Disk Scsi ID Device Path Physical Disk ID Enclosure Slot ID
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
qs4 QS4-zPOOL400 scsi-35000c50083797fb3 mirror-2 931.51GiB Z1W3QTD40000C5402MLT 35000c50083797fb3 /dev/disk/by-id/scsi-35000c50083797fb3 ec8740e9-ef37-b3c1-3f26-b2de4e608101 b3d68bc6-a201-55ee-5698-db059bc18166
qs4 QS4-zPOOL400 scsi-35000c50083855eab mirror-0 931.51GiB Z1W3ZQS10000R5402EHS 35000c50083855eab /dev/disk/by-id/scsi-35000c50083855eab 86d3edec-1965-7a59-a93c-4d99f3a49f92 64818a42-418e-7039-09d1-59c2dedd266c
qs4 QS4-zPOOL400 scsi-35000c50083856367 mirror-1 931.51GiB Z1W3ZQPD0000R539DU1Z 35000c50083856367 /dev/disk/by-id/scsi-35000c50083856367 4135942d-03b8-2c8c-f40c-b660b2091638 dd6782bf-ef72-1b06-9fe5-fae71f09dccf
qs4 QS4-zPOOL400 scsi-35000c50083857383 mirror-1 931.51GiB Z1W3ZQ7Z0000R539SKYY 35000c50083857383 /dev/disk/by-id/scsi-35000c50083857383 82a63585-a3e1-830b-15d6-255f0b853ed7 4badd706-16ed-3ead-850d-df81e69a3b17
qs4 QS4-zPOOL400 scsi-SATA_INTEL_SSDSC2BA4BTHV51810111400NGN 372.61GiB /dev/disk/by-id/scsi-SATA_INTEL_SSDSC.. 1264f2f7-f769-341c-277a-e4a2304151fd
qs4 QS4-zPOOL400 scsi-SATA_ST1000NM0033-9Z_Z1W5Q2QS mirror-0 931.51GiB /dev/disk/by-id/scsi-SATA_ST1000NM003.. b7430a3f-7899-f0b4-3c1f-3b7a669f4e6b
qs4 QS4-zPOOL400 scsi-SATA_ST1000NM0033-9Z_Z1W5Q3TY mirror-2 931.51GiB /dev/disk/by-id/scsi-SATA_ST1000NM003.. a169b366-2f27-d251-e6ec-61dd96bdc776

root@qs4:~# qs pool-remove-read-cache --pool QS4-zPOOL400 --disk-list=scsi-SATA_INTEL_SSDSC2BA4BTHV51810111400NGN
ERROR: Server request to [http://localhost:5152] failed: "Specified PhysicalDisk object 'scsi-SATA_INTEL_SSDSC2BA4BTHV51810111400NGN' could not be found. [err=5]"


root@qs4:~# qs pool-remove-read-cache --pool QS4-zPOOL400 --disk-list=/dev/disk/by-id/scsi-SATA_INTEL_SSDSC2BA4BTHV51810111400NGN
ERROR: Server request to [http://localhost:5152] failed: "Specified name '/dev/disk/by-id/scsi-SATA_INTEL_SSDSC2BA4BTHV51810111400NGN' contains one or more invalid characters. The 'name' may only contain alpha-numeric characters and these characters contained within single quotes: '-_.:@ ()' [err=21]"

January 15, 2018 | Registered CommenterDon Nguyen

Greetings,

Can you open a Support Case with us and upload a set of logs so we can look into this in more detail, please use the steps below:


Open a support case

https://www.osnexus.com/contact-support/

Upload Logs

**Log Gathering**

The procedure for uploading the log files are below.

1) Please login to the QuantaStor via ssh or physically at the system console as the `qadmin` user or a user with similar sudo access, you can also use the root user if you have that configured.
Please note that we also provide a convenient option in the WebUI for systems with internet access where you can right click on the Storage System and choosing 'Send log report...'.

Note: if you did not change the password for the qadmin user, the default password is `qadmin`

2) Please run the `sudo qs-sendlogs` command from a shell console to generate the log file. If your system has internet access it will automatically upload the logfiles to our FTP server.

If your system does not have internet access, please proceed to step 3

3) Copy the logfile generated by the `sudo qs-sendlogs` command from your QuantaStor unit using your preferred ssh/scp/sftp client and upload it using your preferred ftp client to our ftp server.

Our FTP login for uploading the logfiles is below:

```
username: report

password: REP0RT (that 0 is a zero)

ftp server ip: 63.229.31.162

port: 821
```

Please let us know once you have had a chance to upload the logs.

January 15, 2018 | Registered CommenterRobert Staffeld

Hi Don,
With all the APIs/CLI commands you can always specify the UUID/GUID of the object that you want to specify. So if you see errors from the CLI like "Specified 'name' is empty" then try using the UUID of the object. In the case of a storage pool you can see all the pool devices with the 'qs spd-list' command. The reason why we prefer to use the UUID of objects is that they're unique throughout the storage grid whereas a device name like /dev/sda can be common to many hosts. That said, we will look at adding support for specifying the device path as a valid specifier to the 'name' field for objects referring to devices in an upcoming release.
Best,
-Steve

January 15, 2018 | Registered CommenterSteve

Don,
Thanks for the feedback, QuantaStor is looking for the ID of the Physical Disk object as shown in the qs disk-list output. This isn't right and you should be able to use both PD identifiers or the SPD ids as shown in the qs spd-list output. We've identified the bug and corrected it in engineering ticket QSTOR-4407. That'll be addressed in QS 4.5.
Best,
-Steve

January 23, 2018 | Registered CommenterSteve

Don, just an update that was all addressed in v4.5 so you can use physical disk object UUIDs when doing commands on storage pool devices.

March 29, 2018 | Registered CommenterSteve