NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
PSU not detected after upgrade to FW 6.9.1
After upgrading to FW version 6.9.1 from 6.8.x i see log messages that indicate PSU1 not detected and PSU2 not detected. The unit is populated with 12 4TB drives. I've attempted to upload the logs ...
This past weekend I was able to shut down the unit, remove the power cords, remove the power supplies, release the drives from each slot and blow out any dust (there was no visible dust inside the unit and while compressed air was blowing there was no visible dust being displaced) and clean any dirt from the contacts on the back of the power supplies (there was no visible difference after cleaning the contacts.
The unit was reassembled and powered up. Since 6.9.2 had been downloaded it was installed as the machine rebooted.
Upon accessing the GUI the power supplies were both shown as installed and functioning.
While the problem is solved I'm not 100% sure that dirt was the problem and the reappearance of the power supplies could be associated with the extended amount of time the unit was powered down.
I sent in a set of logs earlier this wek via email per the iinstrucions. I havent tried to disable just the PSU messages, it should be possible but it appears that the GUI does not have that level of granularity.
I checked your log, there is i2c error, I need to check with HW developter what problem happen on this device.
Jan 18 12:10:01 apollo CRON[21692]: (root) CMD (/bin/bash /opt/replication/etc/init.d/watchdog.sh) Jan 18 12:10:01 apollo CRON[21688]: pam_unix(cron:session): session closed for user root Jan 18 12:10:01 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:01 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:02 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:02 apollo rn-expand[4952]: PSU read voltage b2 err [-11] state [0], will retry[retry=4]. Jan 18 12:10:02 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:02 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:12 apollo kernel: i2c_nct6775_xfer: data timed out addr:58 cmd:88 Jan 18 12:10:12 apollo kernel: i2c_nct6775_xfer: data timed out addr:58 cmd:88 Jan 18 12:10:13 apollo kernel: i2c_nct6775_xfer: data timed out addr:58 cmd:88 Jan 18 12:10:13 apollo kernel: i2c_nct6775_xfer: data timed out addr:58 cmd:88 Jan 18 12:10:13 apollo rn-expand[4952]: PSU read voltage b0 err [-11] state [0], will retry[retry=4]. Jan 18 12:10:13 apollo kernel: i2c_nct6775_xfer: data timed out addr:58 cmd:88 Jan 18 12:10:13 apollo kernel: i2c_nct6775_xfer: data timed out addr:58 cmd:88 Jan 18 12:10:13 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:14 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:14 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:14 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:14 apollo rn-expand[4952]: PSU read voltage b2 err [-11] state [0], will retry[retry=4]. Jan 18 12:10:14 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:14 apollo kernel: i2c_nct6775_xfer: data timed out addr:58 cmd:78 Jan 18 12:10:15 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:88 Jan 18 12:10:15 apollo kernel: i2c_nct6775_xfer: data timed out addr:59 cmd:78 Jan 18 12:10:19 apollo snapperd[6268]: THROW: subvolume is not a btrfs subvolume Jan 18 12:10:19 apollo snapperd[6268]: reading failed
I debugged one RMA RN3220 with this problem. It turned out that the problem might be related to pollutant in the air :(
See attached picture, the black dust has weak conductivity, resulted I2C bus voltage drop on backplane. While it does not affect backplane I2C bus operation, it does affect I2C bus buffer for PSU PMBus which is sensitive to voltage level. I cleaned up backplane using dust blower, the system was back to normal.
If PSU is not detected right after boot up. Would appreciate if you can try this and report back:
1. Gracefully shutdown NAS
2. Take out all hard drives(keep it in order and put back in same order later even though this is not needed)
3. Visual inspect if there is excessive dust on backplane. Use compressed air can to clean up backplane, especially the area with components. You can also get access of back of backplane by removing top cover if clean from front does not recover the PSU monitoring
4. Replace drive(and cover)
5. Check if PSU is found, chance is it will.
While your suggestion is excellent in this case it is probably not the case. The units operate in a temperature controlled clean environment. While it is not as clean as a true clean room the air is still very clean. So clean that units operating a year or more will have no visible dust on the fan grills or inside. In addition this issue began on the reboot immediately following the update to 6.9.1 from 6.8.x so it is likely related to that change rather than an hardware issue.
Since this unit is a storage domain for a virtual server environment I will have to wait until the maintenance window is available to take it offline and open the cover to clean the backplane (both on the drive side and on the back side) as well as the PSU connection points.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
