File System Issue on Duo is a Show Stopper

[wellsyke]

Just a suggestion:
I understand the concerns about getting data off readynas drives and Netgear should be aware that it is costing them some sales.
With this in mind would it be possible to create a VMware image that could read readynas disks and make them available as network shares? The VMware player is free although I'm not sure what OSs it's available for.

Arthur

[mdgm]

Highly doubt it.

It's not difficult to get data back at all. If your NAS dies NetGear should fix/replace it if under warranty. Otherwise pick up a NAS cheaply second hand. Put disk from slot 1 in old NAS in slot 1 in new NAS etc. Then run usb boot recovery and firmware re-install. Data should all be there and intact.

[backbohne]

I'm still struggling with compiling ext2fuse-src-0.8.1 with Skywalker patch:

Code: Select all

root@segafredo:/home/fbohnsac/e2fs/ext2fuse-src-0.8.1# ls -la /lib/libcom_err* /lib/libext2*
lrwxrwxrwx 1 root root     17 2009-04-27 11:50 /lib/libcom_err.so.2 -> libcom_err.so.2.1
-rw-r--r-- 1 root root   9576 2009-02-12 16:37 /lib/libcom_err.so.2.1
lrwxrwxrwx 1 root root     16 2009-04-27 11:50 /lib/libext2fs.so.2 -> libext2fs.so.2.4
-rw-r--r-- 1 root root 166236 2009-02-12 16:37 /lib/libext2fs.so.2.4

but:

Code: Select all

make[2]: Betrete Verzeichnis '/home/fbohnsac/e2fs/ext2fuse-src-0.8.1/src'
gcc  -g -O2   -o ext2fuse  ext2fuse-ext2fs.o ext2fuse-mkdir.o ext2fuse-readdir.o ext2fuse-symlink.o ext2fuse-wipe_block.o ext2fuse-fuse-ext2fs.o ext2fuse-perms.o ext2fuse-rename.o ext2fuse-truncate.o -lcom_err -lext2fs -lfuse
/usr/bin/ld: cannot find -lcom_err
collect2: ld gab 1 als Ende-Status zurück
make[2]: *** [ext2fuse] Fehler 1
make[2]: Verlasse Verzeichnis '/home/fbohnsac/e2fs/ext2fuse-src-0.8.1/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Verlasse Verzeichnis '/home/fbohnsac/e2fs/ext2fuse-src-0.8.1'
make: *** [all] Fehler 2

If I'm using the orginal Makefile and the internal libs it will build, but I got the same issues as alisonc:

Code: Select all

root@segafredo:/home/fbohnsac# ext2fuse /dev/c/c /mnt/test
/dev/c/c is to be mounted at /mnt/test
fuse-ext2: Can't read an inode bitmap while reading inode bitmap
ext2fuse_dbg_msg: Bad address while reading inode 2326529
ext2fuse_dbg_msg: Operation not permitted while reading inode 2326529
ext2fuse_dbg_msg: Bad address while reading inode 26214401
ext2fuse_dbg_msg: Operation not permitted while reading inode 26214401
ext2fuse_dbg_msg: Bad address while reading inode 12091393
ext2fuse_dbg_msg: Operation not permitted while reading inode 12091393
ext2fuse_dbg_msg: Bad address while reading inode 3375105
ext2fuse_dbg_msg: Operation not permitted while reading inode 3375105

Code: Select all

root@segafredo:/home/fbohnsac/e2fs/ext2fuse-src-0.8.1# ls -la /mnt/test
ls: Zugriff auf /mnt/test/backup nicht möglich: No such file or directory
ls: Zugriff auf /mnt/test/media nicht möglich: No such file or directory
ls: Zugriff auf /mnt/test/home nicht möglich: No such file or directory
ls: Zugriff auf /mnt/test/aquota.user nicht möglich: Input/output error
ls: Zugriff auf /mnt/test/aquota.group nicht möglich: Input/output error
ls: Zugriff auf /mnt/test/.timemachine nicht möglich: No such file or directory
insgesamt 36
drwxrwxrwx 7 root root 16384 2009-04-19 10:38 .
drwxr-xr-x 5 root root  4096 2009-08-14 11:14 ..
?????????? ? ?    ?        ?                ? aquota.group
?????????? ? ?    ?        ?                ? aquota.user
?????????? ? ?    ?        ?                ? backup
?????????? ? ?    ?        ?                ? home
drwx------ 2 root root 16384 2009-03-04 23:18 lost+found
?????????? ? ?    ?        ?                ? media
?????????? ? ?    ?        ?                ? .timemachine

Any ideas what's going wrong here?

ps: have installed e2fsprogs-1.41.8 + fuse-2.8.0-pre3

[Skywalker]

In your Makefile, try adding " -L/lib" to your LDFLAGS.

[backbohne]

seems that 2 symlinks have been missed.

Code: Select all

root@segafredo:/home/fbohnsac# ls -la /lib/libcom_err* /lib/libext2*
lrwxrwxrwx 1 root root     20 2009-08-18 13:02 /lib/libcom_err.so -> /lib/libcom_err.so.2
lrwxrwxrwx 1 root root     17 2009-04-27 11:50 /lib/libcom_err.so.2 -> libcom_err.so.2.1
-rw-r--r-- 1 root root   9576 2009-02-12 16:37 /lib/libcom_err.so.2.1
lrwxrwxrwx 1 root root     19 2009-08-18 13:02 /lib/libext2fs.so -> /lib/libext2fs.so.2
lrwxrwxrwx 1 root root     16 2009-04-27 11:50 /lib/libext2fs.so.2 -> libext2fs.so.2.4
-rw-r--r-- 1 root root 166236 2009-02-12 16:37 /lib/libext2fs.so.2.4

further I ran a changed configure command

Code: Select all

./configure LDFLAGS="-L/lib"

... and it works!!!

many thanks to this forum and Skywalker of cause!

-frank

[karomboe]

I am trying to compile ext2fuse with the modified makefile and using the changed configure command. But something went wrong. I have no real experiences with linux (Ubuntu) and maybe I have forgotten something very stupid.

Here are the errors after compiling:

Code: Select all

mwester@mwester-desktop:~/Dokumente/ext2fuse-src-0.8.1$ make
make  all-recursive
make[1]: Betrete Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1'
Making all in lib/et
make[2]: Betrete Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/lib/et'
make[2]: Für das Ziel »all« ist nichts zu tun.
make[2]: Verlasse Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/lib/et'
Making all in lib/ext2fs
make[2]: Betrete Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/lib/ext2fs'
if gcc -DHAVE_CONFIG_H -I. -I. -I../..    -I.. -I../et -g -O2 -MT libext2fs_a-ismounted.o -MD -MP -MF ".deps/libext2fs_a-ismounted.Tpo" -c -o libext2fs_a-ismounted.o `test -f 'ismounted.c' || echo './'`ismounted.c; \
   then mv -f ".deps/libext2fs_a-ismounted.Tpo" ".deps/libext2fs_a-ismounted.Po"; else rm -f ".deps/libext2fs_a-ismounted.Tpo"; exit 1; fi
ismounted.c: In Funktion »is_swap_device«:
ismounted.c:257: Warnung: Der Rückgabewert von »fgets«, der mit dem Attribut warn_unused_result deklariert wurde, wird ignoriert
In Funktion »open«,
    eingefügt von »check_mntent_file« bei ismounted.c:153:
/usr/include/bits/fcntl2.h:51: Fehler: Aufruf von »__open_missing_mode« mit Attributfehler deklariert: open with O_CREAT in second argument needs 3 arguments
make[2]: *** [libext2fs_a-ismounted.o] Fehler 1
make[2]: Verlasse Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/lib/ext2fs'
make[1]: *** [all-recursive] Fehler 1
make[1]: Verlasse Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1'
make: *** [all] Fehler 2
mwester@mwester-desktop:~/Dokumente/ext2fuse-src-0.8.1$


I am missing the two symlinks described by backbone:

Code: Select all

mwester@mwester-desktop:~/Dokumente/ext2fuse-src-0.8.1$ ls -la /lib/libcom_err* /lib/libext2*
lrwxrwxrwx 1 root root     17 2009-08-21 22:22 /lib/libcom_err.so.2 -> libcom_err.so.2.1
-rw-r--r-- 1 root root   9576 2009-02-12 16:37 /lib/libcom_err.so.2.1
lrwxrwxrwx 1 root root     16 2009-08-21 22:22 /lib/libext2fs.so.2 -> libext2fs.so.2.4
-rw-r--r-- 1 root root 166236 2009-02-12 16:37 /lib/libext2fs.so.2.4


Can you help me please?

[backbohne]

you just have to create the missing links with:

Code: Select all

> ln -s /lib/libcom_err.so.2.1 /lib/libcom_err.so

and

Code: Select all

> ln -s /lib/libext2fs.so.2.4 /lib/libext2fs.so

I've made an additional fix in ext2fuse, but have to look in my office laptop moday morning what

fix coming soon ...

[backbohne]

here are the missing patch:

Code: Select all

> vi +153 ./lib/ext2fs/ismounted.c

    fd = open(TEST_FILE, O_RDWR|O_CREAT, 0644);

hope it works now.

-frank

[karomboe]

Thank you for your informaton, but I think I am to blöde.
I did it like you told me. Here are the errors:

Code: Select all

root@mwester-desktop:~/Dokumente/ext2fuse-src-0.8.1# make
make  all-recursive
make[1]: Betrete Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1'
Making all in lib/et
make[2]: Betrete Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/lib/et'
make[2]: Für das Ziel »all« ist nichts zu tun.
make[2]: Verlasse Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/lib/et'
Making all in lib/ext2fs
make[2]: Betrete Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/lib/ext2fs'
make[2]: Für das Ziel »all« ist nichts zu tun.
make[2]: Verlasse Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/lib/ext2fs'
Making all in src
make[2]: Betrete Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/src'
if gcc -DHAVE_CONFIG_H -I. -I. -I..    -I/usr/include/fuse -I/usr/local/include/fuse -I../lib -I../lib/et -I../lib/ext2fs -D_FILE_OFFSET_BITS=64  -g -O2 -MT ext2fuse-readdir.o -MD -MP -MF ".deps/ext2fuse-readdir.Tpo" -c -o ext2fuse-readdir.o `test -f 'readdir.c' || echo './'`readdir.c; \
   then mv -f ".deps/ext2fuse-readdir.Tpo" ".deps/ext2fuse-readdir.Po"; else rm -f ".deps/ext2fuse-readdir.Tpo"; exit 1; fi
In Datei, eingefügt von readdir.c:1:
readdir.h:6:27: Fehler: fuse_lowlevel.h: No such file or directory
In file included from readdir.c:1:
readdir.h:8: Fehler: expected »)« before »req«
readdir.c:7: Fehler: expected »)« before »req«
readdir.c:46: Fehler: expected »)« before »req«
make[2]: *** [ext2fuse-readdir.o] Fehler 1
make[2]: Verlasse Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Verlasse Verzeichnis '/home/mwester/Dokumente/ext2fuse-src-0.8.1'
make: *** [all] Fehler 2


Maybe you will have a last idea?

[backbohne]

did you installed the package libfuse-dev it will provide /usr/include/fuse/fuse_lowlevel.h?

Code: Select all

> agt-get install libfuse-dev

I also manually installed fuse-2.8.0-pre3 which provides the same header file in /usr/local/include/fuse/fuse_lowlevel.h,
but libfuse-dev should be enough.

good luck

[backbohne]

I really support wellsyke's suggestion to provide a mini linux VMware image to have a "simple" way to mount the drives manually.

[meeow]

I also agree that there should be an easier way to read the drives should the NAS fail. Why doesn't Netgear make a bootable disk that can access the files in a read only state so that they can be copied elsewhere? They could even charge £10 for the cd if they were really tight, I know I would buy one just so that I had piece of mind if the device failed.

If Netgear aren't interested, what about anyone else doing something similar?

Alternatively, can someone right a script or something (for none linux users like myself) that formats the hard drives using 4k blocks instead of 16k so that I could then access the drives using something like Explore2fs?

[dmahon]

Highly doubt it.

It's not difficult to get data back at all. If your NAS dies NetGear should fix/replace it if under warranty. Otherwise pick up a NAS cheaply second hand. Put disk from slot 1 in old NAS in slot 1 in new NAS etc. Then run usb boot recovery and firmware re-install. Data should all be there and intact.

I'm just learning that if I upgraded from a Duo to an NV+, I would have been able to just move my disks across, but I would not be able to do this with an NVX because something is incompatable. I'm not quite sure why Netgear have had to change things so that disks became unreadable just because of a move to a different type of architecture, but they obviously did. Now, if I had a DUO and it failed, I would have to buy another DUO (or an NV+) - which is fine at the moment, but how about in two years time when they have been discontinued and replaced by x86 engine devices entirely? Relying on the instant availability of second hand equipment is not a good option. Yes, we should all have backups but we don't, and even when we do something has often changed on the drive following the backup that we'd rather not loose.

Fortunately, I bought an NVX so I should be OK for a while. However, what's to stop Netgear brining out a new product line that isn't compatable with my disks and making the x86 architecture obsolete in 5 years time? Please, Netgear, if you do, make it backwards compatable with the x86 architecture!

[mdgm]

Highly doubt it.

It's not difficult to get data back at all. If your NAS dies NetGear should fix/replace it if under warranty. Otherwise pick up a NAS cheaply second hand. Put disk from slot 1 in old NAS in slot 1 in new NAS etc. Then run usb boot recovery and firmware re-install. Data should all be there and intact.

I'm just learning that if I upgraded from a Duo to an NV+, I would have been able to just move my disks across, but I would not be able to do this with an NVX because something is incompatable. I'm not quite sure why Netgear have had to change things so that disks became unreadable just because of a move to a different type of architecture, but they obviously did. Now, if I had a DUO and it failed, I would have to buy another DUO (or an NV+) - which is fine at the moment, but how about in two years time when they have been discontinued and replaced by x86 engine devices entirely? Relying on the instant availability of second hand equipment is not a good option. Yes, we should all have backups but we don't, and even when we do something has often changed on the drive following the backup that we'd rather not loose.

Fortunately, I bought an NVX so I should be OK for a while. However, what's to stop Netgear brining out a new product line that isn't compatable with my disks and making the x86 architecture obsolete in 5 years time? Please, Netgear, if you do, make it backwards compatable with the x86 architecture!

Sparc and X86 are on different platforms and the drives etc. are setup differently. I'm sure NetGear would have had backward compatibility setup if it was practical, but it isn't (for moving disks from a Sparc ReadyNas to Sparc ReadyNas or from X86 ReadyNas to X86 ReadyNas see faq.php#How_do_I_migrate_disks_over_from_an_existing_ReadyNAS_to_another%3F) If your NVX fails completely during the warranty period of five years it will be replaced. X86 basically means it has an Intel 32-bit processor. I don't think NetGear has any reason to change to 64-bit processors any time soon. Intel 64-bit x64 processors are just too pricey for what you'd use in a NAS at least for the moment. The NVX is better than the NV+ (2-3x faster I think I read somewhere so it should be well worth it in the long run).

NetGear should still keep Duo or NV+ units available to replace units under warranty until the warranty period runs out for the last unit sold.

Also most of the time a problem just requires at worst the memory, fan or PSU being replaced. Which should all be able to be done (albeit some perhaps with a bit of difficulty) if you can buy the necessary part from NetGear.

[martin]

Hi guys,

Ive been wondering if this was possible but now i mounted my Readynas Duo disk and i see the file structure it is ok but the filesizes are wrong. anyone the same problem ?

original structure

Code: Select all

root@hannes2:/backup# ls -la
total 140831748
drwxrwxrwx  1 root root           0 2009-08-11 10:06 .
drwxr-xr-x 24 root root        4096 2009-03-13 13:57 ..
-rwxrwSrwx  1 root root           0 2009-08-11 10:06 gzip
-rwxrwSrwx  1 root root 87909918720 2009-09-23 00:00 hannes-shares.tar
drwxrwxrwx  1 root root           0 2009-03-13 15:32 ldap
-rwxrwSrwx  1 root root 16597084160 2009-09-23 02:18 profile-shares.tar
drwxrwxrwx  1 root root           0 2009-06-02 12:39 restored
-rwxrwSrwx  1 root root 16321050612 2009-08-11 10:06 zarafa-full-11-jul-2009.sql
-rwxrwSrwx  1 root root 10609398284 2009-05-12 10:49 zarafa-full-12-mei-10-49.sql.gz
-rwxrwSrwx  1 root root 12735055416 2009-09-23 04:00 zarafa-full.sql.gz

Structure found in mounted disk

Code: Select all

root@test01:/mnt/lvm/backup# ls -la
total 140828160
drwxr-xr-x 4 1003 root         16384 2009-08-11 10:06 .
drwxrwxrwx 6 root root         16384 2009-07-02 09:45 ..
-rw-rw-rw- 1 1003 libuuid          0 2009-08-11 10:06 gzip
-rw-rw-rw- 1 1003 libuuid 2010572800 2009-09-23 00:00 hannes-shares.tar
drwxrwxrwx 2 1003 libuuid      16384 2009-03-13 15:32 ldap
-rw-rw-rw- 1 1003 libuuid 3712182272 2009-09-23 02:18 profile-shares.tar
drwxrwxrwx 3 1003 libuuid      16384 2009-06-02 12:39 restored
-rw-rw-rw- 1 1003 libuuid 3436148724 2009-08-11 10:06 zarafa-full-11-jul-2009.sql
-rw-rw-rw- 1 1003 libuuid 2019463692 2009-05-12 10:49 zarafa-full-12-mei-10-49.sql.gz
-rw-rw-rw- 1 1003 libuuid 4145120824 2009-09-23 04:00 zarafa-full.sql.gz


ext2fuse logs following when i open a file:

Code: Select all

ext2fuse_dbg_msg: File not found by ext2_lookup while looking up ".zarafa-full-11-jul-2009.sql.swp"
ext2fuse_dbg_msg: File not found by ext2_lookup while looking up ".zarafa-full-11-jul-2009.sql.swp"
ext2fuse_dbg_msg: File not found by ext2_lookup while looking up ".zarafa-full-11-jul-2009.sql.swx"
ext2fuse_dbg_msg: File not found by ext2_lookup while looking up ".zarafa-full-11-jul-2009.sql.swx"
ext2fuse_dbg_msg: File not found by ext2_lookup while looking up ".zarafa-full-11-jul-2009.sql.swp"
ext2fuse_dbg_msg: File not found by ext2_lookup while looking up ".zarafa-full-11-jul-2009.sql.swp"
ext2fuse_dbg_msg: File not found by ext2_lookup while looking up ".zarafa-full-11-jul-2009.sql.swp"
ext2fuse_dbg_msg: File not found by ext2_lookup while looking up ".zarafa-full-11-jul-2009.sql.swp"