gamebrigada
Dabbler
- Joined
- Jul 9, 2019
- Messages
- 12
Hello,
I'm running 2 identical Supermicro E1CR45H's, 1 as a primary, and 1 as a backup. The primary runs replication tasks to the backup.
Hardware:
45x 10TB Seagate drives HDD-A10T-ST10000NM0096
2x Intel D3-S4510's for Freenas running in mirror under ZFS as well
LSI 3108 Cachevault ultra running in passthrough mode (IT mode) for the disks
2x Intel 905P's. 1 for SLOG, 1 for ZIL, sized accordingly
128GB DDR4-2666 ECC
The backup seems to have taken a dump. It seems to have completely crashed and now fails to import the pool on boot, dumping to a db> shell. Image for reference. The db shell doesn't seem to allow me to do much.
This is the second time such an issue has happened to the backup system. Last time I blamed it on shitty hardware and ended up buying a duplicate of the primary. With my google skills last time I made it worse and don't want to make the same mistake this time. The primary has about 80TB of data that I really don't want to re-replicate it. Would be a royal pain in the ass. Also want to make sure I know how to fix this problem if the primary takes a similar dump...
There was not a power outage, both systems are on power backups.
I'm running 2 identical Supermicro E1CR45H's, 1 as a primary, and 1 as a backup. The primary runs replication tasks to the backup.
Hardware:
45x 10TB Seagate drives HDD-A10T-ST10000NM0096
2x Intel D3-S4510's for Freenas running in mirror under ZFS as well
LSI 3108 Cachevault ultra running in passthrough mode (IT mode) for the disks
2x Intel 905P's. 1 for SLOG, 1 for ZIL, sized accordingly
128GB DDR4-2666 ECC
The backup seems to have taken a dump. It seems to have completely crashed and now fails to import the pool on boot, dumping to a db> shell. Image for reference. The db shell doesn't seem to allow me to do much.
This is the second time such an issue has happened to the backup system. Last time I blamed it on shitty hardware and ended up buying a duplicate of the primary. With my google skills last time I made it worse and don't want to make the same mistake this time. The primary has about 80TB of data that I really don't want to re-replicate it. Would be a royal pain in the ass. Also want to make sure I know how to fix this problem if the primary takes a similar dump...
There was not a power outage, both systems are on power backups.