DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2007-07-30 19:31:35

cyboc
Member
From: Vancouver, BC, Canada
Registered: 2007-07-14
Posts: 27
Website

fw version 1.03, RAID 1 and Corrupted Files

Configuration:
- Firmware version 1.03
- RAID 1
- Two identical drives: Seagate Barracuda 7200.10 500GB SATA2 3GB/S 7200RPM 16MB Cache NCQ Hard Drive (ST3500630AS).

I have created several large files (about 700 MB) on my Windows box and I have transferred them over to the DNS323 via Samba shares. I ran md5sum on all of the files on both the windows box and the DNS. Unfortunately, about 10% of the files on the DNS have a bad md5sum. Furthermore, on some of the files on the DNS, md5sum doesn't even output a value! The funny thing is, when I transferred the files, there were NO error messages. That gives you a false sense of security.

Troubleshooting:
- Deleted the files on the DNS and tried again. I got bad md5sums again, but NOT on the same files as the first try. Hmn.
- Transferred the files from the Windows box to a different Linux box using Samba. This linux box has Samba 3. Good md5sums this time.
- Transferred the files with FTP. md5sums were good.

Has anyone else seen similar behavior? Is Samba 2.2.8a to blame? Is RAID to blame? Could it be something else?

I wanted to use this box at the office for archiving infrequently used files. But now I'm having second thoughts after seeing this weird behavior.  The ironic thing is that the box that the DNS came in says "Protect your important files by making regular backups to mirrored hard drives using RAID 1 Technology." Haha. Yeah...right.


Well, I don't think I'll be using this thing at the office. Too risky. I might hold on to it strictly for research purposes. It is a fun box for playing with.


"If you feel yourself irreplaceable, put a finger in a glass of water. If you leave a hole when you take it out, you truly are irreplaceable."

Offline

 

#2 2007-07-31 02:54:35

fonz
Member / Developer
From: Berlin
Registered: 2007-02-06
Posts: 1716
Website

Re: fw version 1.03, RAID 1 and Corrupted Files

cyboc wrote:

Has anyone else seen similar behavior? Is Samba 2.2.8a to blame? Is RAID to blame? Could it be something else?

There have been reports about corrupted (and disasspearing) files before - but iirc for firmwares before 1.02, only. I don't think the samba version changed (they've added bug fixes, though, eg. the 2G fix that tobyg came up with: http://dns323.kood.org/forum/p1419-2007 … html#p1419). Also, RAID1 was unreliable, but some say it improved in 1.03, too.

Offline

 

#3 2008-03-26 21:43:36

Deadbeef
Member
From: Maastricht, The Netherlands
Registered: 2008-03-26
Posts: 8
Website

Re: fw version 1.03, RAID 1 and Corrupted Files

I'm a new user of an Conceptronic CH3SNAS using firmware 1.03b6a
It really scared me to read Raid1 is possably unreliable.

Is this old news and shouldn't I worry with this version (1.03b6a ) of the firmware.
Or is it a still ongoing issue?

The aroundMyRoom website warns of possible corruption errors with the latest 1.03 (final) firmware.
"Important info: 1.03Final can cause files to become corrupted when copying data with an alternative copy tool, like: Total Commander and/or TeraCopy etc. This has been reported by several users and I could finally reproduce it today."

I use Total Commander (what else is there wink) and filesynchronisation software to copy specific directories from different PC's to the NAS.
I use this businesswise to keep copies of my work. (www.KennethTan.nl)

The NAS is UN-funplugged (yet)

Kenneth

Offline

 

#4 2008-03-26 21:54:13

blahsome
Member
Registered: 2008-03-02
Posts: 157

Re: fw version 1.03, RAID 1 and Corrupted Files

Well, you could break the RAID1 and use Standard (i.e. two independent volumes). See if that "fixes" your problem. If so, you know it's RAID-related. I would then rebuild the RAID1 array again just to make sure your previous RAID1 build wasn't somehow broken.

If that's not the source of your problem, you can always upgrade the firmware to 1.04, which uses Samba 3, I believe. Reformat all drives and try again.

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB