[nas-2000] Re: new firmware from raidsonic: 2.3.2.IB.2.RS.1

  • From: "Christian Wolf" <wolfchri@xxxxxxxxx>
  • To: nas-2000@xxxxxxxxxxxxx
  • Date: Fri, 28 Sep 2007 09:19:21 +0200

With 2.3.2.IB.RS.1, I do not have this problems anymore (had the same
problerms with the 1.x firmware). However, with the very latest
firmware from the raidsonic.de site, the problems are back - system
hangs and needs cold start when copying large files (>400-500 MB) TO
the NAS via NFS, and worse now, with the latest firmware, also via
FTP. Reading from the NAS is no problem.

Again: 2.3.2.IB.RS.1 is OK, also the 2.3.2-Beta, but the latest
2.3.2.IB.RS.2 (currently  2_3_2_IB_2(20070309).tar.gz) suffers from
the same bug as did 1.x

So try the 2.3.2.IB.RS.1, it is ok for me. It is (fortunately!!!!)
still available here from Raidsonic:
http://www.raidsonic.de/de/pages/service/driver.php (scroll down)

And no, this is definitely no thermal problem, at least not here. I
can reproduce it any time with NFS on a IB 1000 (no fan) and it works
on the same machine with the other firmware. I am also using tracker
on the NAS (very high system usage for the NAS during indexing my
15000 fotos) and that makes no problems. Just writing large files.

Here is my log (FTP - NAS did not produce anything).

Jan 7 03:58:32   restart.
Jan 7 03:58:33  crond 2.3.2 dillon, started, log level 8
Sep 25 13:06:14 crond 2.3.2 dillon, started, log level 8
Sep 25 15:06:17 restart.
Sep 25 15:06:28 crond 2.3.2 dillon, started, log level 8
Sep 25 15:06:30 Power management is enabled !!!
Sep 25 15:06:30 crond 2.3.2 dillon, started, log level 8
Sep 25 15:06:32 ^MStarting pid 1309, console /dev/console: '/sbin/getty'
Sep 25 15:08:26 mod_delay/0.5: error opening DelayTable
'/var/run/proftpd/proftpd.delay': No such file or directory
Sep 25 15:08:26 ProFTPD 1.3.0 (stable) (built ¶g¤@ 3¤ë 5 09:03:17 CST
2007) standalone mode STARTUP
Sep 25 15:11:44 authenticated mount request from 192.168.1.34:965 for
/mnt/IDE1/public (/mnt/IDE1/public)
Sep 25 15:17:56 mod_delay/0.5: warning: unable to open DelayTable
'/var/run/proftpd/proftpd.delay': No such file or directory
Sep 25 15:17:56 FTP session opened.
Sep 25 15:17:56 no such user 'xxxxxxxxx'
Sep 25 15:17:56 USER xxxxxxxxx: no such user found from 192.168.1.34
[192.168.1.34] to 192.168.1.32:21
Sep 25 15:17:56 FTP session closed.
Sep 25 15:18:08 mod_delay/0.5: warning: unable to open DelayTable
'/var/run/proftpd/proftpd.delay': No such file or directory
Sep 25 15:18:08 error opening scoreboard: bad/corrupted file
Sep 25 15:18:08 notice: unable to add scoreboard entry: Invalid argument
Sep 25 15:18:08 error rewinding scoreboard: Invalid argument
Sep 25 15:18:08 FTP session opened.
Sep 25 15:18:09 USER xxxxxxxx: Login successful.
Sep 25 13:18:09 Preparing to chroot to directory '/mnt'
Sep 25 13:18:09 error rewinding scoreboard: Invalid argument
Sep 25 13:18:48 recvfile_flag=on
Sep 25 13:18:48 data.c: total=299624
Sep 25 13:18:48 recvfile write data 299624
Sep 25 13:18:48 recvfile_flag=on
Sep 25 13:18:49 data.c: total=4118528
Sep 25 13:18:49 recvfile write data 4118528
Sep 25 13:18:49 recvfile_flag=on
Sep 25 13:18:51 data.c: total=9095522
Sep 25 13:18:51 recvfile write data 9095522
Sep 25 13:18:51 recvfile_flag=on
Sep 25 13:18:54 data.c: total=8584909
Sep 25 13:18:54 recvfile write data 8584909
Sep 25 13:18:54 recvfile_flag=on
Sep 25 13:18:54 data.c: total=50175
Sep 25 13:18:54 recvfile write data 50175
Sep 25 13:18:54 recvfile_flag=on
Sep 25 13:18:54 data.c: total=65588
Sep 25 13:18:54 recvfile write data 65588
Sep 25 13:18:54 recvfile_flag=on
Sep 25 13:18:55 data.c: total=3710214
Sep 25 13:18:55 recvfile write data 3710214
Sep 25 13:18:55 recvfile_flag=on
Sep 25 13:18:55 data.c: total=309314
Sep 25 13:18:55 recvfile write data 309314
Sep 25 13:18:55 recvfile_flag=on
Sep 25 13:18:56 data.c: total=3373735
Sep 25 13:18:56 recvfile write data 3373735
Sep 25 13:18:56 recvfile_flag=on
Sep 25 13:18:56 data.c: total=309154
Sep 25 13:18:56 recvfile write data 309154
Sep 25 13:18:56 recvfile_flag=on
Sep 25 13:18:57 data.c: total=1133967
Sep 25 13:18:57 recvfile write data 1133967
Sep 25 13:18:57 recvfile_flag=on
Sep 25 13:18:57 data.c: total=885079
Sep 25 13:18:57 recvfile write data 885079
Sep 25 13:18:57 recvfile_flag=on
Sep 25 13:18:57 data.c: total=179200
Sep 25 13:18:57 recvfile write data 179200
Sep 25 13:18:57 recvfile_flag=on
Sep 25 13:18:58 data.c: total=1281469
Sep 25 13:18:58 recvfile write data 1281469
Sep 25 13:18:58 recvfile_flag=on
Sep 25 13:18:58 data.c: total=1195864
Sep 25 13:18:58 recvfile write data 1195864
Sep 25 13:18:58 recvfile_flag=on
Sep 25 13:18:58 data.c: total=3569
Sep 25 13:18:58 recvfile write data 3569
Sep 25 13:18:58 recvfile_flag=on
Sep 25 13:18:59 data.c: total=3521934
Sep 25 13:18:59 recvfile write data 3521934
Sep 25 13:18:59 recvfile_flag=on
Sep 25 13:19:00 data.c: total=1268519
Sep 25 13:19:00 recvfile write data 1268519
Sep 25 13:19:00 recvfile_flag=on
Sep 25 13:19:00 data.c: total=1700
Sep 25 13:19:00 recvfile write data 1700
Sep 25 13:19:00 recvfile_flag=on
Sep 25 13:19:00 data.c: total=778
Sep 25 13:19:00 recvfile write data 778
Sep 25 13:19:00 recvfile_flag=on
Sep 25 13:19:00 data.c: total=40448
Sep 25 13:19:00 recvfile write data 40448
Sep 25 13:19:00 recvfile_flag=on
Sep 25 13:19:01 data.c: total=4193280
Sep 25 13:19:01 recvfile write data 4193280
Sep 25 13:19:01 recvfile_flag=on
Sep 25 13:21:38 data.c: total=562044991
Sep 25 13:21:38 recvfile write data 562044991
Sep 25 13:21:38 recvfile_flag=on
Sep 25 13:21:38 data.c: total=3095
Sep 25 13:21:38 recvfile write data 3095
Sep 25 13:21:38 recvfile_flag=on
Sep 25 15:25:16 mod_delay/0.5: warning: unable to open DelayTable
'/var/run/proftpd/proftpd.delay': No such file or directory
Sep 25 15:25:16 error opening scoreboard: bad/corrupted file
Sep 25 15:25:16 notice: unable to add scoreboard entry: Invalid argument
Sep 25 15:25:16 error rewinding scoreboard: Invalid argument
Sep 25 15:25:16 FTP session opened.
Sep 25 15:25:16 USER xxxxxx: Login successful.
Sep 25 13:25:16 Preparing to chroot to directory '/mnt'
Sep 25 13:25:16 error rewinding scoreboard: Invalid argument
Sep 25 15:27:46 mod_delay/0.5: warning: unable to open DelayTable
'/var/run/proftpd/proftpd.delay': No such file or directory
Sep 25 15:27:46 error opening scoreboard: bad/corrupted file
Sep 25 15:27:46 notice: unable to add scoreboard entry: Invalid argument
Sep 25 15:27:46 error rewinding scoreboard: Invalid argument
Sep 25 15:27:46 FTP session opened.
Sep 25 15:27:46 USER xxxxxxxxxx: Login successful.
Sep 25 13:27:46 Preparing to chroot to directory '/mnt'
Sep 25 13:27:46 error rewinding scoreboard: Invalid argument
Sep 25 15:28:29 mod_delay/0.5: warning: unable to open DelayTable
'/var/run/proftpd/proftpd.delay': No such file or directory
Sep 25 15:28:29 error opening scoreboard: bad/corrupted file
Sep 25 15:28:29 notice: unable to add scoreboard entry: Invalid argument
Sep 25 15:28:29 error rewinding scoreboard: Invalid argument
Sep 25 15:28:29 FTP session opened.
Sep 25 15:28:29 USER xxxxxxx: Login successful.
Sep 25 13:28:29 Preparing to chroot to directory '/mnt'
Sep 25 13:28:29 error rewinding scoreboard: Invalid argument
Sep 25 15:30:16 mod_delay/0.5: warning: unable to open DelayTable
'/var/run/proftpd/proftpd.delay': No such file or directory
Sep 25 15:30:16 error opening scoreboard: bad/corrupted file
Sep 25 15:30:16 notice: unable to add scoreboard entry: Invalid argument
Sep 25 15:30:16 error rewinding scoreboard: Invalid argument
Sep 25 15:30:16 FTP session opened.
Sep 25 15:30:16 USER xxxxx: Login successful.
Sep 25 13:30:16 Preparing to chroot to directory '/mnt'
Sep 25 13:30:16 error rewinding scoreboard: Invalid argument


2007/9/27, flipstar@xxxxxxx <flipstar@xxxxxxx>:
> What does /var/log/message say???
>
> Or login via ssh and run
>
> cat /proc/kmsg
>
> then start you file transfer
>
> --
> flip
>
> Codebotcher schrieb:
> > Hi Nils,
> >
> > I had similar issues with my first NAS-2000. Whenever I uploaded a
> > bigger amount of data, the NAS hang up and I were not able to access it
> > any longer. Even ssh did not respond. The only way out of this was to
> > reset the NAS by switching it off and on again.
> >
> > I couldn't say that there was a "critical data mass" that caused this
> > problem. It just happened from time to time and I were not able to
> > reproduce the effect with the same file for a second time.
> >
> > Beside that, the effect was independent from the transfer protocol I
> > used. It happened with samba, ftp, as well as nfs. I tried several
> > different firmware versions but all of them froze at a certain point.
> >
> > Further investigation showed that this problem did occur more often when
> > the fan was completely switched-off and only occasionally with the fan
> > running in position "high". That led me to the suspicion that the unit
> > was suffering from a thermal problem. I reported this issue to the
> > technical service of Raidsonic and asked for advise but never got an
> > answer. I have to admit that I'm quite disappointed about this fact... :-(
> >
> > After this I contacted the mail-order shop where I bought the unit from
> > and they asked me to send it back for further investigations. I got a
> > replacement unit within the week which works fine for me now and without
> > any trouble!
> >
> > One thing that I have noticed is that the first NAS had a small
> > aluminium heat-sink glued on top of the CPU. The replacement that I have
> > got doesn't have this heat-sink, though. I'm not sure from which
> > revision Raidsonic started installing these little thingies. It might
> > well be possible that the unit I got as a replacement is older than the
> > first one, as it was not brand-new, but a refurbished used one. However
> > it works and I'm quite satisfied.
> >
> > Maybe your unit has a similar problem? Can you run it open with the fan
> > running in "high" position and maybe the top cover taken off?
> >
> >
> > Cheers,
> >
> > Stefan
> >
> >
> > Nils Potthoff schrieb:
> > [..]
> >
> >> Nils
> >>
> >> PS: I often have problems to upload greater amount of data per samba. While
> >> the transfer it hangs and finaly the transmission as aborted. Has anyone
> >> ideas why?
> >
> >
>
>

Other related posts: