fvdw-sl on WD My Cloud

[fvdw]

I am sorry but it is not correct, it should be like described earlier

Code: Select all

nr size type
1  512 MB 8300 linux file system (will contain fvdw-sl firmware)
2  512 MB 8300 linux file system (will contain fvdw-sl firmware)
3  512 MB 8200 linux swap
4  768 MB 8300 linux file system (is backup if using p5 fails, for the moment no use)
5  768 MB 8300 linux file system (will contain fvdw-sl database and persitent files
6  10 MB 8300 linux file system (will contain uImage)
7  2 MB 8300 linux filesystem (will contain barebox env)
10 512 MB FD00 Linux raid (will contain /dev/md0 with basic rootfs that will load either firmware from p1 or p2

8 rest of disk (will contain shared folders and files)

Create first partitions 1,2,3,45,6,7 and 10 and then partition 8

If you like to have two partitions for raid1 (dev/md0) it must be like this

Code: Select all

nr size type
1  512 MB 8300 linux file system (will contain fvdw-sl firmware)
2  512 MB 8300 linux file system (will contain fvdw-sl firmware)
3  512 MB 8200 linux swap
4  768 MB 8300 linux file system (is backup if using p5 fails, for the moment no use)
5  768 MB 8300 linux file system (will contain fvdw-sl database and persitent files
6  10 MB 8300 linux file system (will contain uImage)
7  2 MB 8300 linux filesystem (will contain barebox env)
9  512MB FD00 linux raid
10 512 MB FD00 Linux raid
(/dev/md0 will be assembled using sda9 and sda10 and  /dev/md0 will contain the basic p10rootfs that will load either firmware from p1 or p2

8 rest of disk (will contain shared folders and files)

Create first partitions 1,2,3,45,6,7 and 10 and then partition 8

fvdw-sl firmware is the firmware we are running...

[matt_max]

Ok - what about now:

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   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         6318080       974675967   461.7 GiB   8300 
   9       974675968       975724543   512.0 MiB   FD00 
  10       975724544       976773119   512.0 MiB   FD00 


And md0 array is assembled from sda9 and sda10.
I know that

fvdw-sl firmware is the firmware we are running...

but I was curious is it the /etc, /usr or all of them... (doesn't matter right now).

[fvdw]

Well that setup can be used but I rather prefer to have partition 8 as last partion on the disk
like this

Code: Select all

Disk /dev/sdc: 488397168 sectors, 232.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A0CDC7A4-AF74-4E66-9889-538A779F23CC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 488397134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         1050623   512.0 MiB   8300  Linux filesystem
   2         1050624         2099199   512.0 MiB   8300  Linux filesystem
   3         2099200         3147775   512.0 MiB   8200  Linux swap
   4         3147776         4720639   768.0 MiB   8300  Linux filesystem
   5         4720640         6293503   768.0 MiB   8300  Linux filesystem
   6         6293504         6313983   10.0 MiB    8300  Linux filesystem
   7         6313984         6318079   2.0 MiB     8300  Linux filesystem
   8         8415232       488397134   228.9 GiB   8300  Linux filesystem
   9         6318080         7366655   512.0 MiB   FD00  Linux RAID
  10         7366656         8415231   512.0 MiB   FD00  Linux RAID



Notice that partion 8 first sector is the one after partition 10

partitions 1,2,5 and /dev/md0 must get ext3 format and partition 8 ext4.

The three file archives sent 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 the raid1 arrau on p9+10

[matt_max]

I think I've done something wrong - output from console.
Enough for me today... :z)

[fvdw]

...mmm seems you have put the wrong kernel on p6
Barebox loads a linux 3.2.26 kernel compiled on 23 aug 2022, so one of my trial kernels
You should put the debian kernel (=3.2.68) in partition 6
As result the kernel module to activate the ethernet port will not be loaded as I have put 3.2.68 modules on p10rootfs
That also explains why why it cannot mount /dev/sda1. This kernel has a problem

So try the debian kernel if that solves this problem

:z)

[fvdw]

I have edited my last post

[fvdw]

ps it is remarkable that now this trial kernel doesn't give the getty issue...probably because now we have fvdw-sl base system on /dev/md0

[matt_max]

...mmm seems you have put the wrong kernel on p6
Barebox loads a linux 3.2.26 kernel compiled on 23 aug 2022, so one of my trial kernels
You should put the debian kernel (=3.2.68) in partition 6
As result the kernel module to activate the ethernet port will not be loaded as I have put 3.2.68 modules on p10rootfs
That also explains why why it cannot mount /dev/sda1. This kernel has a problem

So try the debian kernel if that solves this problem

:z)

Of course - it was my fault :doh
Now I've got another bunch of errors - console output.

[fvdw]

Well the fvdw-sl system started :-D
However it seems I have made an error in the file /etc/inc/global_defs.inc in fvdw-sl package.
I will send you an updated package tomorrow
I also will have a look to some other errors.
The good news is these can be solved to my opinion

Sleep well

[fvdw]

a patch file for sda1 partition is sent via pm
unpack archive in root folder (/) of sda1
It should overwrite existing files on sda1

/etc/platform_check.sh (unchanged)
/etc/inc/globals.inc (modified)
/etc/inc/globals_defs.inc (modified)
/etc/init.d/rcS (modified)