NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
scottonaharley
Dec 06, 2017Aspirant
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 but the zip file is not accepted. Furthermore only jpg,gif,png,pdf are the only file types accepted. Am I expected to convert every file contained log download from .log (text) to a pdf?
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.
13 Replies
Replies have been turned off for this discussion
- evan2NETGEAR Expert
I checked my RN4220X, RN4220S and RN3220, PSU works OK after update to 6.9.1,
Cloud do you please send log and let us check?
How do I send all logs to ReadyNAS Community moderators?
https://kb.netgear.com/21543/How-do-I-send-all-logs-to-ReadyNAS-Community-moderators- scottonaharleyAspirant
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.
- evan2NETGEAR Expert
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
- StephenBGuru - Experienced User
scottonaharley wrote:
Am I expected to convert every file contained log download from .log (text) to a pdf?
No. You shouldn't post the log zip here, as there is some personal information in them that will then be accessible to the whole planet.
You are supposed to email the zip using the instructions here: https://kb.netgear.com/21543/How-do-I-send-all-logs-to-ReadyNAS-Community-moderators
Another approach is to PM (private message) the mod, and send a link to the log zip (using google drive, dropbox, ...). You send a PM using the envelope link in the upper right of the forum page.
Either way, normally logs aren't sent unless a mod requests them (and they are directed to that mod).
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!