10 team standard Start two of Dalton , Tannehill , Rivers <| sep |> Just make some simple brown gravy . Pan drippings , a bit of flour , stir and add a bit milk and water . Salt and pepper to taste . <| sep |> Big Horn sheep do the same thing . <| sep |> WET PALLETE . Wet . Pallete . <| sep |> I was just responding to his questions . I ' m not advocating for voat or anything . <| sep |> Writethrough without a BBU isn ' t the problem , it ' s writeback mode with the BBU that causes the potential mismatch in what ZFS thinks vs what actually is ZFS will think the data is safely on disk , but it might actually be in the RAID controller ' s cache . hardware RAID does some things to the data that will fuck up the checksumsIf those checksums or metadata are in the RAID controller ' s cache and it goes sideways , you can definitely screw things up . That ' s down to luck though . Someone may be able to go the entire system ' s lifetime without ever hitting that problem , and things are great for them because they got fast sync writes without SLOG thanks to BBWC . But someone else might have their RAID card or battery die at a crucial point , lose a few critical pieces of data , and torch a filedatasettheir entire pool . The linked doc does mention HW RAID in a few places , but it also calls out the cache a couple times make sure your controller enables flushing , and make sure arrays don ' t flush as a potential pain point . Perhaps ZFS is able to cope with HW RAID , but it ' s certainly not the intended configuration .