Question & Answer
Question
If /store has enough space then why can't we keep SFS file in that partition?
Answer
No. We can not keep the SFS file in the /store partition for the upgrade process.
If we copy the SFS file under /store, mount it and then run the installer, we get below error:
"The patch cannot start from the store partition"
# /media/updates/installer
[ERROR] The patch cannot start from the store partition.
Copy the SFS file to the /var/log directory or to another location that has sufficient disk space.
This restriction is due to the fact that the /store partition gets reconfigured during the upgrade, wherein the sub-directories gets recreated.
While upgrading the /store partition, the directories gets recreated as shown below:
Tue Jan 2 09:12:28 EST 2024 [setup]: mkdir -p /opt/qradar/conf
…
Tue Jan 2 09:12:28 EST 2024 [setup]: mkdir /store
mkdir: cannot create directory '/store': File exists
Tue Jan 2 09:12:28 EST 2024 [setup]: chmod 755 /store
…
Tue Jan 2 09:16:17 EST 2024 [setup]: mkdir -p /store/configservices
Tue Jan 2 09:16:17 EST 2024 [setup]: chmod 775 /store/configservices
…
Tue Jan 2 09:16:17 EST 2024 [setup]: mkdir -p /store/ariel
Tue Jan 2 09:16:17 EST 2024 [setup]: chmod 775 /store/ariel
…
Tue Jan 2 09:35:13 EST 2024: [create_nobody_dirs] mkdir -p /store/ariel
Tue Jan 2 09:35:13 EST 2024: [create_nobody_dirs] chown nobody:nobody /store/ariel
Tue Jan 2 09:35:13 EST 2024: [create_nobody_dirs] mkdir -p /store/backup
Tue Jan 2 09:35:13 EST 2024: [create_nobody_dirs] chown nobody:nobody /store/backup
…
Tue Jan 2 09:35:13 EST 2024: [create_nobody_dirs] mkdir -p /store/configservices/configurationsets
Tue Jan 2 09:35:13 EST 2024: [create_nobody_dirs] chown nobody:nobody /store/configservices/configurationsets
Tue Jan 2 09:35:13 EST 2024: [create_nobody_dirs] mkdir -p /store/configservices/deployed
Tue Jan 2 09:35:13 EST 2024: [create_nobody_dirs] chown nobody:nobody /store/configservices/deployed
To resolve this situation, unmount the /media/updates and move the SFS to directories like /tmp, /storetmp, /store/transient. Mount the sfs file again and run the installer.
# umount /media/updates
# cp -p /store/<SFS file name> /storetmp
# mount -o loop -t squashfs /storetmp/<SFS file name> /media/updates
# /media/updates/installer
[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwtdAAA","label":"Upgrade"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
17 July 2024
UID
ibm17159524