4.2.31 on my Ultra 6 has killed my NAS? Drive is read only and frontview hangs.
So I logged into my Ultra 6 and noticed there was a firmware upgrade available from May 2017! Since I get at least two emails from my NAS every day I assume it should have emailed me about this, but anyway, that's a minor problem.
I installed the upgrade and then.... time machine no longer worked. My two laptop macs no longer could log in. I rebooted the ReadyNAS (since sometimes it gets in a mode where nothing can log into it) and it didn't help.
Probing a little further, I attempted to change the Time Machine access password to be sure I had it correct. The web interface hung! A hard reset and disk check later and some errors were corrected.
All SMART reading good and no errors.
So I tried again. Same result. Every time I tried to change the time machine access password the UI and effectively the ReadyNAS hung.
The next step was re-installing the OS, using the reset hole and front panel buttons. I did this. Another disk check.
Now I can attempt to change the time machine access password and it appears to work, except the "volume size" of the time machine space is set back to the default 3000 every time I apply changes.
Digging deeper, it appears my partitions are mounted read-only which would explain a lot.
# touch /c/doc/SymformContrib/delete_this
touch: cannot touch `/c/doc/SymformContrib/delete_this': Read-only file system
During boot in kern.log I have this
EXT4-fs error (device dm-0): ext4_mb_generate_buddy:726: group 10 blocks in bitmap, 32768 in gd
Sep 14 10:59:30 sleepy kernel: Aborting journal on device dm-0-8.
Sep 14 10:59:30 sleepy kernel: EXT4-fs (dm-0): Remounting filesystem read-only
Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted
Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted
Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_ext_remove_space:2437: Journal has aborted
Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted
Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_orphan_del:2098: Journal has aborted
Sep 14 10:59:31 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted
The first line seems to be some Linux bug which may have been fixed.
My data is there. The filesystem is read only. This seems to be showing up other bugs (such as the entire device hanging).
Does anyone have any suggestions beyond "Backup your 12GB data, install OS6 and start again"?
Many thanks in advance.
Model: ReadyNAS RNDU6000|ReadyNAS Ultra 6 Chassis only
Re: 4.2.31 on my Ultra 6 has killed my NAS? Drive is read only and frontview hangs.
Clearly the file system has corruption, you also need to confirm the disk health.
What do you see in disk_smart.log (reallocated, current pending sectors, offline uncorrectable, etc)? Have you gotten any email alerts related to disk health?
redpola wrote: Does anyone have any suggestions beyond "Backup your 12GB data, install OS6 and start again"?
OS-6 would be up to you. You hopefully realize that your data is at risk, so you should be backing up what you can.
Re: 4.2.31 on my Ultra 6 has killed my NAS? Drive is read only and frontview hangs.
All fine. The filesystem has no corruption.
I need to get to the bottom of this before I go for OS 6. I'd rather my device worked the same as it did before the OS upgrade. Is it possible to downgrade?
Re: 4.2.31 on my Ultra 6 has killed my NAS? Drive is read only and frontview hangs.
The changes in 4.2.31 were mainly security patches - nothing that would cause disk corruption. So I don't think this is upgrade related (despite the timing). You can certainly downgrade if you want to.
