NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
ReadyNAS Ultra 6
3 Topics
fsck failing against /dev/c/c_YYYY_MM_DD_HH24_MI
Hello. Can anyone help me to get an idea of how to fix the following.. During each boot there is fsck scheduled and I get the following in the configured email: fsck 1.42.12 (29-Aug-2014) /dev/c/c: clean, 756316/121716736 files, 940648136/1947467776 blocks fsck.ext4: Bad magic number in super-block while trying to open /dev/c/c_2013_01_13_07_00 /dev/c/c_2013_01_13_07_00: The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> everything is stored on /dev/c/c and all disks seem to be visible and without problems, i.e. I dont experience problems with accessing the data. Looking at fsck.log extract dated back to 2012 (when this error message started to pop up): ... ***** Volume maintainance: Online file system check performed at Sun Dec 30 07:00:11 2012 ***** Warning! /dev/c/c_2012_12_30_07_00 is mounted. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/c/c_2012_12_30_07_00: 98333/60817408 files (14.3% non-contiguous), 389063700/973078528 blocks ***** Volume maintainance: Online file system check performed at Sun Jan 6 07:00:12 2013 ***** Warning! /dev/c/c_2013_01_06_07_00 is mounted. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/c/c_2013_01_06_07_00: 98690/60817408 files (14.4% non-contiguous), 407680312/973078528 blocks ***** File system check performed at Wed Feb 6 04:15:48 GST 2013 ***** fsck 1.41.14 (22-Dec-2010) /dev/c/c: clean, 107283/91267072 files, 437388225/1460273152 blocks fsck.ext4: Bad magic number in super-block while trying to open /dev/c/c_2013_01_13_07_00 /dev/c/c_2013_01_13_07_00: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> ... I do not fully understand the logic behind, but it looks like for each fsck run scheduled, it makes a new device (temporarily?) named /dev/c/c_YYYY_MM_DD_HH24_MI. Everything was fine until 13.01.2013. If I remember correctly, there was a disk removal+insertion that time. And now I always get this message from the bottom.. When I remove this device so that it no longer visible in /dev/c/, it will pop up again during next fsck run.. Can anyone suggest if this is really important and how to get rid of it? Thanks, IgorSolved3.3KViews0likes7Comments
ownCloud 8.1.2 (rnxtras) fresh install failing
Did anyone manage to install ownCloud above version 8.1 on ReadyNAS R6? I'm getting some errors from the start. Owncloud was working well here until up to 8.0.X. So I decided to do a fresh install of 8.1.2 (rnxtras), which gave me the following errors: root@readyNAS:/data/OwnCloud# more owncloud.log {"reqId":"lC6uPPrO6EUF\/pAvHmWq","remoteAddr":"192.168.11.134","app":"PHP","message":"Undefined offset: 0 at \/apps\/owncloud\/web\/lib\/private\/appframework\/http\/request.php#685 ","level":3,"time":"2015-09-04T18:29:04+00:00"} {"reqId":"lC6uPPrO6EUF\/pAvHmWq","remoteAddr":"192.168.11.134","app":"PHP","message":"fopen(\/apps\/owncloud\/web\/config\/config.php): failed to open stream: No such file or direct ory at \/apps\/owncloud\/web\/lib\/private\/config.php#191","level":3,"time":"2015-09-04T18:29:05+00:00"} {"reqId":"6zhmZ7g2DtsFAQP2rij1","remoteAddr":"192.168.11.134","app":"PHP","message":"Undefined offset: 0 at \/apps\/owncloud\/web\/lib\/private\/appframework\/http\/request.php#685" ,"level":3,"time":"2015-09-04T18:31:17+00:00"} It seems the config.php file was not writable. Apart from the instanceid, the config file is empty. I guess this is triggering the other error about undefined offset at request.php#685, as this line is about the trusted host that needs to be defined in the config file. After making the config writable, and adding the necessary config, I'm stll getting a blank page. The database isn't created, and the config file seems too empty to be complete. I know that since Owncloud 8.1, they became much stricter regarding SSL, but my SSL certificate is working fine, as it was before. I'm getting the following errors in the browser: Firefox: Secure Connection Failed Chromium: No Data Received, ERR_EMPTY_RESPONSE I'm wondering if anyone managed to install the owncloud app properly, so I can rule out the possibilty that the problem lies with the ReadyNAS.7.4KViews0likes13Comments