Unable to add disk to array

Question

Hello everyone,&nbsp;We have an F5 7000S that we have purchased new in 2013 and kept it running pretty much 24/7 all this time.After a datacenter outage one of the drives in the device died. We have replaced it with another disk, but addig it back into the array using GUI gives "NO access" error.Attempting to follow&nbsp;https://my.f5.com/manage/s/article/K12756&nbsp;does not help.When executing from command line the following error is given:tm_install::process::Proces_array_member_add --sdb ownership is noneThe F5 is still running 11.4.1.The replacement disk is of bigger capacity (2TB instead of 1TB).Does anyone know of this specific error - searching this forum and internet returns nothing. I wonder if this is fixed in later OS images or maybe F5 refuses to work with different disk sizes (most normal raids can accept bigger disk as replacement)&nbsp;Any help is apprecaited!

ca_valli · Answer

I'm guessing the replacement disk you installed was not F5-supplied, correct?&nbsp;First thing I'd check is if it's being seen by the unit, do the LEDs blink? What's the output of&nbsp;tmsh show sys raid disk ?
Also, what procedure did you use to unmount the disk? Did you remove it from the array before switching it as detailed in&nbsp;https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/platform-b7000/4.html#c_reuse_fru_hd_about&nbsp;?&nbsp;

ca_valli · Answer

Thanks for the outputs.So, let's go back to the output log in your first query. SD-A and SD-B should be the the lables of the disk in the array. In your log, it refers no ownership to SD-B so there might still be issues with "accepting" the new disk even if output shows it's present.&nbsp;
Try running these commands:
dmesg |grep --color sd[a-b]sfdisk -l /dev/sdb&nbsp; &nbsp; # I think new disk should be seen as sdb while existing should be sda&nbsp;sfdisk -l /dev/sda
If they return disk as failed, or if they return no output, the problem is the new disk, likely.&nbsp;One more question, just fr myself to understand this better -- what was the status of the old disk that was removed?&nbsp;
I'd also like to check if the&nbsp;linux subsystem sees the same status of the array as well .. Can you run&nbsp;array&nbsp;command too?&nbsp;You'll want to confront its output with the following tmsh commands (again - just to confirm again disk status)tmsh list /sys disk all-properties&nbsp; &nbsp;# should list both diskstmsh show sys raid&nbsp; &nbsp;# it's like the one I gave u last time, just has more output&nbsp;
Last thing would be checking if the&nbsp;mdadm process is running and in sync -- but I'm not sure if it already exists in version v11, and anyways having a disk in that status will likely result in bad output for the mdadm.&nbsp;
&nbsp;grep -e "_U" -e "U_" -e "__" /proc/mdstat | wc -l
&nbsp;

ca_valli · Answer

I've reviewed this further.According to&nbsp;https://my.f5.com/manage/s/article/K15525 (old article, but should be relevant for your version) we should perform a logical rebuild of the RAID array.
This brings us back, again, to that ownership log.If you run the following command:&nbsp; &nbsp;&nbsp;ls /dev/ -l | grep sd&nbsp;do you see different permissions assinged to the sda* / sdb* partitions?&nbsp;

&nbsp;
If that's the case (my suspect would be SDB1 to SDB4 do not have the root:disk ownership) , I think&nbsp;&nbsp;that you'll need to change owner and/or permissions of the mount.However!Before attemtping to change the permissions, I would try to perform a physical rebuild of the array.
According to&nbsp;https://my.f5.com/manage/s/article/K12756#logical%20rebuild&nbsp;
steps would be:0- backup configuration in an ucs archive and copy it to another system1- shut down the device2- remove "bad" drive3- start device with single disk and wait for RAID master to be assigned to remaining drive4- shutdown device again5- reinsert drive6- start appliance7- (my addition) potentially check for this&nbsp;https://my.f5.com/manage/s/article/K12380
If this still fails, you might want to try with changing permissions + logical rebuild of the array ..
&lt;&lt; Disclaimer &gt;&gt; I would normally suggest you to contact support for this type of issue but I recognize software has been out of support for quite a long time. Use at your own risk.&nbsp;This would be done via:&nbsp;chown root:disk&nbsp;&lt; /path/to/the/mount &gt;&nbsp; ## check group name (disk) via ls -l /dev/&nbsp; as said beforechmod g+rw&nbsp;&lt; /path/to/the/mount &gt;tmsh modify sys raid array &lt;array name&gt; remove &lt;disk name&gt; ## might not be required -- disk name should be HD2, I guess?tmsh modify sys raid array &lt;array name&gt; add &lt;disk name&gt;

michael09 · Answer

The error "tm_install::process::Process_array_member_add --sdb ownership is none" suggests that there may be a configuration or ownership issue with the replacement disk on your F5 7000S running OS version 11.4.1. Since the replacement disk is of a bigger capacity, it's possible that the RAID configuration is not recognizing the new disk properly. Consider updating the F5 OS to the latest available version, as newer versions may have addressed compatibility issues with different disk sizes.

nycdude · Answer

That is correct.The replacement disk is a Samsung EVO 870 SSD.I tried replacing it with the same identical vendor (not F5 sourced though) WD-Velociraptor 1TB, but the results are the same.here is the output of the command. The disk is recognized, just wont add to raid.---------------------------------------------------------------------Sys::Raid::DiskName Serial Number Array Array Status ModelMember---------------------------------------------------------------------HD1 WD-WXR1E63HMUYD yes ok ATA WDC WD1000CHTZ-0HD2 S6PNNJ0W412826X no undefined ATA Samsung SSD 870

Forum Discussion

Unable to add disk to array

Recent Discussions

RECOVER LOST OR STOLEN CRYPTO ASSETS THROUGH CYBER CONSTABLE INTELLIGE

ASM Sync Between 2 Data Centers

Glucovate Blood Sugar Support Review (2024-2025): Pros, Cons, and Potential Side Effects

F5 Hotfix

Bypass "Bad unescape" in Body POST (ASM, POST, JSON)

Related Content

Disk space full

Arrays

Lock and Key - Encrypting EBS Disk Volumes for BIG-IP AWS Deployments

Unable to access GUI

iRule: List vs Array