fvdw-sl on WD My Cloud

[fvdw]

I will sent you 3 file packages by pm,
fvdw-sl-18-1- base tgz archive extract that in p1
p5-base tgz archive extract this in p5
p10rootfs-v4 tgz archive exctract this in /dev/md0 on p10 (p10 must contain raid1 /dev/md0 !)

After that put the disk in your wd mycloud gen 1 and see if the magixc happens

Note there will be no additional kernel modules loaded I need to check which one will be required and if they are availaible
Loading of ethernet module will be done for the moment in p10, this may be changed later

[matt_max]

Do I need to create new partitions or use the existing ones?

[fvdw]

You need to create new partitions with sizes as described 2 post earlier
viewtopic.php?f=4&t=3635&start=140#p37105

[matt_max]

I mean is it mandatory to create new partitions? If original ones are even slightly larger I can use them or do they need to have exact same size as you described?

[fvdw]

What are the sizes of the original ones?
Nevertheless it is better to destroy the partition table and start from scratch.

[fvdw]

Check your pm inbox

[matt_max]

Original partitions structure:

Code: Select all

GPT fdisk (gdisk) version 1.0.9

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

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 976773168 sectors, 465.8 GiB
Model: 00LPVX-22V0TT0 
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): D18B1F01-B99D-4A7C-B5B1-365B04F5CF05
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 128079853 sectors (61.1 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         4196351   2.0 GiB     FD00  primary
   2         4196352         8390655   2.0 GiB     FD00  primary
   3         8390656         9414655   500.0 MiB   0700  primary
   4         9414656       848275455   400.0 GiB   0700  primary
   5       848275456       848480255   100.0 MiB   0700  primary
   6       848480256       848685055   100.0 MiB   0700  primary
   7       848685056       848689151   2.0 MiB     0700  primary
   8       848689152       848695295   3.0 MiB     0700  primary


I've made exact copy of all partitions from my wd disc (check the odd ids) shrinking only part4.
Output from parted looks like this:

Code: Select all

Model: ATA IRP-SSDPR-S25C-5 (scsi)
Dysk /dev/sda: 512GB
Rozmiar sektora (logiczny/fizyczny): 512B/512B
Tablica partycji: gpt
Flagi dysku:

Numer  Początek  Koniec  Rozmiar  System plików  Nazwa                         Flaga
 1     1049kB    106MB   105MB    ntfs           Basic data partition          ukryta, diag
 2     106MB     211MB   105MB    fat32          EFI system partition          ładowalna, esp
 3     211MB     228MB   16,8MB                  Microsoft reserved partition  msftres
 4     228MB     108GB   107GB    ntfs           Basic data partition          msftdata
 5     108GB     430GB   322GB    ntfs           Basic data partition          msftdata
 6     430GB     512GB   82,4GB   btrfs          Linux filesystem


Model: WDC WD50 00LPVX-22V0TT0 (scsi)
Dysk /dev/sdb: 500GB
Rozmiar sektora (logiczny/fizyczny): 512B/512B
Tablica partycji: gpt
Flagi dysku:

Numer  Początek  Koniec  Rozmiar  System plików   Nazwa    Flaga
 1     1049kB    2149MB  2147MB   ext3            primary  raid
 2     2149MB    4296MB  2147MB   ext3            primary  raid
 3     4296MB    4820MB  524MB    linux-swap(v1)  primary  msftdata
 4     4820MB    434GB   429GB    ext4            primary  msftdata
 5     434GB     434GB   105MB                    primary  msftdata
 6     434GB     435GB   105MB                    primary  msftdata
 7     435GB     435GB   2097kB                   primary  msftdata
 8     435GB     435GB   3146kB                   primary  msftdata


Model: Nieznane (unknown)
Dysk /dev/zram0: 8246MB
Rozmiar sektora (logiczny/fizyczny): 4096B/4096B
Tablica partycji: loop
Flagi dysku:

Numer  Początek  Koniec  Rozmiar  System plików   Flaga
 1     0,00B     8246MB  8246MB   linux-swap(v1)


Now - if I understood correctly - I should create partitions in that order:

Code: Select all

GPT fdisk (gdisk) version 1.0.9

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

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 976773168 sectors, 465.8 GiB
Model: 00LPVX-22V0TT0 
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 2402C150-1331-4EA9-A85D-E33EE5ECC194
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2029 sectors (1014.5 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         1050623   512.0 MiB   FD00 
   2         1050624         2099199   512.0 MiB   FD00 
   3         2099200         3147775   512.0 MiB   8200 
   4         3147776         4720639   768.0 MiB   8300 
   5         4720640         6293503   768.0 MiB   8300 
   6         6293504         6313983   10.0 MiB    8300 
   7         6313984         6318079   2.0 MiB     8300 
   8         6318080       976773119   462.7 GiB   8300 


But something isn't clear for me. How can I create array on partition #10? If it is raid1 it should be assembled from 2 partitions - for example sda1 and sda2 but you ask me to create them separately. I'm confused :scratch
So IMHO I should do something like this:

Code: Select all

mdadm --create --verbose --level=1 --metadata=0.9 --raid-devices=2 /dev/md0 /dev/sdb1 /dev/sdb2


So sdb1 and sdb2 should be FD00 not 8300.

[fvdw]

The reason we want to boot from /dev/md0 and using autodetect raid.
/dev/md0 should be on the partition containing the root file system we want to load, in fvdw-sl case we want to use sda10. This rootfs will load a chrooted fvdw-sl linux system from sda1 or sda2. In this way we can update firmware. For instance we are running from sda1, the new firmware will then be stored on sda2 and on sda10 we set chrooted boot partition to sda2 iso sda1. So sfa2 will be used in next boot.
Afaik it should be possible to create a raid1 array using only partition.vif thats not possible we can add sda9 and make raid1 with sda9 and sda10.
Why we want to use sda1 and sra2 in this way is to keep same setup as used on lacie nas which prevent making a lot of adaptations in the firmware

[fvdw]

So your partition setup is not ok

[matt_max]

The reason we want to boot from /dev/md0 and using autodetect raid.
/dev/md0 should be on the partition containing the root file system we want to load, in fvdw-sl case we want to use sda10. This rootfs will load a chrooted fvdw-sl linux system from sda1 or sda2. In this way we can update firmware. For instance we are running from sda1, the new firmware will then be stored on sda2 and on sda10 we set chrooted boot partition to sda2 iso sda1. So sfa2 will be used in next boot.
Afaik it should be possible to create a raid1 array using only partition.vif thats not possible we can add sda9 and make raid1 with sda9 and sda10.
Why we want to use sda1 and sra2 in this way is to keep same setup as used on lacie nas which prevent making a lot of adaptations in the firmware

Ok but software raid is build from partitions - so in my opinion there is no point to create two separate partitions sdb1 and sdb2 if we do not create array.
I think it should looks like this:
sdX1 - 512MB ext3 fvdw-sl firmware (what is that precisely?)
sdX2 - 512MB swap
sdX3 - 768MB ext3? (backup if using p5 fails, for the moment no use)
sdX4 - 768MB ext3? (fvdw-sl database and persitent files)
sdX5 - 10MB ext3? (uImage - which one? original or that one you attached here?)
sdX6 - 2MB (barebox)
sdX7 and sdX8 = /dev/md0 (FD00 - raid) That will be the root partition
sdX9 - ext4 - rest of free space.

P.S. Ok - I think I understand now.

Code: Select all

PT fdisk (gdisk) version 1.0.9

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

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 976773168 sectors, 465.8 GiB
Model: 00LPVX-22V0TT0 
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 2402C150-1331-4EA9-A85D-E33EE5ECC194
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2029 sectors (1014.5 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         1050623   512.0 MiB   8300 
   2         1050624         2099199   512.0 MiB   8300 
   3         2099200         3147775   512.0 MiB   8200 
   4         3147776         4720639   768.0 MiB   8300 
   5         4720640         6293503   768.0 MiB   8300 
   6         6293504         6313983   10.0 MiB    8300 
   7         6313984         6318079   2.0 MiB     8300 
   8       975724544       976773119   512.0 MiB   FD00 
   9       974675968       975724543   512.0 MiB   FD00 
  10         6318080       974675967   461.7 GiB   8300 


Is that correct?