seems your fdisk is able to read disks with gpt partition table. Probably a mewer version than mines.
Anyhow from the output of gdisk we learn that there is a problem with the disk, you could try to use the 'v' command in gdisk and the expert commands to try to repair the disk errors and after that sees if it boots. But I am afraid that this disk may have some bad sectors. You should test all other disks as well as the used in raid array.If two of them have a problem the raid array cannot be assembled. It uses raid for all data partitions as far as I know. To check the file systems on those partitions the arrays must be assembled first. As long as the nas won't boot you can forget that
However if it uses uefi boot than most likely partition 1 contains the bootloader (grub)
To see if thats true try to mount the first partition (should be fat32) and look to content of the partition, if it contains a folder efi and subfolder boot then it is the one we are looking for.
- Code: Select all
mkdir sdb1
mount /dev/sdb1 /sdb1
ls /sdb1
try mount -t vfat /dev/sdb1 /sdb1 if it complains that it cannot determine file system
Then use 'blkid' command to find out the partition uuid of the that partition. If we have that we might be able to prepare an usb stick and boot a kernel from usb. For that we will need to know that partition UUID
If that doesn't work we can try to prepare a disk with a kernel and basic linux system and see if that loads. I did some tests in the meantime with a seagate 4 bay pro nas,that is similar to 5bigpro.