it says: mounting fs with errors, running e2fsck is recommended

tried e2fsck -b /dev/xxx
4096, 8193, 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,102400000, 214990848

bad magic number in super-block while trying to open /dev/xxx

encrypted ext4 partition - gpt file system - raid 5 system

is this normal on ext4 partition, should i try zfs? am near capacity, is that a possibility? this is the 3rd time i got this and fsck fixed this in the past. tia

What errors? Does your syslog say someting?
Try tune2fs -l /dev/xxx next time, just to see what's in that superblock. Apart from the magic number, do the other values make sense?

I don't think it's normal that the superblock is corrupted on any type of filesystem, even when getting full.

Couldn't find valid filesystem superblock when running tune2fs -l. syslog doesn't say anything and hasn't said anything other than to run the e2fsck. got the other values by googling.

When are you getting this? During bootup? Is it pointing to a certain partition?

during mounting

Any hard shutdowns lately (brownouts, blackouts, etc)? You do properly shut down the nas every time you power it off, yes?

it never goes off, nothing like that