NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Error making EXT3 filesystem on the USB device
Like every 6 monthes, I wanted to back up a share on an external drive and followed my usual procedure: plug a USB drive on my NVX, format the drive (EXT3) and launch the job.
Surprisingly, the NVX refused to format the drive, here is what I got in the system.log:
As you can see, it was possible to format the drive with FAT32, but not with EXT3. The NVX runs latest radiator: 4.2.24
I tried at home with my Ultra2+ (raidator 4.2.23), and I could format the drive in EXT3 (and the NVX is now doing the backup job).
Last time I tried, and succeded, to format the USB drive on the NVX, it was still running raidator 4.2.22
Is it a known issue (I couldn't find anything on the forum!)?
p
Surprisingly, the NVX refused to format the drive, here is what I got in the system.log:
Jul 26 12:10:25 BU-2TbRaid exportfs[15263]: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/USB_HDD_2". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x
Jul 26 12:10:25 BU-2TbRaid exportfs[15263]: /proc/fs/nfs/exports:1: unknown keyword "test-client-(rw"
Jul 26 12:11:53 BU-2TbRaid RAIDiator: Error making EXT3 filesystem on the USB device. [USB_HDD_2]
Jul 26 12:12:58 BU-2TbRaid RAIDiator: Successfully created FAT32 file system on the USB device. [USB_HDD_2]
As you can see, it was possible to format the drive with FAT32, but not with EXT3. The NVX runs latest radiator: 4.2.24
I tried at home with my Ultra2+ (raidator 4.2.23), and I could format the drive in EXT3 (and the NVX is now doing the backup job).
Last time I tried, and succeded, to format the USB drive on the NVX, it was still running raidator 4.2.22
Is it a known issue (I couldn't find anything on the forum!)?
p
53 Replies
Replies have been turned off for this discussion
- I've got the same problem with an ReadyNAS 2100 running Raidiator 4.2.27 (the latest one).
Can you confirm that it's still the same source of the problem, namely the e2fslibs being a buggy version which needs to be updated?
As I'm not a Linux guy, I didn't tinker with the ReadyNAS in any way, yet. Actually, I am a bit terrified that I'd have to, now... ;) - This is a known issue. It should work on 4.2.26.
- Is it possible to safely downgrade to 4.2.26?
Do you know when 4.2.28 will be out, with this issue hopefully fixed?
Thanks! - You can safely downgrade, but you will lose some security fixes for Bash, OpenSSL and Samba (in particular shellshock).
If you allow web access to the NAS over the internet then your NAS would be hackable. - Thanks for your answer!
Nonetheless I would prefer not having to downgrade, hence my question: Do you know when this issue will be fixed, probably via the next firmware version (4.2.28?)? When can one expect it to be released?
Thanks! - I don't have any ETA on that, but yes hopefully it will be fixed in that.
- This has been fixed internally so the fix will be in 4.2.28.
If you are comfortable with SSH you can install the fix from our 4.2.28 repository.
First edit /etc/apt/sources.list to use the 4.2.28 repository using vi
# vi /etc/apt/sources.list
Then do
# apt-get update
# apt-get install e2fslibs
Then edit /etc/apt/sources.list to use the 4.2.27 repository again
# vi /etc/apt/sources.list
# apt-get updateI had the same fault adding a new internal volume on my NAS.
While the fix from mdgm worked, and thankyou for that, its really fustrating that it took a good bit of googling to find the answer and I've disposed of a disk that I suspect was perfectly fine as I couldn't get it to create a file system... Perhaps serious faults such as not being able to create new volumes should have a bot more publicity about them...
David.
- I started this topic almost 2 years ago and this bug is still not fixed! Is there any hope to get 4.2.28 in the future or did this system reached its eol?
In the meantime I'll try your work around… - I'd be highly interested in that, too!
As of yet, I haven't done a backup in months due to this error; and I'm not tech-savvy enough that the manual update procedure of this particular component would go smooth and without hassles.
It's sad, because it affects a ReadyNAS 2100 which was once sold as a business-unit. Having to wait forever for a fix this critical is unacceptable. I was planning on upgrading the 4x1TB-disks to larger ones, but given the support situation I'm reconsidering and also thinking of other manufacturers... - 4.2.28 beta is available now (viewtopic.php?f=51&t=70385)
This problem looks like the "divide by 0" issue fixed in T5. If so, the beta fix was available last February.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
