BUILD FreeNAS on Readynas Pro 6

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
Wow - that couldn't have been an easier install. Writing this all down to keep track of it for the next one.

Got a VGA header cable (so I could mod the BIOS boot screen and fan settings) from here (note to self: the red stripe cable should go on the bottom of the chassis as shown):
http://www.pccables.com/VGA_PORT_HD15F_PORT_To_IDC16.htm
IMG_20141109_195929.jpg


I got one of these to install the OS on (this allows me to keep the internal ReadyNas OS USB drive in tact, just in case):
View: http://www.amazon.com/gp/product/B00812F7O8/ref=oh_aui_detailpage_o06_s00?ie=UTF8&psc=1


I followed the RAM upgrade (8GB) and BIOS guidance from here:
http://www.readynas.com/forum/viewtopic.php?t=74678#p415297
http://www2.warwick.ac.uk/fac/sci/csc/people/computingstaff/jaroslaw_zachwieja/readynaspro-jailfix/

My fan control settings:
IMG_20141109_200530.jpg



Some info on configuring the LCD screen (haven't ventured into these waters yet):
http://www.nexentastor.org/boards/9/topics/8238#message-8241
 

Aaron Ryan

Dabbler
Joined
Mar 20, 2015
Messages
20
I got a ReadyNAS Pro 6 too and was thinking of doing the same thing. Thanks for the post. Have you had any issues since your initial install?

Thanks,
-Aaron
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
The only issue I've had was the nic freezing up under heavy network load. I found a sysctl setting which fixed it. I'm not at the machine right now to find the exact setting though.
 

leoj3n

Dabbler
Joined
Jan 10, 2014
Messages
18
The only issue I've had was the nic freezing up under heavy network load. I found a sysctl setting which fixed it. I'm not at the machine right now to find the exact setting though.

The following seems to delay, but not eliminate, msk watchdog errors on my RNP6 (with 8GB ram and breakout cable) when using it as Replication Target and initiating a Replication Task to it from my more stable desktop FreeNAS machine:

System > Advanced

Enable autotune: ✓​

System > Tunables

Type "loader":
hw.pci.enable_msi = 0
hw.pci.enable_msix = 0

Type "sysctl":
net.inet.tcp.tso = 0​

I wonder if this msk0: watchdog timeout patch can help in regards to these Marvell Yukon 88E8053 Gigabit Ethernet cards on FreeNAS? I'm just not sure how to apply it, if I should bring attention to it via a ticket, or if it will be inlcuded in for example FreeNAS 10.

Watchdog timeouts begin, and the transfer fails because the server drops off the network, after transferring around 70GiB of data. Are the other tunables you think I should try? The sysctl command reports sysctl: unknown oid 'hw.msk'... So I'm guessing that was a setting available in a previous version that has since been removed? It's curious that it no longer exists despite being recommended various places, including the original Freenas on Readynas Pro post, and that various other triggers exist:

# sysctl hw | grep msi
hw.aac.enable_msi: 1
hw.bce.msi_enable: 1
hw.cxgb.msi_allowed: 2
hw.em.enable_msix: 1
hw.igb.enable_msix: 1
hw.ix.enable_msix: 1
hw.ixl.enable_msix: 1
hw.mfi.msi: 1
hw.pci.honor_msi_blacklist: 1
hw.pci.enable_msix: 0
hw.pci.enable_msi: 0​

I'm running on the FreeNAS-9.3-STABLE "train" with all updates installed on both machines. Maybe I will try the 9.3 and 10 nightlies on the RNP6 to see if that makes a difference. Are you still running "RELEASE"? Would that make a difference? The only reference to "msk" in the FreeNAS repo seems to be in some config files. Here is my RNP6 BIOS info, for reference:

Vendor: American Megatrends Inc.
Version: 080014
Release Date: 07/26/2010
BIOS Revision: 8.14​

And the Marvell Yukon NIC:

# ifconfig msk0
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c011a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,VLAN_HWTSO,LINKSTATE>
ether 00:1f:33:ea:f9:5b
inet 10.0.1.210 netmask 0xffffff00 broadcast 10.0.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active​

I hope I can get this figured out so as to have a secure backup of my data. So close yet no cigar.
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
I've been running with these 2 tunables and it's been stable for a long time.
upload_2016-1-3_12-15-38.png
 

leoj3n

Dabbler
Joined
Jan 10, 2014
Messages
18
I've been running with these 2 tunables and it's been stable for a long time.
View attachment 9820

Are you running the latest updated STABLE train:

FreeNAS-9.3-STABLE-201512121950


And what does sysctl report when you query it on shell like:

sysctl hw.msk.msi_disable


Have you tried writing a large amount of data (100+GiB) to a dataset across the network to your RNP6? What protocol if so? Any replication target tasks?

For me sysctl is reporting "unkown oid", and I did have hw.msk.msi_disable and vfs.zfs.prefetch_disable set in previous trials without success.

The RNP6 seems to operate flawlessly otherwise, until it's under heavy write load over the network. I believe the replication task is purely over SSH, and that is the only service enabled on both machines.

Edit:

I'd also be interested to see the output of this command on your machine:

dmidecode -t bios -q
 
Last edited:

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
This is my replication target (yep over ssh), so I've written 10's of TB to it without issue. I don't use it for anything else (no other services).

I think I started on 9.2, so maybe it used to be a valid sysctl then. Like you, I'm also getting unknown oid on the sysctl hw.msk.msi_disable now.

Code:
[root@freenas2] ~# sysctl vfs.zfs.prefetch_disable 
vfs.zfs.prefetch_disable: 0
[root@freenas2] ~# sysctl hw.msk.msi_disable
sysctl: unknown oid 'hw.msk.msi_disable'
[root@freenas2] ~# 


Code:
[root@freenas2] ~# dmidecode -t bios -q
BIOS Information
        Vendor: American Megatrends Inc.
        Version: 080014
        Release Date: 07/26/2010
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 1024 kB
        Characteristics:
                ISA is supported
                PCI is supported
                PNP is supported
                APM is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                ESCD support is available
                Boot from CD is supported
                Selectable boot is supported
                BIOS ROM is socketed
                EDD is supported
                5.25"/1.2 MB floppy services are supported (int 13h)
                3.5"/720 kB floppy services are supported (int 13h)
                3.5"/2.88 MB floppy services are supported (int 13h)
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Serial services are supported (int 14h)
                Printer services are supported (int 17h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                LS-120 boot is supported
                ATAPI Zip drive boot is supported
                BIOS boot specification is supported
        BIOS Revision: 8.14

BIOS Language Information
        Language Description Format: Abbreviated
        Installable Languages: 1
                en|US|iso8859-1
        Currently Installed Language: en|US|iso8859-1

[root@freenas2] ~# 
 

leoj3n

Dabbler
Joined
Jan 10, 2014
Messages
18
400GiB transferred and I'm convinced those settings finally made a difference. Perhaps it took some combination but now I'm just glad it's working. Thank you.
 
Last edited:

jblakeney

Dabbler
Joined
May 6, 2015
Messages
10
Depasseg,
Would you mind posting your memory part # and cpu? I have a 6 Pro now and would really like to put FreeNAS on it but I have seen nothing of support for ECC memory. Mine has an E5300 processor. It also is constantly warning "DDB18 power is out of normal range." Did you ever see that message before the migration?
Thanks,
Jimmy
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
I'm pretty sure all the Pro 6's use ECC RAM. I also have the E5300. I upgraded my RAM years ago (pre-freenas) to 8GB. I haven't seen that error, but it sounds like bad power. Either a failing PSU or a bad UPS. If you are on an UPS, try running without it and see if that helps.

Code:
[root@freenas2] ~# dmidecode
# dmidecode 2.12
SMBIOS 2.4 present.
27 structures occupying 1435 bytes.
Table at 0x000FCBF0.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: American Megatrends Inc.
        Version: 080014
        Release Date: 07/26/2010
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 1024 kB
        Characteristics:
                ISA is supported
                PCI is supported
                PNP is supported
                APM is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                ESCD support is available
                Boot from CD is supported
                Selectable boot is supported
                BIOS ROM is socketed
                EDD is supported
                5.25"/1.2 MB floppy services are supported (int 13h)
                3.5"/720 kB floppy services are supported (int 13h)
                3.5"/2.88 MB floppy services are supported (int 13h)
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Serial services are supported (int 14h)
                Printer services are supported (int 17h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                LS-120 boot is supported
                ATAPI Zip drive boot is supported
                BIOS boot specification is supported
        BIOS Revision: 8.14

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: To Be Filled By O.E.M.
        Product Name: To Be Filled By O.E.M.
        Version: 07/26/2010 FLAME6-MB V2.0
        Serial Number: To Be Filled By O.E.M.
        UUID: 00020003-0004-0005-0006-000700080009
        Wake-up Type: Power Switch
        SKU Number: To Be Filled By O.E.M.
        Family: To Be Filled By O.E.M.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: To be filled by O.E.M.
        Product Name: To be filled by O.E.M.
        Version: To be filled by O.E.M.
        Serial Number: To be filled by O.E.M.
        Asset Tag: To Be Filled By O.E.M.
        Features:
                Board is a hosting board
                Board is replaceable
        Location In Chassis: To Be Filled By O.E.M.
        Chassis Handle: 0x0003
        Type: Motherboard
        Contained Object Handles: 0

Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
        Manufacturer: To Be Filled By O.E.M.
        Type: Desktop
        Lock: Not Present
        Version: To Be Filled By O.E.M.
        Serial Number: To Be Filled By O.E.M.
        Asset Tag: To Be Filled By O.E.M.
        Boot-up State: Safe
        Power Supply State: Safe
        Thermal State: Safe
        Security Status: None
        OEM Information: 0x00000000
        Height: Unspecified
        Number Of Power Cords: 1
        Contained Elements: 0

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
        Socket Designation: CPU 1
        Type: Central Processor
        Family: Quad-Core Xeon 5300
        Manufacturer: Intel           
        ID: 7A 06 01 00 FF FB EB BF
        Signature: Type 0, Family 6, Model 23, Stepping 10
        Flags:
                FPU (Floating-point unit on-chip)
                VME (Virtual mode extension)
                DE (Debugging extension)
                PSE (Page size extension)
                TSC (Time stamp counter)
                MSR (Model specific registers)
                PAE (Physical address extension)
                MCE (Machine check exception)
                CX8 (CMPXCHG8 instruction supported)
                APIC (On-chip APIC hardware supported)
                SEP (Fast system call)
                MTRR (Memory type range registers)
                PGE (Page global enable)
                MCA (Machine check architecture)
                CMOV (Conditional move instruction supported)
                PAT (Page attribute table)
                PSE-36 (36-bit page size extension)
                CLFSH (CLFLUSH instruction supported)
                DS (Debug store)
                ACPI (ACPI supported)
                MMX (MMX technology supported)
                FXSR (FXSAVE and FXSTOR instructions supported)
                SSE (Streaming SIMD extensions)
                SSE2 (Streaming SIMD extensions 2)
                SS (Self-snoop)
                HTT (Multi-threading)
                TM (Thermal monitor supported)
                PBE (Pending break enabled)
        Version: Pentium(R) Dual-Core  CPU      E5300  @ 2.60GHz    
        Voltage: 1.3 V
        External Clock: 200 MHz
        Max Speed: 2600 MHz
        Current Speed: 2600 MHz
        Status: Populated, Enabled
        Upgrade: Socket LGA775
        L1 Cache Handle: 0x0005
        L2 Cache Handle: 0x0006
        L3 Cache Handle: 0x0007
        Serial Number: To Be Filled By O.E.M.
        Asset Tag: To Be Filled By O.E.M.
        Part Number: To Be Filled By O.E.M.

Handle 0x0005, DMI type 7, 19 bytes
Cache Information
        Socket Designation: L1-Cache
        Configuration: Enabled, Not Socketed, Level 1
        Operational Mode: Write Back
        Location: Internal
        Installed Size: 64 kB
        Maximum Size: 64 kB
        Supported SRAM Types:
                Other
        Installed SRAM Type: Other
        Speed: Unknown
        Error Correction Type: Parity
        System Type: Data
        Associativity: 8-way Set-associative

Handle 0x0006, DMI type 7, 19 bytes
Cache Information
        Socket Designation: L2-Cache
        Configuration: Enabled, Not Socketed, Level 2
        Operational Mode: Write Back
        Location: Internal
        Installed Size: 2048 kB
        Maximum Size: 2048 kB
        Supported SRAM Types:
                Other
        Installed SRAM Type: Other
        Speed: Unknown
        Error Correction Type: Single-bit ECC
        System Type: Unified
        Associativity: 8-way Set-associative

Handle 0x0007, DMI type 7, 19 bytes
Cache Information
        Socket Designation: L3-Cache
        Configuration: Disabled, Not Socketed, Level 3
        Operational Mode: Unknown
        Location: Internal
        Installed Size: 0 kB
        Maximum Size: 0 kB
        Supported SRAM Types:
                Unknown
        Installed SRAM Type: Unknown
        Speed: Unknown
        Error Correction Type: Unknown
        System Type: Unknown
        Associativity: Unknown

Handle 0x0008, DMI type 5, 24 bytes
Memory Controller Information
        Error Detecting Method: 64-bit ECC
        Error Correcting Capabilities:
                None
        Supported Interleave: One-way Interleave
        Current Interleave: One-way Interleave
        Maximum Memory Module Size: 4096 MB
        Maximum Total Memory Size: 16384 MB
        Supported Speeds:
                Other
        Supported Memory Types:
                DIMM
                SDRAM
        Memory Module Voltage: 3.3 V
        Associated Memory Slots: 4
                0x0009
                0x000A
                0x000B
                0x000C
        Enabled Error Correcting Capabilities:
                None

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: DIMM0
        Bank Connections: 0 1
        Current Speed: Unknown
        Type: DIMM SDRAM
        Installed Size: 4096 MB (Double-bank Connection)
        Enabled Size: 4096 MB (Double-bank Connection)
        Error Status: OK

Handle 0x000A, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: DIMM1
        Bank Connections: 2 3
        Current Speed: Unknown
        Type: DIMM SDRAM
        Installed Size: Not Installed
        Enabled Size: Not Installed
        Error Status: OK

Handle 0x000B, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: DIMM2
        Bank Connections: 4 5
        Current Speed: Unknown
        Type: DIMM SDRAM
        Installed Size: 4096 MB (Double-bank Connection)
        Enabled Size: 4096 MB (Double-bank Connection)
        Error Status: OK

Handle 0x000C, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: DIMM3
        Bank Connections: 6 7
        Current Speed: Unknown
        Type: DIMM SDRAM
        Installed Size: Not Installed
        Enabled Size: Not Installed
        Error Status: OK

Handle 0x000D, DMI type 13, 22 bytes
BIOS Language Information
        Language Description Format: Abbreviated
        Installable Languages: 1
                en|US|iso8859-1
        Currently Installed Language: en|US|iso8859-1

Handle 0x000E, DMI type 15, 35 bytes
System Event Log
        Area Length: 4 bytes
        Header Start Offset: 0x0000
        Header Length: 2 bytes
        Data Start Offset: 0x0002
        Access Method: Indexed I/O, one 16-bit index port, one 8-bit data port
        Access Address: Index 0x046A, Data 0x046C
        Status: Invalid, Not Full
        Change Token: 0x00000000
        Header Format: No Header
        Supported Log Type Descriptors: 6
        Descriptor 1: End of log
        Data Format 1: OEM-specific
        Descriptor 2: End of log
        Data Format 2: OEM-specific
        Descriptor 3: End of log
        Data Format 3: OEM-specific
        Descriptor 4: End of log
        Data Format 4: OEM-specific
        Descriptor 5: End of log
        Data Format 5: OEM-specific
        Descriptor 6: End of log
        Data Format 6: OEM-specific

Handle 0x000F, DMI type 16, 15 bytes
Physical Memory Array
        Location: System Board Or Motherboard
        Use: System Memory
        Error Correction Type: None
        Maximum Capacity: 4 GB
        Error Information Handle: Not Provided
        Number Of Devices: 4

Handle 0x0010, DMI type 19, 15 bytes
Memory Array Mapped Address
        Starting Address: 0x00000000000
        Ending Address: 0x001FFFFFFFF
        Range Size: 8 GB
        Physical Array Handle: 0x000F
        Partition Width: 4

Handle 0x0011, DMI type 17, 27 bytes
Memory Device
        Array Handle: 0x000F
        Error Information Handle: Not Provided
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 4096 MB
        Form Factor: DIMM
        Set: None
        Locator: DIMM0
        Bank Locator: BANK0
        Type: SDRAM
        Type Detail: Synchronous
        Speed: Unknown
        Manufacturer: Manufacturer0
        Serial Number: SerNum0
        Asset Tag: AssetTagNum0
        Part Number: PartNum0

Handle 0x0012, DMI type 20, 19 bytes
Memory Device Mapped Address
        Starting Address: 0x00000000000
        Ending Address: 0x000FFFFFFFF
        Range Size: 4 GB
        Physical Device Handle: 0x0011
        Memory Array Mapped Address Handle: 0x0010
        Partition Row Position: 1
        Interleaved Data Depth: 1

Handle 0x0013, DMI type 17, 27 bytes
Memory Device
        Array Handle: 0x000F
        Error Information Handle: Not Provided
        Total Width: Unknown
        Data Width: Unknown
        Size: No Module Installed
        Form Factor: DIMM
        Set: None
        Locator: DIMM1
        Bank Locator: BANK1
        Type: Unknown
        Type Detail: Unknown
        Speed: Unknown
        Manufacturer: Manufacturer1
        Serial Number: SerNum1
        Asset Tag: AssetTagNum1
        Part Number: PartNum1

Handle 0x0014, DMI type 20, 19 bytes
Memory Device Mapped Address
        Starting Address: 0x00000000000
        Ending Address: 0x000000003FF
        Range Size: 1 kB
        Physical Device Handle: 0x0013
        Memory Array Mapped Address Handle: 0x0010
        Partition Row Position: 1
        Interleaved Data Depth: 1

Handle 0x0015, DMI type 17, 27 bytes
Memory Device
        Array Handle: 0x000F
        Error Information Handle: Not Provided
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 4096 MB
        Form Factor: DIMM
        Set: None
        Locator: DIMM2
        Bank Locator: BANK2
        Type: SDRAM
        Type Detail: Synchronous
        Speed: Unknown
        Manufacturer: Manufacturer2
        Serial Number: SerNum2
        Asset Tag: AssetTagNum2
        Part Number: PartNum2

Handle 0x0016, DMI type 20, 19 bytes
Memory Device Mapped Address
        Starting Address: 0x00100000000
        Ending Address: 0x001FFFFFFFF
        Range Size: 4 GB
        Physical Device Handle: 0x0015
        Memory Array Mapped Address Handle: 0x0010
        Partition Row Position: 1
        Interleaved Data Depth: 1

Handle 0x0017, DMI type 17, 27 bytes
Memory Device
        Array Handle: 0x000F
        Error Information Handle: Not Provided
        Total Width: Unknown
        Data Width: Unknown
        Size: No Module Installed
        Form Factor: DIMM
        Set: None
        Locator: DIMM3
        Bank Locator: BANK3
        Type: Unknown
        Type Detail: Unknown
        Speed: Unknown
        Manufacturer: Manufacturer3
        Serial Number: SerNum3
        Asset Tag: AssetTagNum3
        Part Number: PartNum3

Handle 0x0018, DMI type 20, 19 bytes
Memory Device Mapped Address
        Starting Address: 0x00000000000
        Ending Address: 0x000000003FF
        Range Size: 1 kB
        Physical Device Handle: 0x0017
        Memory Array Mapped Address Handle: 0x0010
        Partition Row Position: 1
        Interleaved Data Depth: 1

Handle 0x0019, DMI type 32, 20 bytes
System Boot Information
        Status: No errors detected

Handle 0x001A, DMI type 127, 4 bytes
End Of Table

[root@freenas2] ~# 
 

jblakeney

Dabbler
Joined
May 6, 2015
Messages
10
Depasseg,
Thank you for the reply. Based upon what I see and compared to my 3 FreeNAS system, I would say that ECC is not supported or you don't have ECC memory in the ReadyNAS.

Your ReadyNAS lists:
  1. Handle 0x0008, DMI type 5, 24 bytes
  2. Memory Controller Information
  3. Error Detecting Method: 64-bit ECC
  4. Error Correcting Capabilities:
  5. None
  6. .......
  7. Enabled Error Correcting Capabilities:
  8. None
Two of mine (Intel) list: Error Correction Type: Multi-bit ECC
One (AMD): Error Correction Type: Single-bit ECC

Also each memory module on the ReadyNAS:
  1. Handle 0x0011, DMI type 17, 27 bytes
  2. Memory Device
  3. .......
  4. Total Width: 64 bits
  5. Data Width: 64 bits
  6. Size: 4096 MB
All of my systems show the Total Width: 72 bits and Data Width: 64 bits.


I would really like to use the ReadyNAS as a backup to my systems but I am concerned about the data becoming corrupted.

Thanks for all the help,
Jimmy
 

jblakeney

Dabbler
Joined
May 6, 2015
Messages
10
Depasseg,
Were you able to get a model number for the ram in your pro 6? I did not see anything in the dmidecode that would point me to the proper modules. I have read that the pro6 can be temperamental.
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
It's funny you should ask. So since someone pointed out i might not be running ECC memory, I've been looking around, and just bought some. The sticks are scheduled to arrive today. I'll let you know the model number if they work. :)

UPDATE: Package arrived, but didn't work (it's registered RAM, which was a long shot). I can't find anything else. I think I need 2x4GB ECC Unbuffered DDR2-800 (6400), but I can't find that anywhere.
 
Last edited:

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
I'm looking for a replacement system that has ECC. Thanks a lot!

Anyone want to buy a couple 6 disk ReadyNAS pro enclosures?
 

AidanPryde

Cadet
Joined
Jan 17, 2019
Messages
1
HI depasseg
could you please elt me know how and where you installed the FreeNAS software on?
Did you use an external drive or one internal one to host FreeNAS on the ReadyNAS device.

regards
Aidan
 

jblakeney

Dabbler
Joined
May 6, 2015
Messages
10
Aidan,
I used 2 USB flash drives in a mirror configuration. You can use the two on the back or get an adapter for the onboard USB header pins and leave the two on the back free.
 

tony359

Cadet
Joined
Apr 5, 2023
Messages
3
Digging out this old thread. With Netgear doing very little development on their NAS, I was considering migrating to TrueNAS.

My Pro6 is on OS6 and has a Core2 6600 and can be upgraded to 8GB of RAM. Last post here is from 2019 so I was wondering if there has been any changes since then and if there is anybody running TrueNAS on a Pro6 - or a similar x86 ReadyNAS.

If I understand correctly, the NAS has 128MB flash storage somewhere which acts as a bootloader. Looking at the first post it seems that the boot drive can be changed in the BIOS (I am making the VGA adaptor) and TrueNAS has to be installed on a USB stick which can be installed at the back of the unit or inside the NAS on one of the USB header (with an adaptor).

What happens then, will TRUEnas see the hardware and the drives with no further actions on my end?

Thanks to anybody who can help on this :)
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
Not a great solution, I'm afraid. The minimum requirements were bumped up to 16 GB of RAM fairly recently and Core 2s are rather ancient at this point.
Will it boot? Probably. Will the experience be a good one? I doubt it.
 

tony359

Cadet
Joined
Apr 5, 2023
Messages
3
Thank you!
16GB for a NAS seems quite a lot to be honest, particularly for a Linux system! I don't do much with my NAS, it's really just single user and just storage, no transcoding, no crazy access. My whole video library is there and I stream - with no transcoding - so it could be 30-40Mbit/s maximum on a single file.

Would you say that 16GB is just a "to have all the features" requirement?

The specs I found have this line in it


The TrueNAS installer recommends 8 GB of RAM. TrueNAS installs, runs, operates jails, hosts SMB shares, and replicates TBs of data with less. iXsystems recommends the above for better performance and fewer issues.
I don't mean to question you - I know nothing about TrueNAS - but if feels more of a "to be on the safe side". Still, 16GB feels excessive for a NAS OS, even in 2023.

Anyways, it looks like I might not want to migrate to a platform which could be "unsupported" soon if it recommends 16GB of RAM. I appreciate my NAS is a bit old but for I feel I don't have such high requirements to justify a powerful and modern system.

Food for thought :)
 
Top