Raid5 Faile: can not change to fd00

Re: Raid5 Faile: can not change to fd00

Postby Jocko » Thu Jan 20, 2022 5:57 pm

So it was really a ms-dos table? do again gdisk -l /dev/sda and select the item 1 'MBR'
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Raid5 Faile: can not change to fd00

Postby Draftmancorp » Thu Jan 20, 2022 5:58 pm

Jocko wrote:So it was really a ms-dos table? do again gdisk -l /dev/sda and select the item 1 'MBR'


I'm pretty sure to chosen GPT douring the "Initialize hard disk and volume" ... so i really don't know why it sems to be mbr...

Code: Select all
login as: root
root@192.168.1.189's password:
root@Norman_Nas:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!

Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: damaged

Found valid MBR and corrupt GPT. Which do you want to use? (Using the
GPT MAY permit recovery of GPT data.)
 1 - MBR
 2 - GPT
 3 - Create blank GPT

Your answer: 1
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 1261DB24-B49A-4C9E-B12C-F6B38656B12F
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 8-sector boundaries
Total free space is 647636 sectors (316.2 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1          128520         1156679   502.0 MiB   8300  Linux filesystem
   2         1156680         2184839   502.0 MiB   8300  Linux filesystem
   3         2184840         3212999   502.0 MiB   8200  Linux swap
   5         3341520         5012279   815.8 MiB   8300  Linux filesystem
   6         5140800         5269319   62.8 MiB    8300  Linux filesystem
   7         5397840         6425999   502.0 MiB   8300  Linux filesystem
   8         6554520      3907024064   1.8 TiB     8300  Linux filesystem
root@Norman_Nas:/ #
Draftmancorp
Donator VIP
Donator VIP
 
Posts: 526
Joined: Thu May 02, 2013 1:55 pm

Re: Raid5 Faile: can not change to fd00

Postby Draftmancorp » Thu Jan 20, 2022 6:06 pm

at the end of this, I'll owe you another coffee :doh
Draftmancorp
Donator VIP
Donator VIP
 
Posts: 526
Joined: Thu May 02, 2013 1:55 pm

Re: Raid5 Faile: can not change to fd00

Postby Jocko » Thu Jan 20, 2022 6:07 pm

We go now to change the partition id on partition 8

So run
Code: Select all
gdisk /dev/sda
t and enter
8 and enter
FD00 and enter
p and enter
w and enter
y and enter


Note we need to the same thing on sd[bcde]. So post
Code: Select all
gdisk -l /dev/sdb
gdisk -l /dev/sdc
gdisk -l /dev/sdd
gdisk -l /dev/sde
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Raid5 Faile: can not change to fd00

Postby Draftmancorp » Thu Jan 20, 2022 6:08 pm

wait... at gdisk /dev/sda it require an answer 1, 2 or 3? imagine 1? nevermind :doh ok you can read next post.
Last edited by Draftmancorp on Thu Jan 20, 2022 6:14 pm, edited 2 times in total.
Draftmancorp
Donator VIP
Donator VIP
 
Posts: 526
Joined: Thu May 02, 2013 1:55 pm

Re: Raid5 Faile: can not change to fd00

Postby Draftmancorp » Thu Jan 20, 2022 6:10 pm

Before doing the same with other... is this ok?
Code: Select all
login as: root
root@192.168.1.189's password:
root@Norman_Nas:/ # gdisk /dev/sda
GPT fdisk (gdisk) version 0.8.5

Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!

Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: damaged

Found valid MBR and corrupt GPT. Which do you want to use? (Using the
GPT MAY permit recovery of GPT data.)
 1 - MBR
 2 - GPT
 3 - Create blank GPT

Your answer: t

Command (? for help): t
Partition number (1-10): 8
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 8300): FD00
Changed type of partition to 'Linux RAID'

Command (? for help): p
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): C02433D0-7BB7-46FC-A73E-0F65356C9E01
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 28866 sectors (14.1 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1         4036608         4038655   1024.0 KiB  0700  primary
   2         4048896      3907028991   1.8 TiB     0700  primary
   3         4040704         4042571   934.0 KiB   0700  primary
   4         4044800         4046848   1.0 MiB     0700  primary
   5            2048          514047   250.0 MiB   0700  primary
   6          530432          546497   7.8 MiB     0700  primary
   7          546816          578945   15.7 MiB    0700  primary
   8          579584         2266409   823.6 MiB   FD00  primary
   9         2267136         4018221   855.0 MiB   0700  primary
  10         4020224         4036289   7.8 MiB     0700  primary

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sda.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
root@Norman_Nas:/ #
Draftmancorp
Donator VIP
Donator VIP
 
Posts: 526
Joined: Thu May 02, 2013 1:55 pm

Re: Raid5 Faile: can not change to fd00

Postby Draftmancorp » Thu Jan 20, 2022 6:12 pm

Jocko wrote:Note we need to the same thing on sd[bcde]. So post
Code: Select all
gdisk -l /dev/sdb
gdisk -l /dev/sdc
gdisk -l /dev/sdd
gdisk -l /dev/sde


here we go:

Code: Select all
login as: root
root@192.168.1.189's password:
root@Norman_Nas:/ # gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): D82BD6FB-1D08-489F-9A9D-CA6D90022734
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5803998 sectors (2.8 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   8         5804032      3907029134   1.8 TiB     8300  Linux filesystem
root@Norman_Nas:/ # gdisk -l /dev/sdc
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 4BEC45E5-D068-4FD0-B82C-2815D65F0322
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5803998 sectors (2.8 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   8         5804032      3907029134   1.8 TiB     8300  Linux filesystem
root@Norman_Nas:/ # gdisk -l /dev/sdd
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdd: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): F1004E80-3AD7-4A21-9A29-A612310467E9
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5803998 sectors (2.8 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   8         5804032      3907029134   1.8 TiB     8300  Linux filesystem
root@Norman_Nas:/ # gdisk -l /dev/sde
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sde: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 485424C6-3BFF-4670-9703-E660DB98763B
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5803998 sectors (2.8 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   8         5804032      3907029134   1.8 TiB     8300  Linux filesystem
root@Norman_Nas:/ #
Draftmancorp
Donator VIP
Donator VIP
 
Posts: 526
Joined: Thu May 02, 2013 1:55 pm

Re: Raid5 Faile: can not change to fd00

Postby Jocko » Thu Jan 20, 2022 6:14 pm

Stop to do any thing on sda !

It is not the same table !
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Raid5 Faile: can not change to fd00

Postby Draftmancorp » Thu Jan 20, 2022 6:15 pm

Jocko wrote:Stop to do any thing
It is not the same table !


ok :shocked
Draftmancorp
Donator VIP
Donator VIP
 
Posts: 526
Joined: Thu May 02, 2013 1:55 pm

Re: Raid5 Faile: can not change to fd00

Postby Jocko » Thu Jan 20, 2022 6:19 pm

So I understand what was the damaged GPT table on sda, it was an orphan Lacie table with 10 partitions.

It seems you reactivated it by answer t instead of 1 on the first question

I hope you still have the mbr partition :crazy. So post
Code: Select all
fdisk -l /dev/sda
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

PreviousNext

Return to Lacie 5big Network vs2

Who is online

Users browsing this forum: No registered users and 10 guests