#gdisk — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gdisk, aggregated by home.social.
-
Онлайн миграция системного диска Enterprise Linux на другую СХД
Иногда бывает, что наступает EndOfLife систем хранения данных (СХД) и их нужно выводить из работы, т.к. заканчиваются запчасти. В нашем случае оказалось, что неcколько хостов с Enterprise Linux загружены с этой СХД и необходимо их плавно перевести на другую. Подключить две СХД через SAN к серверам достаточно просто, но как перетащить систему так, чтобы это прошло с минимальным влиянием на бизнес-процессы? В прошлой статье в блоге Bercut я знакомил читателя с утилитой fsarchiver , сегодня мы рассмотрим другой вариант миграции с pvmove и qaucli .
https://habr.com/ru/articles/875824/
#qaucli #pvmove #grub2 #системный_диск #Беркут #Bercut #gdisk #QLogic
-
Онлайн миграция системного диска Enterprise Linux на другую СХД
Иногда бывает, что наступает EndOfLife систем хранения данных (СХД) и их нужно выводить из работы, т.к. заканчиваются запчасти. В нашем случае оказалось, что неcколько хостов с Enterprise Linux загружены с этой СХД и необходимо их плавно перевести на другую. Подключить две СХД через SAN к серверам достаточно просто, но как перетащить систему так, чтобы это прошло с минимальным влиянием на бизнес-процессы? В прошлой статье в блоге Bercut я знакомил читателя с утилитой fsarchiver , сегодня мы рассмотрим другой вариант миграции с pvmove и qaucli .
https://habr.com/ru/articles/875824/
#qaucli #pvmove #grub2 #системный_диск #Беркут #Bercut #gdisk #QLogic
-
Онлайн миграция системного диска Enterprise Linux на другую СХД
Иногда бывает, что наступает EndOfLife систем хранения данных (СХД) и их нужно выводить из работы, т.к. заканчиваются запчасти. В нашем случае оказалось, что неcколько хостов с Enterprise Linux загружены с этой СХД и необходимо их плавно перевести на другую. Подключить две СХД через SAN к серверам достаточно просто, но как перетащить систему так, чтобы это прошло с минимальным влиянием на бизнес-процессы? В прошлой статье в блоге Bercut я знакомил читателя с утилитой fsarchiver , сегодня мы рассмотрим другой вариант миграции с pvmove и qaucli .
https://habr.com/ru/articles/875824/
#qaucli #pvmove #grub2 #системный_диск #Беркут #Bercut #gdisk #QLogic
-
Онлайн миграция системного диска Enterprise Linux на другую СХД
Иногда бывает, что наступает EndOfLife систем хранения данных (СХД) и их нужно выводить из работы, т.к. заканчиваются запчасти. В нашем случае оказалось, что неcколько хостов с Enterprise Linux загружены с этой СХД и необходимо их плавно перевести на другую. Подключить две СХД через SAN к серверам достаточно просто, но как перетащить систему так, чтобы это прошло с минимальным влиянием на бизнес-процессы? В прошлой статье в блоге Bercut я знакомил читателя с утилитой fsarchiver , сегодня мы рассмотрим другой вариант миграции с pvmove и qaucli .
https://habr.com/ru/articles/875824/
#qaucli #pvmove #grub2 #системный_диск #Беркут #Bercut #gdisk #QLogic
-
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
https://alien.slackbook.org/blog/how-i-switched-us-slackware-nl-from-lilo-to-grub/
#Slackware #Software #gdisk #gpt #grub #lilo #mbr #raid #raid1
-
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
https://alien.slackbook.org/blog/how-i-switched-us-slackware-nl-from-lilo-to-grub/
#Slackware #Software #gdisk #gpt #grub #lilo #mbr #raid #raid1
-
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
https://alien.slackbook.org/blog/how-i-switched-us-slackware-nl-from-lilo-to-grub/
#Slackware #Software #gdisk #gpt #grub #lilo #mbr #raid #raid1
-
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
https://alien.slackbook.org/blog/how-i-switched-us-slackware-nl-from-lilo-to-grub/
#Slackware #Software #gdisk #gpt #grub #lilo #mbr #raid #raid1
-
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
https://alien.slackbook.org/blog/how-i-switched-us-slackware-nl-from-lilo-to-grub/
#Slackware #Software #gdisk #gpt #grub #lilo #mbr #raid #raid1
-
i installed using legacy boot to sata, think i have to format nvme as gpt and go uefi #gdisk
-
i installed using legacy boot to sata, think i have to format nvme as gpt and go uefi #gdisk
-
i installed using legacy boot to sata, think i have to format nvme as gpt and go uefi #gdisk
-
@mfjurbala for user-friendly partitioning, I always use the port of GPT fdisk:
<https://www.freshports.org/sysutils/gdisk/>
then maybe newfs_msdos(8) or whatever to create the file system:
<https://man.freebsd.org/cgi/man.cgi?query=newfs_msdos&sektion=8&manpath=freebsd-release>
-
@mfjurbala for user-friendly partitioning, I always use the port of GPT fdisk:
<https://www.freshports.org/sysutils/gdisk/>
then maybe newfs_msdos(8) or whatever to create the file system:
<https://man.freebsd.org/cgi/man.cgi?query=newfs_msdos&sektion=8&manpath=freebsd-release>
-
@mfjurbala for user-friendly partitioning, I always use the port of GPT fdisk:
<https://www.freshports.org/sysutils/gdisk/>
then maybe newfs_msdos(8) or whatever to create the file system:
<https://man.freebsd.org/cgi/man.cgi?query=newfs_msdos&sektion=8&manpath=freebsd-release>
-
@mfjurbala for user-friendly partitioning, I always use the port of GPT fdisk:
<https://www.freshports.org/sysutils/gdisk/>
then maybe newfs_msdos(8) or whatever to create the file system:
<https://man.freebsd.org/cgi/man.cgi?query=newfs_msdos&sektion=8&manpath=freebsd-release>
-
@mfjurbala for user-friendly partitioning, I always use the port of GPT fdisk:
<https://www.freshports.org/sysutils/gdisk/>
then maybe newfs_msdos(8) or whatever to create the file system:
<https://man.freebsd.org/cgi/man.cgi?query=newfs_msdos&sektion=8&manpath=freebsd-release>
-
Rescuing a primary partition table that has been corrupted, when the partition itself is intact, should be easy. Especially in the case of EFI partitioning. See the #rodsbooks doco.
Alternatively: The partition table actually being intact and the NTFS flags saying that the partition needs checking are on, or the MFT pointer or BPB data being lost (which latter could well make it not look like an NTFS volume), requires a different solution.
-
Rescuing a primary partition table that has been corrupted, when the partition itself is intact, should be easy. Especially in the case of EFI partitioning. See the #rodsbooks doco.
Alternatively: The partition table actually being intact and the NTFS flags saying that the partition needs checking are on, or the MFT pointer or BPB data being lost (which latter could well make it not look like an NTFS volume), requires a different solution.
-
Rescuing a primary partition table that has been corrupted, when the partition itself is intact, should be easy. Especially in the case of EFI partitioning. See the #rodsbooks doco.
Alternatively: The partition table actually being intact and the NTFS flags saying that the partition needs checking are on, or the MFT pointer or BPB data being lost (which latter could well make it not look like an NTFS volume), requires a different solution.
-
It depends whether it has lost your partition table or unformatted (or marked as needing scan and repair) the partition.
First thing to do is to use gdisk(8) or sfdisk(8) or *something* to determine what of your partition table, if anything, is actually there at the moment.
Because that tells you what to fix.
-
It depends whether it has lost your partition table or unformatted (or marked as needing scan and repair) the partition.
First thing to do is to use gdisk(8) or sfdisk(8) or *something* to determine what of your partition table, if anything, is actually there at the moment.
Because that tells you what to fix.
-
It depends whether it has lost your partition table or unformatted (or marked as needing scan and repair) the partition.
First thing to do is to use gdisk(8) or sfdisk(8) or *something* to determine what of your partition table, if anything, is actually there at the moment.
Because that tells you what to fix.
-
It depends whether it has lost your partition table or unformatted (or marked as needing scan and repair) the partition.
First thing to do is to use gdisk(8) or sfdisk(8) or *something* to determine what of your partition table, if anything, is actually there at the moment.
Because that tells you what to fix.
-
For what it's worth, if you are using the EFI partitioning scheme:
It should be relatively easy to use something like gdisk(8) or fixparts(8) to restore from the backup copy of the partition table.
If the primary and backup copies have both been zapped, then the likelihood is that some serious data corruption has happened, since they are at opposite ends of the disc, nominally.
https://www.rodsbooks.com/gdisk/repairing.html
-
For what it's worth, if you are using the EFI partitioning scheme:
It should be relatively easy to use something like gdisk(8) or fixparts(8) to restore from the backup copy of the partition table.
If the primary and backup copies have both been zapped, then the likelihood is that some serious data corruption has happened, since they are at opposite ends of the disc, nominally.
https://www.rodsbooks.com/gdisk/repairing.html
-
For what it's worth, if you are using the EFI partitioning scheme:
It should be relatively easy to use something like gdisk(8) or fixparts(8) to restore from the backup copy of the partition table.
If the primary and backup copies have both been zapped, then the likelihood is that some serious data corruption has happened, since they are at opposite ends of the disc, nominally.
https://www.rodsbooks.com/gdisk/repairing.html
-
For what it's worth, if you are using the EFI partitioning scheme:
It should be relatively easy to use something like gdisk(8) or fixparts(8) to restore from the backup copy of the partition table.
If the primary and backup copies have both been zapped, then the likelihood is that some serious data corruption has happened, since they are at opposite ends of the disc, nominally.
https://www.rodsbooks.com/gdisk/repairing.html