this is the error I get from the replication task Pool2-Pool3. I would appreciate any help you can provide
I have rebooted. I get this same error every time the replication runs. Is there any information here that can help as to why? Pool3 is not in any samba share. I'll try again to reinitiate the replicationsomething is preventing the umount of /var/db/system/samba4, which is very weird, because you should not be able to replicate that.
have you tried rebooting to see if it clears.....whatever the heck is causing that error?
First switch I bought was a Quanta LB4M, It had 2 SPF+ ports so I could integrate the 10Gb stuff with my 1Gb stuff. It was so loud I could not stand it. Those tiny fans built into the supply were impossible to silence. I built a closet under the stairs in my basement to get it away from me. When I saw the Aruba switch, I sold the Quanta. The Aruba 2500 is very quiet and has 4 SFP+ ports and a nice web interface. 2 of those must be a challenge.Checked out your profile,
Quanta LB6M
Quanta LB4M
naw, I have them racked in another room. I dont use any of the managed features, so a web interface is pointless. they give me wire speeds and basic switching. I haven't found anything to replace them that isn't many hundreds of dollars, much less ports, or also louder2 of those must be a challenge
truenas and USB 3.0 is unreliable at best. there is no support or help for it.Create Backup system (right now to USB 3.0 drives, Need some help with this. The replication task is complete, but I cannot seem to create a SMB share it to check the contents.
you can probably put an expander in a PCIe slot with no CPU. it just needs power and a connection to a SAS, which ought to work with the onboard SAS.That is a bummer but I can add a raid card to connect that. That will burn a slot.
The Aruba 2500 is a lot quieter and is reasonably priced.naw, I have them racked in another room. I dont use any of the managed features, so a web interface is pointless. they give me wire speeds and basic switching. I haven't found anything to replace them that isn't many hundreds of dollars, much less ports, or also louder
truenas and USB 3.0 is unreliable at best. there is no support or help for it.
you can probably put an expander in a PCIe slot with no CPU. it just needs power and a connection to a SAS, which ought to work with the onboard SAS.
RES2SV240, for example, can be powered by a PCIe slot OR a molex right from the PSU. you would be able to run 5 full sets of breakout cables or SFF's to backplanes from it.
USB drives are not great to begin with and USB is particularly unreliable with ZFS so TrueNAS doesn't bother to support it. the hub topology of USB, where devices are obfuscated from the OS by responding in a round-robin like hub-and-spoke topology means that USB drives are NOT available consistently, the way ZFS needs drives to be. ZFS needs to be able to reach all drives in a pool simultaneously, and USB makes this impossible (unless you have each drive on a root USB port and nothing else, which is unlikely)USB than about Truenas support
a port replicator is different, that's for SATA, and they are always crap, built with the cheapest parts and cheapest methods. they basically do to SATA the same thing as USB does - round robin hub-and-spoke sporadic drive availability.port replicator
what, exactly, is your second chassis? can you give the part number, a pic, or the product page? "825-7" is not enough to look it up/My second Chassis
I only planned to use a pool with a single USB 3.0 drive for a backup. the concerns seems to be using an array of USB drives. I think I might be OK. But the ZFS concerns would be eliminated if I attach the USB to a client and backup there. I can also buy a single big internal drive and use that as an offline backup.USB drives are not great to begin with and USB is particularly unreliable with ZFS so TrueNAS doesn't bother to support it. the hub topology of USB, where devices are obfuscated from the OS by responding in a round-robin like hub-and-spoke topology means that USB drives are NOT available consistently, the way ZFS needs drives to be. ZFS needs to be able to reach all drives in a pool simultaneously, and USB makes this impossible (unless you have each drive on a root USB port and nothing else, which is unlikely)
the behaviour of USB drives will have similarities to how SMR mangles things.
Thanks for the explanation. I was nervous about the Expander. I see there is no reason to be.a port replicator is different, that's for SATA, and they are always crap, built with the cheapest parts and cheapest methods. they basically do to SATA the same thing as USB does - round robin hub-and-spoke sporadic drive availability.
a SAS expander is an entirely different beast. any SAS compliant controller will work with a SAS expander. the intel SAS in that board appears to be fully compliant. you can chain SAS expanders up to like 256-1024 or so devices. they are conceptually switches for SAS, giving you network switch like functionality.
Here is my lab descriptionwhat, exactly, is your second chassis? can you give the part number, a pic, or the product page? "825-7" is not enough to look it up/
I am a rookie, I did not expand the spoilers until after I went through looking at a bunch of options, then I saw what you posted. Again, thanks for the education. I did not know these kind of cables existed and how there are used. The bulkheads make things a lot more robust. If I did not already have the raid card, (I have 2, I bought those for a 16 drive earlier setup before I bought the 12 sled chassis with the Expander), the Intel RES25V240 would be very attractive. I will not be expanding beyond this many drives so the extra capability of the Intel expander is not needed. I have 4 extra SATA ports. The 12 Sled chassis is basically a JBOD so I could add 4 SSD drives in that chassis someday, so the double bulkhead is attractive..ahh, so you have 2x 2Us. that makes more sense now. it wasn't making any sense as just 1 2U.
internal SAS cables are NOT designed for external use.
that leaves a few general paths (in order that I would recommend):
since you are abandoning 1/2 the PCIe slots, you should have plenty of slots for expanders or SAS adapters.
- 1 external SAS card and just use the SATA/SAS ports for the first chassis. + PCI SAS adapter for the 2nd chassis.
- expander that has both internal and external SAS ports (low profile might be difficult) + PCI SAS adapter for the 2nd chassis.
- get a RES2V240 + PCI SAS adapters for both chassis.
low profile, but SAS3, so expensive. you would only be getting SAS1 out of it, but you would be getting full speeds possible. you would need 8087 > 8043 cables. the art of server hardware is usually updated to the newest firmware and fully tested.
Adaptec AEC-82885T 36-Port SAS-3 12Gbps Expander firmware B059
oh. found a cheaper one. expanders are less likely to be fakes - low volume. (I'm tempted to get one of these actually, though I dont really have a use for it...)
Adaptec 2283400-R AEC-82885T/LENOVO 36Port 12Gb/s SAS Expander Card 82885T
intel:
Intel RES3FV288 RAID Expander 36 Port 12Gb/s SAS PCI Express W/Full Height BRKT
high profile
HP 24-Bay 3GB SAS Expander Card 487738-001 468405-002there are much cheaper ones but these are an example.
Aom-Sas3-16i16e for sale | eBay
Find great deals on eBay for Aom-Sas3-16i16e. Shop with confidence.www.ebay.ca![]()
![]()
as these are basically just cables soldered to a PCB, cheap ones are usually OK.
Dual Ports Mini SAS Internal SFF-8087 to External HD SFF-8088 PCI SAS Adapter
RAID card does not equal HBA. when using an HBA, refer to it as an HBA, especially here where RAID + ZFS = bad.raid card
yes. we all say that. then get racks of chassis.I will not be expanding beyond this many drives
That uses the Intel PCH SAS option, which was somewhat popular in the Xeon E5 v1/v2 generation and disappeared in the E5 v3/v4 generation. It's similar to PCH SATA.X9DR3-F
That uses an LSI SAS2208 - of course, it's a SAS controller, but that's obvious. The problem is that it's typically only compatible with RAID firmware, which is a no-go. There may be a way to get IT firmware onto the thing, but I'll let someone with specific experience provide more information.
That one uses an LSI SAS2308, which is one of the go-to controllers as it supports IR (which is okay) and IT mode firmware (preferred). See for instance the once-ubiquitous X10SL7-F.
I read the description on how to flash the SAS2208 to the SAS2308 firmware. That looked doable but unsupported. There was a comment about an option in the SAS2208 firmware to select JBOD mode for the drives. I did that and below is what bootup looks like. I was able to move drives from the SAS2208 to the onboard SATA and vice versa with no issue. Do you think there is still an issue using the JBOD mode of the SAS2208 firmware? This is not the same as the technique to create dummy drives that apparently does have issues. If you compare what my bootup looks like and the after screen in the SAS2208/SAS2308 flash post https://www.truenas.com/community/t...log-zil-with-zfs-on-freenas.13633/post-527596 They look the same to me. Do you think there is a difference? I will use this in my backup server so I am really looking forward to some feedback. If I do not select the JBOD option I get the RAID config screens so I do not think I happen to have one that was modded.X9DRH-7F
That uses an LSI SAS2208 - of course, it's a SAS controller, but that's obvious. The problem is that it's typically only compatible with RAID firmware, which is a no-go. There may be a way to get IT firmware onto the thing, but I'll let someone with specific experience provide more information.