NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ultra 4: Getting off on the wrong foot
Using RAID 5. Access method is AFP. Using Snow Leopard 10.6.8, but might have updated from 10.6.7 through all the activity. Started life with firmware 4.2.15. As concise as I can put it: • Inst...
I did the firmware update the same way again to be sure. I watched the "Booting... Updating FW" on the display, and then "Booting...". I was unable to mount AFP still.
Next, I enabled a "volume scan" on reboot, then rebooted. I assume that is what you meant by a file system check. No luck after that either.
I re-downloaded the Frontview -> System -> Config Backup -> Backup and complete logs and the error is the same and the netatalk still has my DNS information in it. Is it possible that netatalk is not getting cleaned up in the OS Reinstall???
When you are asking about what disk I used as the replacement, you are going back in history a little bit. At first, when the ReadyNAS said disk 2 failed, I shut down cleanly, then immediately replaced the disk with a new disk right out of the box. I did that a couple times assuming the disk did actually fail. You see that with new drives from time to time. However statistical improbability quickly suggested it wasn't the disk.
The last time disk 2 "failed", I did the reboot WITHOUT scan, and it treated the disk like it was new and synced that, then I never saw issues again. If I had to ship another disk back to the dealer, the NAS was going with it. :-(
All the logs I saw in Frontview -> Status -> Logs suggested to me it was just a software error.
I really don't think it is a hardware issue, I think it is software. I hope I had a bad firmware or 2 causing the "disk failures" and hope I am now past that, but this pesky AFP and SMB share issue is getting in the way.
[UPDATE] SMB mounting seems to work now. I am almost tempted to modify the Configuration backup to correct Netatalk myself, and restore. :-)
Next, I enabled a "volume scan" on reboot, then rebooted. I assume that is what you meant by a file system check. No luck after that either.
I re-downloaded the Frontview -> System -> Config Backup -> Backup and complete logs and the error is the same and the netatalk still has my DNS information in it. Is it possible that netatalk is not getting cleaned up in the OS Reinstall???
When you are asking about what disk I used as the replacement, you are going back in history a little bit. At first, when the ReadyNAS said disk 2 failed, I shut down cleanly, then immediately replaced the disk with a new disk right out of the box. I did that a couple times assuming the disk did actually fail. You see that with new drives from time to time. However statistical improbability quickly suggested it wasn't the disk.
The last time disk 2 "failed", I did the reboot WITHOUT scan, and it treated the disk like it was new and synced that, then I never saw issues again. If I had to ship another disk back to the dealer, the NAS was going with it. :-(
All the logs I saw in Frontview -> Status -> Logs suggested to me it was just a software error.
I really don't think it is a hardware issue, I think it is software. I hope I had a bad firmware or 2 causing the "disk failures" and hope I am now past that, but this pesky AFP and SMB share issue is getting in the way.
[UPDATE] SMB mounting seems to work now. I am almost tempted to modify the Configuration backup to correct Netatalk myself, and restore. :-)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
