home.social

#raid1 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #raid1, aggregated by home.social.

fetched live
  1. Started #zpool shinannigans. I'm switching from RAIDZ1 to Stripe storage type and want to remove two old, smaller drives. At the end, it should be one of those:

    1. Same storage size, less power consumption, colder NAS, faster storage, and two empty drive bays.

    2. Lost data, fire, and explosions.

    #homelab #NAS #DYNAS #zfs #RAID1 #Raidz1 #storage

  2. Started #zpool shinannigans. I'm switching from RAIDZ1 to Stripe storage type and want to remove two old, smaller drives. At the end, it should be one of those:

    1. Same storage size, less power consumption, colder NAS, faster storage, and two empty drive bays.

    2. Lost data, fire, and explosions.

    #homelab #NAS #DYNAS #zfs #RAID1 #Raidz1 #storage

  3. Started #zpool shinannigans. I'm switching from RAIDZ1 to Stripe storage type and want to remove two old, smaller drives. At the end, it should be one of those:

    1. Same storage size, less power consumption, colder NAS, faster storage, and two empty drive bays.

    2. Lost data, fire, and explosions.

    #homelab #NAS #DYNAS #zfs #RAID1 #Raidz1 #storage

  4. Started #zpool shinannigans. I'm switching from RAIDZ1 to Stripe storage type and want to remove two old, smaller drives. At the end, it should be one of those:

    1. Same storage size, less power consumption, colder NAS, faster storage, and two empty drive bays.

    2. Lost data, fire, and explosions.

    #homelab #NAS #DYNAS #zfs #RAID1 #Raidz1 #storage

  5. #Proxmox / #KVM: Ist es geschickter, zwei als Datenspeicher genutzte #Raid1 als "Festplatte" in die VM zu geben, und dort #LVM aufzusetzen, um die beiden zu verbinden. Oder sollte ich LVM auch auf dem Host aufsetzen und als virtiofs in die VM geben?
    Ich tendiere zu ersterem.

  6. #Proxmox / #KVM: Ist es geschickter, zwei als Datenspeicher genutzte #Raid1 als "Festplatte" in die VM zu geben, und dort #LVM aufzusetzen, um die beiden zu verbinden. Oder sollte ich LVM auch auf dem Host aufsetzen und als virtiofs in die VM geben?
    Ich tendiere zu ersterem.

  7. #Proxmox / #KVM: Ist es geschickter, zwei als Datenspeicher genutzte #Raid1 als "Festplatte" in die VM zu geben, und dort #LVM aufzusetzen, um die beiden zu verbinden. Oder sollte ich LVM auch auf dem Host aufsetzen und als virtiofs in die VM geben?
    Ich tendiere zu ersterem.

  8. Ah, the thrilling saga of a #techie setting up a #FreeBSD home #NAS because apparently, Netflix wasn't entertaining enough 🤓. In a riveting tale of #RAID1 configurations and SSD slot descriptions, the author bravely sacrifices their social life to the gods of data redundancy 💾. Meanwhile, the rest of us are still trying to figure out how to connect our WiFi 📶.
    rtfm.co.ua/en/freebsd-home-nas #sociallife #sacrifice #HackerNews #ngated

  9. Ah, the thrilling saga of a #techie setting up a #FreeBSD home #NAS because apparently, Netflix wasn't entertaining enough 🤓. In a riveting tale of #RAID1 configurations and SSD slot descriptions, the author bravely sacrifices their social life to the gods of data redundancy 💾. Meanwhile, the rest of us are still trying to figure out how to connect our WiFi 📶.
    rtfm.co.ua/en/freebsd-home-nas #sociallife #sacrifice #HackerNews #ngated

  10. Ah, the thrilling saga of a #techie setting up a #FreeBSD home #NAS because apparently, Netflix wasn't entertaining enough 🤓. In a riveting tale of #RAID1 configurations and SSD slot descriptions, the author bravely sacrifices their social life to the gods of data redundancy 💾. Meanwhile, the rest of us are still trying to figure out how to connect our WiFi 📶.
    rtfm.co.ua/en/freebsd-home-nas #sociallife #sacrifice #HackerNews #ngated

  11. Ah, the thrilling saga of a #techie setting up a #FreeBSD home #NAS because apparently, Netflix wasn't entertaining enough 🤓. In a riveting tale of #RAID1 configurations and SSD slot descriptions, the author bravely sacrifices their social life to the gods of data redundancy 💾. Meanwhile, the rest of us are still trying to figure out how to connect our WiFi 📶.
    rtfm.co.ua/en/freebsd-home-nas #sociallife #sacrifice #HackerNews #ngated

  12. Random update that hits both my #photog and #sysadmin roles; I ran out of disk space for my raw #photography recently. I have a home-made #NAS box with a pair of disks in #RAID1 running Rocky Linux and I needed to get more space. I spent an evening shopping around for the best value I could get in local disks and that required driving to three Canada Computers locations to pick up one drive at each so I could build a #RAID5 array and not deal with this again in the near future. [ continues ]

  13. Random update that hits both my #photog and #sysadmin roles; I ran out of disk space for my raw #photography recently. I have a home-made #NAS box with a pair of disks in #RAID1 running Rocky Linux and I needed to get more space. I spent an evening shopping around for the best value I could get in local disks and that required driving to three Canada Computers locations to pick up one drive at each so I could build a #RAID5 array and not deal with this again in the near future. [ continues ]

  14. Random update that hits both my #photog and #sysadmin roles; I ran out of disk space for my raw #photography recently. I have a home-made #NAS box with a pair of disks in #RAID1 running Rocky Linux and I needed to get more space. I spent an evening shopping around for the best value I could get in local disks and that required driving to three Canada Computers locations to pick up one drive at each so I could build a #RAID5 array and not deal with this again in the near future. [ continues ]

  15. Random update that hits both my #photog and #sysadmin roles; I ran out of disk space for my raw #photography recently. I have a home-made #NAS box with a pair of disks in #RAID1 running Rocky Linux and I needed to get more space. I spent an evening shopping around for the best value I could get in local disks and that required driving to three Canada Computers locations to pick up one drive at each so I could build a #RAID5 array and not deal with this again in the near future. [ continues ]

  16. Ich brauche nochmal #Brainpower der #EDV #Bubble 🤣

    Da mein bisheriges, betagtes, leistungsschwaches 1-Bay
    #QNAP #NAS sehr langsam ist, z.B. beim #rsync, habe ich inzwischen das #Ugreen #NAS #DPX2800 gekauft, mit 32 GB #RAM aufgerüstet und 2 #NVNE mit je 2 TB eingebaut.

    Azf den beiden M.2 ist
    #Proxmox im #ZFS #RAID1 installiert. #Homeassistant und #TrueNAS laufen je in einer #VM.

    TrueNAS soll nun einen
    #Datenpool in Form eines verschlüsselten ZFS RAID 1 auf 2 16 TB Festplatten bekommen. So weit so gut.

    Nur: Wie bekomme ich die
    #Daten vom alten NAS, die in einer verschlüsselten #LUKS #Partition liegen, in den Datenpool?

    Über
    #Netzwerk kopieren ist keine wirkliche Option. Das ist für ~ 10 TB Nutzdaten viel zu langsam.

    Bitte
    #Boost für mehr Reichweite. 🙏

  17. Ich brauche nochmal #Brainpower der #EDV #Bubble 🤣

    Da mein bisheriges, betagtes, leistungsschwaches 1-Bay
    #QNAP #NAS sehr langsam ist, z.B. beim #rsync, habe ich inzwischen das #Ugreen #NAS #DPX2800 gekauft, mit 32 GB #RAM aufgerüstet und 2 #NVNE mit je 2 TB eingebaut.

    Azf den beiden M.2 ist
    #Proxmox im #ZFS #RAID1 installiert. #Homeassistant und #TrueNAS laufen je in einer #VM.

    TrueNAS soll nun einen
    #Datenpool in Form eines verschlüsselten ZFS RAID 1 auf 2 16 TB Festplatten bekommen. So weit so gut.

    Nur: Wie bekomme ich die
    #Daten vom alten NAS, die in einer verschlüsselten #LUKS #Partition liegen, in den Datenpool?

    Über
    #Netzwerk kopieren ist keine wirkliche Option. Das ist für ~ 10 TB Nutzdaten viel zu langsam.

    Bitte
    #Boost für mehr Reichweite. 🙏

  18. Ich brauche nochmal #Brainpower der #EDV #Bubble 🤣

    Da mein bisheriges, betagtes, leistungsschwaches 1-Bay
    #QNAP #NAS sehr langsam ist, z.B. beim #rsync, habe ich inzwischen das #Ugreen #NAS #DPX2800 gekauft, mit 32 GB #RAM aufgerüstet und 2 #NVNE mit je 2 TB eingebaut.

    Azf den beiden M.2 ist
    #Proxmox im #ZFS #RAID1 installiert. #Homeassistant und #TrueNAS laufen je in einer #VM.

    TrueNAS soll nun einen
    #Datenpool in Form eines verschlüsselten ZFS RAID 1 auf 2 16 TB Festplatten bekommen. So weit so gut.

    Nur: Wie bekomme ich die
    #Daten vom alten NAS, die in einer verschlüsselten #LUKS #Partition liegen, in den Datenpool?

    Über
    #Netzwerk kopieren ist keine wirkliche Option. Das ist für ~ 10 TB Nutzdaten viel zu langsam.

    Bitte
    #Boost für mehr Reichweite. 🙏

  19. Ich brauche nochmal #Brainpower der #EDV #Bubble 🤣

    Da mein bisheriges, betagtes, leistungsschwaches 1-Bay
    #QNAP #NAS sehr langsam ist, z.B. beim #rsync, habe ich inzwischen das #Ugreen #NAS #DPX2800 gekauft, mit 32 GB #RAM aufgerüstet und 2 #NVNE mit je 2 TB eingebaut.

    Azf den beiden M.2 ist
    #Proxmox im #ZFS #RAID1 installiert. #Homeassistant und #TrueNAS laufen je in einer #VM.

    TrueNAS soll nun einen
    #Datenpool in Form eines verschlüsselten ZFS RAID 1 auf 2 16 TB Festplatten bekommen. So weit so gut.

    Nur: Wie bekomme ich die
    #Daten vom alten NAS, die in einer verschlüsselten #LUKS #Partition liegen, in den Datenpool?

    Über
    #Netzwerk kopieren ist keine wirkliche Option. Das ist für ~ 10 TB Nutzdaten viel zu langsam.

    Bitte
    #Boost für mehr Reichweite. 🙏

  20. Excited for Btrfs RAID1's "preferred read device" feature in Linux 6.14. This allows to have one fast device, example SSD backed bcache device and other slow cheap hard drive. We can set the bcache deice as preferred read device so reads are always fast.
    It also wears down only one disk reducing the chance of both the disks evenly wearing out which increases the chances of both of them failing around the same time.

    From the pull request:

    > more read IO balancing strategies (experimental config), add two new
    ways how to select a device for read if the profiles allow that (all RAID1*),
    the current default selects the device by pid which is good on average
    but less performant for single reader workloads
    - select preferred device for all reads (namely for testing)
    - round-robin, balance reads across devices relevant for the requested IO
    range

    Source: lore.kernel.org/lkml/cover.173

    #btrfs #linux #linux_6_14 #filesystems #bcache #raid #raid1 #nas #selfhosting #selfhost

  21. Excited for Btrfs RAID1's "preferred read device" feature in Linux 6.14. This allows to have one fast device, example SSD backed bcache device and other slow cheap hard drive. We can set the bcache deice as preferred read device so reads are always fast.
    It also wears down only one disk reducing the chance of both the disks evenly wearing out which increases the chances of both of them failing around the same time.

    From the pull request:

    > more read IO balancing strategies (experimental config), add two new
    ways how to select a device for read if the profiles allow that (all RAID1*),
    the current default selects the device by pid which is good on average
    but less performant for single reader workloads
    - select preferred device for all reads (namely for testing)
    - round-robin, balance reads across devices relevant for the requested IO
    range

    Source: lore.kernel.org/lkml/cover.173

    #btrfs #linux #linux_6_14 #filesystems #bcache #raid #raid1 #nas #selfhosting #selfhost

  22. Excited for Btrfs RAID1's "preferred read device" feature in Linux 6.14. This allows to have one fast device, example SSD backed bcache device and other slow cheap hard drive. We can set the bcache deice as preferred read device so reads are always fast.
    It also wears down only one disk reducing the chance of both the disks evenly wearing out which increases the chances of both of them failing around the same time.

    From the pull request:

    > more read IO balancing strategies (experimental config), add two new
    ways how to select a device for read if the profiles allow that (all RAID1*),
    the current default selects the device by pid which is good on average
    but less performant for single reader workloads
    - select preferred device for all reads (namely for testing)
    - round-robin, balance reads across devices relevant for the requested IO
    range

    Source: lore.kernel.org/lkml/cover.173

    #btrfs #linux #linux_6_14 #filesystems #bcache #raid #raid1 #nas #selfhosting #selfhost

  23. Excited for Btrfs RAID1's "preferred read device" feature in Linux 6.14. This allows to have one fast device, example SSD backed bcache device and other slow cheap hard drive. We can set the bcache deice as preferred read device so reads are always fast.
    It also wears down only one disk reducing the chance of both the disks evenly wearing out which increases the chances of both of them failing around the same time.

    From the pull request:

    > more read IO balancing strategies (experimental config), add two new
    ways how to select a device for read if the profiles allow that (all RAID1*),
    the current default selects the device by pid which is good on average
    but less performant for single reader workloads
    - select preferred device for all reads (namely for testing)
    - round-robin, balance reads across devices relevant for the requested IO
    range

    Source: lore.kernel.org/lkml/cover.173

  24. Oh boy, setting up this #RAID array is gonna be an overnight ordeal 🤪

    Last time I manually set up raid (specifically #raid1) was with two 4 Tb drives. Which I do not recall taking too long; maybe an hour or two. Now I am doing four 12 Tb in #raid5. Good thing I am on summer break 😅

  25. Oh boy, setting up this #RAID array is gonna be an overnight ordeal 🤪

    Last time I manually set up raid (specifically #raid1) was with two 4 Tb drives. Which I do not recall taking too long; maybe an hour or two. Now I am doing four 12 Tb in #raid5. Good thing I am on summer break 😅

  26. Oh boy, setting up this #RAID array is gonna be an overnight ordeal 🤪

    Last time I manually set up raid (specifically #raid1) was with two 4 Tb drives. Which I do not recall taking too long; maybe an hour or two. Now I am doing four 12 Tb in #raid5. Good thing I am on summer break 😅

  27. @var it’s nice to have a separate dedicated computer for managing the backup. You really need to have all backup disks attached to SATA. USB is not reliable for backup purposes because is likely to lose data when a sudden power outage occurs. So if you have (for example) 4 disks that all attach to SATA, that is a lot of IO happening, which you really don’t want when you are using your computer for other things that may need that IO, especially games or multimedia. You’ll notice the performance hit if it is backups are happening on a computer that you use for other things.

    Also, it’s nice that the NAS comes with software that takes care of things like software RAID-1 or #ZFS for you. Some #NAS products will do #RAID1 in hardware for you.

    #tech #hardware #selfhosting

  28. @var it’s nice to have a separate dedicated computer for managing the backup. You really need to have all backup disks attached to SATA. USB is not reliable for backup purposes because is likely to lose data when a sudden power outage occurs. So if you have (for example) 4 disks that all attach to SATA, that is a lot of IO happening, which you really don’t want when you are using your computer for other things that may need that IO, especially games or multimedia. You’ll notice the performance hit if it is backups are happening on a computer that you use for other things.

    Also, it’s nice that the NAS comes with software that takes care of things like software RAID-1 or #ZFS for you. Some #NAS products will do #RAID1 in hardware for you.

    #tech #hardware #selfhosting

  29. @var it’s nice to have a separate dedicated computer for managing the backup. You really need to have all backup disks attached to SATA. USB is not reliable for backup purposes because is likely to lose data when a sudden power outage occurs. So if you have (for example) 4 disks that all attach to SATA, that is a lot of IO happening, which you really don’t want when you are using your computer for other things that may need that IO, especially games or multimedia. You’ll notice the performance hit if it is backups are happening on a computer that you use for other things.

    Also, it’s nice that the NAS comes with software that takes care of things like software RAID-1 or #ZFS for you. Some #NAS products will do #RAID1 in hardware for you.

    #tech #hardware #selfhosting

  30. AI has gotten some training clearly from programmers? "It's not a bug or flaw. It's an artifact." - Great answer!!! - Why running "mount -a" repeatedly ignores all other mounted file systems, but for an #Btrfs #RAID1 mounts it gives an error (exit level 32) that it's already mounted. Ok? What's the logic here? #mount #linux
  31. AI has gotten some training clearly from programmers? "It's not a bug or flaw. It's an artifact." - Great answer!!! - Why running "mount -a" repeatedly ignores all other mounted file systems, but for an #Btrfs #RAID1 mounts it gives an error (exit level 32) that it's already mounted. Ok? What's the logic here? #mount #linux
  32. AI has gotten some training clearly from programmers? "It's not a bug or flaw. It's an artifact." - Great answer!!! - Why running "mount -a" repeatedly ignores all other mounted file systems, but for an #Btrfs #RAID1 mounts it gives an error (exit level 32) that it's already mounted. Ok? What's the logic here? #mount #linux
  33. AI has gotten some training clearly from programmers? "It's not a bug or flaw. It's an artifact." - Great answer!!! - Why running "mount -a" repeatedly ignores all other mounted file systems, but for an #Btrfs #RAID1 mounts it gives an error (exit level 32) that it's already mounted. Ok? Logic?

  34. How I switched us.slackware.nl from lilo to grub

    Today I finally switched my US server from lilo to grub as its bootloader.

    The reason for doing it now, is that I usually do not have a remote IP console (KVM) to that physical server which is located in a US datacenter whereas I live in Europe. This server's storage is configured as software RAID1

    alien.slackbook.org/blog/how-i

  35. How I switched us.slackware.nl from lilo to grub

    Today I finally switched my US server from lilo to grub as its bootloader.

    The reason for doing it now, is that I usually do not have a remote IP console (KVM) to that physical server which is located in a US datacenter whereas I live in Europe. This server's storage is configured as software RAID1

    alien.slackbook.org/blog/how-i

    #Slackware #Software #gdisk #gpt #grub #lilo #mbr #raid #raid1

  36. How I switched us.slackware.nl from lilo to grub

    Today I finally switched my US server from lilo to grub as its bootloader.

    The reason for doing it now, is that I usually do not have a remote IP console (KVM) to that physical server which is located in a US datacenter whereas I live in Europe. This server's storage is configured as software RAID1

    alien.slackbook.org/blog/how-i

    #Slackware #Software #gdisk #gpt #grub #lilo #mbr #raid #raid1

  37. How I switched us.slackware.nl from lilo to grub

    Today I finally switched my US server from lilo to grub as its bootloader.

    The reason for doing it now, is that I usually do not have a remote IP console (KVM) to that physical server which is located in a US datacenter whereas I live in Europe. This server's storage is configured as software RAID1

    alien.slackbook.org/blog/how-i

    #Slackware #Software #gdisk #gpt #grub #lilo #mbr #raid #raid1

  38. @samurro
    I had to ditch LVM. You just can't remove a drive and boot without manual intervention in initramfs.

    The complete process is described here: dahlem-consulting.de/install-d

    #debian #raid1

  39. @samurro
    I had to ditch LVM. You just can't remove a drive and boot without manual intervention in initramfs.

    The complete process is described here: dahlem-consulting.de/install-d

    #debian #raid1

  40. @samurro
    I had to ditch LVM. You just can't remove a drive and boot without manual intervention in initramfs.

    The complete process is described here: dahlem-consulting.de/install-d

    #debian #raid1

  41. @samurro
    I had to ditch LVM. You just can't remove a drive and boot without manual intervention in initramfs.

    The complete process is described here: dahlem-consulting.de/install-d

    #debian #raid1

  42. I tried this solution serverfault.com/a/1144562 at least the installer goes through without a grub error, but the system still doesn't boot after the installation is through. Installing 12 on a software with seems like a high ask of the debian installer...

  43. I tried this solution serverfault.com/a/1144562 at least the installer goes through without a grub error, but the system still doesn't boot after the installation is through. Installing #debian 12 on a software #raid1 with #uefi seems like a high ask of the debian installer...

  44. I tried this solution serverfault.com/a/1144562 at least the installer goes through without a grub error, but the system still doesn't boot after the installation is through. Installing #debian 12 on a software #raid1 with #uefi seems like a high ask of the debian installer...

  45. @robertdahlem The question is how do I get a raid on my installation partition going. I want to have a across two smaller disks where root is installed, the installer now fumbled (grub error) when I tried to do it manually.