OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!

mdgm wrote:
What is the date of the BIOS on your NAS?

Thanks mdgm

6/10/2010.
I have seen another thread with a bin file to update the bios via an add on. Is this applicable to my version?
Also if that is the correct update can I run it from os 6 or do I need to try to revert to 4, update the bios then reinstall 6.

Thanks

That is the latest BIOS for your NAS: http://www.readynas.com/forum/viewtopic.php?p=387035#p387035

So no point trying to update it. I could provide instructions again for updating the BIOS on OS 6 (or link to another post) but there is no point in this case.

Thanks. I guess with the ultra 6 bios fan control is not an option.
I think on balance the best solution for me is to change the fan to one with built in thermistor control. I am unsure what numbers in the dashboard system status tab will be reliable to monitor temps but I figure if I pick a high enough performance fan even running quietly it should move more air than the factory crown fan.
I will let you know how I get on.

I have readyNAS 2100v2 and managed to install OS 6.0.8. First thanks to the forum who helped me in installing and making the readynas to run on the latest OS :)

I have managed to make Fan Control to work as well for ReadyNAS 2100v2.
/etc/fancontrol details:

# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/it87.2576
DEVNAME=hwmon0=coretemp hwmon1=it8721
FCTEMPS=hwmon1/device/pwm3=hwmon0/device/temp2_input hwmon1/device/pwm2=hwmon0/device/temp2_input  hwmon1/device/pwm1=hwmon0/device/temp2_input
FCFANS=hwmon1/device/pwm3=hwmon1/device/fan2_input hwmon1/device/pwm2=hwmon1/device/fan1_input  hwmon1/device/pwm1=
MINTEMP=hwmon1/device/pwm3=51 hwmon1/device/pwm2=51  hwmon1/device/pwm1=51
MAXTEMP=hwmon1/device/pwm3=58 hwmon1/device/pwm2=58  hwmon1/device/pwm1=75
MINSTART=hwmon1/device/pwm3=40 hwmon1/device/pwm2=40  hwmon1/device/pwm1=150
MINSTOP=hwmon1/device/pwm3=40 hwmon1/device/pwm2=40  hwmon1/device/pwm1=0
MINPWM=hwmon1/device/pwm3=40 hwmon1/device/pwm2=40
MAXPWM=hwmon1/device/pwm3=255 hwmon1/device/pwm2=255

I have also managed with the temperature monitoring using this forum help:
crontab entry
*/1 * * * * root /data/Tims/UpdateTemp

UpdateTemp file contents:

#!/bin/sh
#######################################################
Coretemp="/sys/devices/platform/coretemp.0/temp2_input"
Systemp="/sys/devices/platform/it87.2576/temp2_input"
Coretemp2="/sys/devices/platform/coretemp.0/temp3_input"
Ct=`cat $Coretemp`
C=`expr $Ct / 1000`
Ct2=`cat $Coretemp2`
C2=`expr $Ct2 / 1000`
St=`cat $Systemp`
S=`expr $St / 1000`
rrdtool update /run/readynasd/stats/temperature_int_deg.rrd N:$C:$S

NOW I am struggling with the Volume entries listing correctly under System->Volumes.
I have four HDD, two 2TB HDD and two 1TB HDD, but the display only shows first two disk i.e. two 2TB HDD, other two 1TB HDD is not shown in the UI.
my mtstat.log details:

Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] 
md126 : active raid1 sdb4[1] sda4[0]
      976622784 blocks super 1.2 [2/2] [UU]
      
md127 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
      2915731968 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
      
md1 : active raid6 sdd2[3] sdc2[2] sdb2[1] sda2[0]
      1047936 blocks super 1.2 level 6, 64k chunk, algorithm 2 [4/4] [UUUU]
      
md0 : active raid1 sdd1[3] sdc1[2] sdb1[1] sda1[0]
      4192192 blocks super 1.2 [4/4] [UUUU]
      
unused devices: <none>
/dev/md/1af8fae2:0:
        Version : 1.2
  Creation Time : Wed Jul 10 21:57:24 2013
     Raid Level : raid1
     Array Size : 4192192 (4.00 GiB 4.29 GB)
  Used Dev Size : 4192192 (4.00 GiB 4.29 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Thu Jul 11 11:28:50 2013
          State : active 
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

           Name : 1af8fae2:0  (local to host 1af8fae2)
           UUID : cc72b189:34201546:4b959aa3:a412bb35
         Events : 20

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1
       2       8       33        2      active sync   /dev/sdc1
       3       8       49        3      active sync   /dev/sdd1
/dev/md/1af8fae2:1:
        Version : 1.2
  Creation Time : Wed Jul 10 21:57:24 2013
     Raid Level : raid6
     Array Size : 1047936 (1023.55 MiB 1073.09 MB)
  Used Dev Size : 523968 (511.77 MiB 536.54 MB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Wed Jul 10 21:59:02 2013
          State : active 
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           Name : 1af8fae2:1  (local to host 1af8fae2)
           UUID : dcdbeca8:0ead7586:185bb8b7:a2eee11c
         Events : 18

    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2
       2       8       34        2      active sync   /dev/sdc2
       3       8       50        3      active sync   /dev/sdd2
/dev/md/data-0:
        Version : 1.2
  Creation Time : Wed Jul 10 21:57:25 2013
     Raid Level : raid5
     Array Size : 2915731968 (2780.66 GiB 2985.71 GB)
  Used Dev Size : 971910656 (926.89 GiB 995.24 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Thu Jul 11 11:28:31 2013
          State : clean 
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           Name : 1af8fae2:data-0  (local to host 1af8fae2)
           UUID : 1dcbc9aa:810af4f8:815edb55:48c86376
         Events : 22

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       1       8       19        1      active sync   /dev/sdb3
       2       8       35        2      active sync   /dev/sdc3
       3       8       51        3      active sync   /dev/sdd3
/dev/md/data-1:
        Version : 1.2
  Creation Time : Thu Jul 11 03:57:33 2013
     Raid Level : raid1
     Array Size : 976622784 (931.38 GiB 1000.06 GB)
  Used Dev Size : 976622784 (931.38 GiB 1000.06 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Thu Jul 11 11:28:01 2013
          State : clean 
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           Name : 1af8fae2:data-1  (local to host 1af8fae2)
           UUID : b664f984:d9820153:aa0e66b0:07df6678
         Events : 19

    Number   Major   Minor   RaidDevice State
       0       8        4        0      active sync   /dev/sda4
       1       8       20        1      active sync   /dev/sdb4
 

Thanks for your kind help.

Hey,

I have a wired problem.... I have a Ultra 4 with OS 6.... Problem is that approx. after half an hour the frontview is not reachable and I get the message, that the Ultra is not connected and it takes time until it connects again. (Seems Ultra loses connection) The thing is that over ssh the ultra is always reachable also when frontview want start.... I have already preformed a reset and also reinstalled os but with no success, error is still there.... Anyone a clue?? (Maybe sonting with the BIO? I have the old one and can't find any file for update that is .deb only the one in bin which was postet and do not work in os 6...) => The alternative with usb stick and exe file (for downgrade on 4.2) which was postet here somewhere is also a problem since I work on a Macbook Air without windo$....

ps: Sorry for my english i´m from austria....

Are you running the latest version of ReadyNAS OS (currently 6.0.8 )?

mdgm wrote:
Are you running the latest version of ReadyNAS OS (currently 6.0.8)?

Yes 6.0.8.....

So for any of you who have not been following along, I've been putting a brand new (excess inventory) ReadyNAS Pro through its paces with a fresh install of OS6 version 6.0.8.

About eight posts ago I ended with a list of eleven steps that I either had done or were planning on doing. The conclusion of that little experiment was simple. . . It turned out to be a BAD HARD DRIVE. Even though all the short/quick diagnostic tests I attempted said that the drive was okay the ReadyNAS knew otherwise. Once I resorted to a FULL Diagnostic / Surface Scan the problems eventually came to light. So I set that Hard Drive aside to send back to Western Digital for warranty replacement.

Fortunately I had a spare hard drive of the same brand and model that I could use in place of the newly discovered BAD drive. So, for the past week I have been pushing and pulling Terabytes and Terabytes worth of data to and from this ReadyNAS Pro using different protocols and methods trying to test every possible scenario before putting OS6 into a production environment. I also experimented with some really crazy drive swapping scenarios that I would NEVER attempt in a production environment. All in all, the vast majority of testing went pretty well, until. . . I get this E-Mail out of the blue from the NAS under test:

"Detected increasing ATA error count: [24636] on disk 5 [WDC WD2002FYPS-02W3B0, WD-WCAVY5956816] 2 times in the past 30 days. This condition often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy."

I'm like "What the Hell?" The distressing thing about the timing of this message is it took place about 20 minutes into a volume expansion experiment that I was performing. You see, all the testing that I was doing previously was with four 2TB Drives (Bays 2,3,4,5 populated. 1 and 6 empty). So I filled the volume with test data to ensure that I would get an alert stating that it was getting full. Once I was satisfied that the volume capacity alerts were working properly, I thought it would be a good time to do a Volume Expansion test. I inserted a fresh drive into Bay 6. Along with the message above I received another that said:

"Disk in channel '5' (Internal) changed state from ONLINE to FAILED."

So I removed the drive from Bay 5 and started a failure diagnosis on it. Here comes the weird part - After doing a FULL diagnostic on the drive with two different tools (to include a full SURFACE SCAN) both diagnostics reported zero errors or problems of any kind. Again I say: What the hell? So I wiped the first and last million sectors of the drive in preparation for reintroduction to the array.

Since performing a full diagnostic on a 2TB drive takes about 5 to 6 hours, the drive that I popped into Bay 6 had finished the integration process. Unfortunately, since the drive that was in Bay 5 failed during a Volume Expansion, the Array as a whole was still considered "Degraded". So, in an attempt to "fool" the ReadyNAS into forgetting about the drive that failed from Bay 5, I shut the unit down and moved the new drive that was in Bay 6 to Bay 5, and powered it back on, waited 15 or 20 minutes and reinserted the alleged "BAD" drive that was originally in Bay 5 into Bay 6. The insertion was detected and this is what I saw on the GUI:



Which leads me to three questions, which are:
1.) Why do you suppose the ReadyNAS thinks that this drive has issues when two different Hard Drive diagnostic programs say otherwise?
2.) Does OS6 have some sort Hard Drive Database that remembers every Hard Drive that has ever been in it?
3.) If number 2 above = YES, is there some way to clear that data so that the ReadyNAS reassess the condition of a particular drive from scratch sometime in the future?

As always. . . Thanks in advance,

1) Have you checked the drive using WD LifeGuard Diagnostics? Have you checked the SMART stats on the disk when it is connected to a PC? An ATA error count of 24638 is huge and does suggest that there is a big problem with the disk.
2) I think that might be the case
3) A factory default (wipes all data, settings, everything) would wipe it. Not sure how else to do so but there probably is a way.

Good Lord you're fast! I wasn't even finished proofreading/editing my last post before you sent a reply. . . :)

Anyway, my answers are:

mdgm wrote:
1) Have you checked the drive using WD LifeGuard Diagnostics? Have you checked the SMART stats on the disk when it is connected to a PC? An ATA error count of 24638 is huge and does suggest that there is a big problem with the disk.

YES! That was the first tool that I used, which is typically the case when I'm diagnosing Western Digital Hard Drives. The primary reason I even sought a "Second Opinion" was because "LifeGuard Diagnostics" reported that the drive had NO ERRORS of any kind. I concur, 24638 ATA errors is huge! Which is why I think the data may be erroneous.

mdgm wrote:
3) A factory default (wipes all data, settings, everything) would wipe it. Not sure how else to do so but there probably is a way.

Well yeah, I figured that much. . . :roll: I was hoping to avoid that primarily for two reasons:
a.) It takes forever (24+ hours) to rebuild the RAID array from scratch, and. . .
b.) I was afraid that doing so might wipe out all the Fan Speed and Temperature Graphing tweaks that I had done. Not being the Linux expert as many of you are, just having to do those two things over again is a couple of hours of work for me :oops: