Steps to perform maintenance on a node in PetaSAN 4.0.0

uduggireddy
6 Posts
December 9, 2025, 1:07 pmQuote from uduggireddy on December 9, 2025, 1:07 pmHi team,
Can you please help me with the steps and details that needs to be checked before doing maintenance and how to perform maintenance
Hi team,
Can you please help me with the steps and details that needs to be checked before doing maintenance and how to perform maintenance

admin
3,054 Posts
December 10, 2025, 4:41 amQuote from admin on December 10, 2025, 4:41 amCan you tell what sort of maintenance, replace disk ? remove node ? add disk ? ...
Can you tell what sort of maintenance, replace disk ? remove node ? add disk ? ...

uduggireddy
6 Posts
December 10, 2025, 10:07 amQuote from uduggireddy on December 10, 2025, 10:07 amWould like to know the process for disk replacement and also node reboot
Would like to know the process for disk replacement and also node reboot

admin
3,054 Posts
December 10, 2025, 2:02 pmQuote from admin on December 10, 2025, 2:02 pmTo replace a defective OSD, delete it from UI, physically add a new disk, then in UI press + button next to the new disk and add it as OSD.
It is possible to reboot a node without doing any additional actions, since the system is highly available and will deal with failures and recoveries.
But optionally, it is better but not a must:
- Move any paths of services from node to be rebooted to another node. This is not a must, but will make client i/o freeze for a shorter time.
- In UI Maintenance menu, set the no out flag before stopping the node, and return it to normal when node is up. This is not a must, but tells Ceph not to bother initiating a recovery since you know the node will be up soon. However if the node will be down for a long time, do not do this as you do want the normal recovery ( recreating lost replica) to go on.
To replace a defective OSD, delete it from UI, physically add a new disk, then in UI press + button next to the new disk and add it as OSD.
It is possible to reboot a node without doing any additional actions, since the system is highly available and will deal with failures and recoveries.
But optionally, it is better but not a must:
- Move any paths of services from node to be rebooted to another node. This is not a must, but will make client i/o freeze for a shorter time.
- In UI Maintenance menu, set the no out flag before stopping the node, and return it to normal when node is up. This is not a must, but tells Ceph not to bother initiating a recovery since you know the node will be up soon. However if the node will be down for a long time, do not do this as you do want the normal recovery ( recreating lost replica) to go on.
Last edited on December 10, 2025, 2:03 pm by admin · #4
Steps to perform maintenance on a node in PetaSAN 4.0.0
uduggireddy
6 Posts
Quote from uduggireddy on December 9, 2025, 1:07 pmHi team,
Can you please help me with the steps and details that needs to be checked before doing maintenance and how to perform maintenance
Hi team,
Can you please help me with the steps and details that needs to be checked before doing maintenance and how to perform maintenance
admin
3,054 Posts
Quote from admin on December 10, 2025, 4:41 amCan you tell what sort of maintenance, replace disk ? remove node ? add disk ? ...
Can you tell what sort of maintenance, replace disk ? remove node ? add disk ? ...
uduggireddy
6 Posts
Quote from uduggireddy on December 10, 2025, 10:07 amWould like to know the process for disk replacement and also node reboot
Would like to know the process for disk replacement and also node reboot
admin
3,054 Posts
Quote from admin on December 10, 2025, 2:02 pmTo replace a defective OSD, delete it from UI, physically add a new disk, then in UI press + button next to the new disk and add it as OSD.
It is possible to reboot a node without doing any additional actions, since the system is highly available and will deal with failures and recoveries.
But optionally, it is better but not a must:
- Move any paths of services from node to be rebooted to another node. This is not a must, but will make client i/o freeze for a shorter time.
- In UI Maintenance menu, set the no out flag before stopping the node, and return it to normal when node is up. This is not a must, but tells Ceph not to bother initiating a recovery since you know the node will be up soon. However if the node will be down for a long time, do not do this as you do want the normal recovery ( recreating lost replica) to go on.
To replace a defective OSD, delete it from UI, physically add a new disk, then in UI press + button next to the new disk and add it as OSD.
It is possible to reboot a node without doing any additional actions, since the system is highly available and will deal with failures and recoveries.
But optionally, it is better but not a must:
- Move any paths of services from node to be rebooted to another node. This is not a must, but will make client i/o freeze for a shorter time.
- In UI Maintenance menu, set the no out flag before stopping the node, and return it to normal when node is up. This is not a must, but tells Ceph not to bother initiating a recovery since you know the node will be up soon. However if the node will be down for a long time, do not do this as you do want the normal recovery ( recreating lost replica) to go on.