odd raptor
I found out that one entry in our shelfs table is kinda odd to me.
We got the controller FAS 2040 Shelf 0 and DS4243 Shelf 1
(I know its very old, its also kinda just an archiv)
Does someone know how to fix the table and with which commands?
I uploaded a screenshot.
Thank you
tacit owl
looks like you lost one of the SATA disks and since you didnn't have a SATA spare, the BSAS disk was selected as spare and being reconstructed to. You should be able to just replace the disk with one of the spare SATA disks that you can barely see at the bottom of the screenshot: disk replace 0d.01.9 0c.00.7 but I would wait with that until the reconstruction of the parity disk is finished
odd raptor
Alright that sounds great. Also I found out that disk 0c.00.2 is not showing up but I checked it the bay 3 of shelf 0 is plugged in with one disk
do you know what to do in that case?
also I got 24 disks in total but it only shows 11 / 11 / 1
tribal dew
This can be because the disk isn't assigned or if the disk is broken. so try to run: "node run -node * -command disk show -n" If this shows a disk with "Not Owned" you can use the "disk assign" to assign the disk. You can also run "disk show -broken" to see if the disk is broken. In some instances the disk is "dead" and not shown as broken, and you can only see it with "node run -node * -command sysconfig -v" which should show you all your disks and it may have "broken" after its name... anyway if its broken if should be replaced... but like Darkstar mentioned, please wait until the rebuild is done...
odd raptor
also shows no broken and under sysconfig -v also nothing
I will replug it after the reconstruction and zeoering process
and check again if its getting listed properly
tacit owl
I think your cabling might be wrong, looks like you connected IOM A to IOM B on the next shelf. That wouldn't explain the missing disks though... no idea what's going on there.
try priv set advanced; disk_list and see if the disks show up there
late coyote
If it’s rebooted since failing and failed dead it may not show up at all.
odd raptor
odd raptor
If it’s rebooted since failing and failed dead it may not show up at all.
Yeah I assume its dead fully. Thanks for your expertise
I also got these errors now:
or warnings
I kinda think the system itself won't survive that long anymore or what do you guys think?
We probably should exchange it asap
late coyote
Hmmm! Not a good sign
I think we stopped selling 2040s in 2012
So.. it’s time, yes
odd raptor
Yeah I will talk to my IT manager. We definately need to order a new netapp system soonish
late coyote
If you'd like to DM me the serial number, I can let you know original purchase date 😉
odd raptor
If you'd like to DM me the serial number, I can let you know original purchase d...
Alright send you. ty
I found the disk 2 in bay 3 but it got a lot of error cnts
late coyote
yeah, the disk errors are probably causing the SAS errors
odd raptor
yeah, the disk errors are probably causing the SAS errors
ah interesting that makes sense yea
do someone know the old cmdlet for showing live logs?
in shell
late coyote
I really can't remember anymore
I found a few cases where FAS2040s had these errors and they were solved by replacing the faulty disk
"Removed and replaced disk <.> This disk was was logically missing from the system but was causing high phy change counts on the rest of the drives in the internal shelf. This was causing mailbox errors as well."
so.. sounds like this exact issue
tacit owl
this can also be caused by dust in the connectors (either between disk annd backplane, or betweenn IOM and backplane) ... you can try using compressed air to cleanup the connector with the failed disk...
silent quarry
do someone know the old cmdlet for showing live logs?
you mean this?
rdfile /etc/messages
tribal dew
The disk 01.6 looks to be a non-netapp disk as it is not reporting the vendor as NETAPP?