[opensuse] Root-partition migration ext3 to ext4
Hi Listmates, Using:
OS: Linux 2.6.31.12-0.2-desktop x86_64 System: openSUSE 11.2 (x86_64) KDE: 4.3.5 (KDE 4.3.5) "release 0"
I want to migrate my rootdisk from ext3 to ext4, but after the migration in the startup fsck.ext3 starts and the boot stops. Used partitions; part3 ext3 grub bootdisk (stays at ext3) part5 ext3 / (migrate to ext4) part10 ext4 backupspace Migration process: 1 Boot systemrescuecd ( http://www.sysresccd.org ) 2 mount sda10 backupspace 3 make backup of partition 5 fsarchiver savefs part5.fsa /dev/sda5 4 create fs ext4 and restore fsarchiver restfs part5.fsa id=0,dest=/dev/sda5,mkfs=ext4 5 reboot Til sofar everything is OK. The question, how do I modify the bootprocess so it doesn't an fsck.ext3 but fsck.ext4 Next question are there other dependencies in the bootprocess of the filesystem ? Thanks, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Hans de Faber
Using:
OS: Linux 2.6.31.12-0.2-desktop x86_64 System: openSUSE 11.2 (x86_64) KDE: 4.3.5 (KDE 4.3.5) "release 0"
I want to migrate my rootdisk from ext3 to ext4, but after the migration in the startup fsck.ext3 starts and the boot stops.
Used partitions; part3 ext3 grub bootdisk (stays at ext3) part5 ext3 / (migrate to ext4)
what filesystem does /etc/fstab show for "/", part5 ? -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 20/05/10 15:14, Patrick Shanahan wrote:
* Hans de Faber
[05-20-10 08:54]: Using:
OS: Linux 2.6.31.12-0.2-desktop x86_64 System: openSUSE 11.2 (x86_64) KDE: 4.3.5 (KDE 4.3.5) "release 0"
I want to migrate my rootdisk from ext3 to ext4, but after the migration in the startup fsck.ext3 starts and the boot stops.
Used partitions; part3 ext3 grub bootdisk (stays at ext3) part5 ext3 / (migrate to ext4)
what filesystem does /etc/fstab show for "/", part5 ?
The / partition is not mentioned in /etc/fstab. I think it doesn't solve the problem. Fstab is opened in a later stage of the bootprocess. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-05-20 15:36, Hans de Faber wrote:
On 20/05/10 15:14, Patrick Shanahan wrote:
* Hans de Faber <> [05-20-10 08:54]:
I want to migrate my rootdisk from ext3 to ext4, but after the migration in the startup fsck.ext3 starts and the boot stops.
Used partitions; part3 ext3 grub bootdisk (stays at ext3) part5 ext3 / (migrate to ext4)
what filesystem does /etc/fstab show for "/", part5 ?
The / partition is not mentioned in /etc/fstab.
Impossible.
I think it doesn't solve the problem. Fstab is opened in a later stage of the bootprocess.
Not true. That file is parsed by the script doing the fsck to know what it has to fsck. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkv1gd8ACgkQja8UbcUWM1zEEAD/aJ5ZxC9AodYcA8fROxpJByKk XGExX2euNRumh+vaAcgA/jdEwEb9g4jXLHhjIKUrjKWab+xpIJSzaOkUKYxF+wTo =Bfvu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 20/05/10 20:39, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2010-05-20 15:36, Hans de Faber wrote:
On 20/05/10 15:14, Patrick Shanahan wrote:
* Hans de Faber <> [05-20-10 08:54]:
I want to migrate my rootdisk from ext3 to ext4, but after the migration in the startup fsck.ext3 starts and the boot stops.
Used partitions; part3 ext3 grub bootdisk (stays at ext3) part5 ext3 / (migrate to ext4)
what filesystem does /etc/fstab show for "/", part5 ?
The / partition is not mentioned in /etc/fstab.
Impossible.
I think it doesn't solve the problem. Fstab is opened in a later stage of the bootprocess.
Not true. That file is parsed by the script doing the fsck to know what it has to fsck.
- -- Cheers / Saludos,
I lived since the 11.2 upgrade with no / line in fstab, I thought this was new in 11.2 no problems For this debugging I put the following line in fstab /dev/sda5 / ext4 defaults 1 1 Some more info from my bootconsole. 1 The startup process tries to resume from the swapfile, nothing in so continue 2 the bootprocess does a fsck.ext3 /dev/sda5 "fs clean" 3 the bootprocess does a mount, mount -o rw -t ext3 /dev/sda5 / this ends with the error "wrong fs" Then the startup ends. The question is still the same, where in the startup is mount -t ext3 hard coded ? Thanks, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-05-20 21:41, Hans de Faber wrote:
On 20/05/10 20:39, Carlos E. R. wrote:
what filesystem does /etc/fstab show for "/", part5 ?
The / partition is not mentioned in /etc/fstab.
Impossible.
I think it doesn't solve the problem. Fstab is opened in a later stage of the bootprocess.
Not true. That file is parsed by the script doing the fsck to know what it has to fsck.
I lived since the 11.2 upgrade with no / line in fstab, I thought this was new in 11.2 no problems
I have never seen such a thing. Well... perhaps not.
For this debugging I put the following line in fstab
/dev/sda5 / ext4 defaults 1 1
Some more info from my bootconsole. 1 The startup process tries to resume from the swapfile, nothing in so continue 2 the bootprocess does a fsck.ext3 /dev/sda5 "fs clean" 3 the bootprocess does a mount, mount -o rw -t ext3 /dev/sda5 / this ends with the error "wrong fs" Then the startup ends.
The question is still the same, where in the startup is mount -t ext3 hard coded ?
As far as I know, it is not. Are you sure the /etc/fstab file is correct? Please paste it here, perhaps we can see something. what gives "file -s /dev/sda5"? I have seen a similar symptom in 11.2, when the fstab is not correct: initial mount (ro) works, but later there are problems when mounting rw, when fstab is actually read. In my case, it mounted. It is a reported bug, that 11.2 can start with an incorrect fstab entry for /. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkv1kv0ACgkQja8UbcUWM1wdmAD9HfbBOSc1+S4UyESdQvYXtOzM zxgrrOwAYQRgz9dIieUA/2/q/lvZON6VtDzZpMuX7L1cB/TuoJhSE+FDPX7aGrfJ =pTy4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 20/05/10 21:52, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2010-05-20 21:41, Hans de Faber wrote:
On 20/05/10 20:39, Carlos E. R. wrote:
what filesystem does /etc/fstab show for "/", part5 ?
The / partition is not mentioned in /etc/fstab.
Impossible.
I think it doesn't solve the problem. Fstab is opened in a later stage of the bootprocess.
Not true. That file is parsed by the script doing the fsck to know what it has to fsck.
I lived since the 11.2 upgrade with no / line in fstab, I thought this was new in 11.2 no problems
I have never seen such a thing. Well... perhaps not.
For this debugging I put the following line in fstab
/dev/sda5 / ext4 defaults 1 1
Some more info from my bootconsole. 1 The startup process tries to resume from the swapfile, nothing in so continue 2 the bootprocess does a fsck.ext3 /dev/sda5 "fs clean" 3 the bootprocess does a mount, mount -o rw -t ext3 /dev/sda5 / this ends with the error "wrong fs" Then the startup ends.
The question is still the same, where in the startup is mount -t ext3 hard coded ?
As far as I know, it is not. Are you sure the /etc/fstab file is correct? Please paste it here, perhaps we can see something.
what gives "file -s /dev/sda5"?
I have seen a similar symptom in 11.2, when the fstab is not correct: initial mount (ro) works, but later there are problems when mounting rw, when fstab is actually read. In my case, it mounted.
It is a reported bug, that 11.2 can start with an incorrect fstab entry for /.
Here is the line "/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246JDWS911276-part5 / ext4 defaults 1 1 " But I think I have found the source of the error In the file:///boot/initrd-2.6.31.12-0.2-desktop is hard coded the disk+partition+filesystem. Thus the question is now how to generate a new initrd But thats for tomorrow, thanks,Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-05-20 22:40, Hans de Faber wrote:
Here is the line "/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246JDWS911276-part5 / ext4 defaults 1 1 "
¿No other?
But I think I have found the source of the error In the file:///boot/initrd-2.6.31.12-0.2-desktop is hard coded the disk+partition+filesystem.
How do you know? That is new to me. And I have changed the root filesystem in 11.2 sucessfully. Weird.
Thus the question is now how to generate a new initrd
mkinitrd - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkv1olkACgkQU92UU+smfQV5xgCfYZTe6NKigxlatxaxCrVBqKlb c5cAn3510QxYM1XF13cF27K9MfXrMrgj =2Yjg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2010-05-20 22:40, Hans de Faber wrote:
Here is the line "/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246JDWS911276-part5 / ext4 defaults 1 1 "
¿No other? Not relevant all lines are OK, its a 100% copy of my running ext3 root
On 20/05/10 22:58, Carlos E. R. wrote: partition. Only ext3 is changed in ext4 and part6 in part5
But I think I have found the source of the error In the file:///boot/initrd-2.6.31.12-0.2-desktop is hard coded the disk+partition+filesystem.
How do you know?
Unpack and open the file with okteta
That is new to me. And I have changed the root filesystem in 11.2 sucessfully.
I changed also my rootpartion succesfully, you can override the disk and the partition in grubs menu.lst. But you can't overide the filesystem in grub and thats the problem
Weird.
Thus the question is now how to generate a new initrd
mkinitrd
Yes and how do I put in the new parameters ???? IF I boot the new partition I don't have a complete OS. Goodnight, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 20 May 2010 23:20:27 +0200, Hans de Faber
But you can't overide the filesystem in grub and thats the problem
Of cause you can! Just configure the boot loader in YaST2.
Yes and how do I put in the new parameters ????
Which parameters? mkinitrd normally detects all needed stuff by itself. BTW, could you *please* cut down the quoting to what is really needed? This helps immensely in following the discussions. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-05-21 01:43, Philipp Thomas wrote:
On Thu, 20 May 2010 23:20:27 +0200, Hans de Faber <> wrote:
Which parameters? mkinitrd normally detects all needed stuff by itself.
On a booted system - his does not boot. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkv1y9UACgkQU92UU+smfQWJ8gCfXlSCyB1aUEB9teRYXExTnt1Z Jg0AoI6HKY7X/ojGvQy1sikxREaXprRg =1fF6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 21 May 2010 01:55:01 +0200, "Carlos E. R."
On a booted system - his does not boot.
I said mkinird inspects the running system to detect what needs to be included and done in the initrd that it will create. Things not included when building the initrd will of cause be missing when booting. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-05-21 02:25, Philipp Thomas wrote:
On Fri, 21 May 2010 01:55:01 +0200, "Carlos E. R." <> wrote:
On a booted system - his does not boot.
I said mkinird inspects the running system to detect what needs to be included and done in the initrd that it will create. Things not included when building the initrd will of cause be missing when booting.
Ok, so what can he do solve his problem? The hack I recommended, then, is the only way? - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkv2ETkACgkQja8UbcUWM1x42AD9ENwBNKyl96mSsdt0ypkHM/RM 8m1Y45Uol6cN2u68+zIA/2kjQM/6YvvBpmQoMNEZ/Esjvrv/orVe7oLP1fe67wPN =zszM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2010-05-21 01:43, Philipp Thomas wrote:
On Thu, 20 May 2010 23:20:27 +0200, Hans de Faber <> wrote:
Which parameters? mkinitrd normally detects all needed stuff by itself.
On a booted system - his does not boot.
Hans should be able to boot into rescue, mount the filesystems, chroot and then run mkinitrd. I think he might need to amend /etc/sysconfig/kernel:INITRD_MODULES. -- Per Jessen, Zürich (10.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 21/05/10 07:55, Per Jessen wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2010-05-21 01:43, Philipp Thomas wrote:
On Thu, 20 May 2010 23:20:27 +0200, Hans de Faber <> wrote:
Which parameters? mkinitrd normally detects all needed stuff by itself.
On a booted system - his does not boot.
Hans should be able to boot into rescue, mount the filesystems, chroot and then run mkinitrd. I think he might need to amend /etc/sysconfig/kernel:INITRD_MODULES.
Good morning I am online again. I think this is the right way to go. Is there somewhere a example how to do this ? Another way I think is: Do a new install, os on ext4, extract the initrd, restore the backup and insert the new initrd. It looks to me an easy but longer way . . Linux (opensuse) is a very flexible OS you can put everything were you want and changing is easy. Grub is also very flexible you can boot always and everything. Except for the hardcoded data in initrd this kills the flexibility. This construction looks to me like the sentence "Every color is beautifull if it is black" Thanks, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hans de Faber wrote:
Hans should be able to boot into rescue, mount the filesystems, chroot and then run mkinitrd. I think he might need to amend /etc/sysconfig/kernel:INITRD_MODULES.
Good morning I am online again. I think this is the right way to go. Is there somewhere a example how to do this ?
Probably, but it's not too difficult - boot a rescue system run fsck on the filesystems you need (root,boot,usr,whatever) mount root on /mnt mount boot on /mnt/boot mount usr on /mnt/usr mount var on /mnt/var (you get the idea). mount -o bind /proc /mnt/proc mount -o bind /dev /mnt/dev mount -o bind /sys /mnt/sys chroot /mnt make sure that /etc/sysconfig/kernel:INITRD_MODULES contains 'ext4' run mkinitrd update your bootloader (e.g. run lilo) exit from chroot umount /mnt/proc /mnt/dev /mnt/sys umount /mnt/usr /mnt/boot /mnt/var /mnt reboot
Linux (opensuse) is a very flexible OS you can put everything were you want and changing is easy. Grub is also very flexible you can boot always and everything. Except for the hardcoded data in initrd this kills the flexibility.
This construction looks to me like the sentence "Every color is beautifull if it is black"
No, there is nothing wrong with the initrd - changing your root filesystem is not a minor change, it's not realistic to expect it to 'just work'. -- Per Jessen, Zürich (11.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 21/05/10 09:39, Per Jessen wrote:
Hans de Faber wrote:
Hans should be able to boot into rescue, mount the filesystems, chroot and then run mkinitrd. I think he might need to amend /etc/sysconfig/kernel:INITRD_MODULES.
Good morning I am online again. I think this is the right way to go. Is there somewhere a example how to do this ?
Probably, but it's not too difficult -
boot a rescue system run fsck on the filesystems you need (root,boot,usr,whatever) mount root on /mnt mount boot on /mnt/boot mount usr on /mnt/usr mount var on /mnt/var (you get the idea). mount -o bind /proc /mnt/proc mount -o bind /dev /mnt/dev mount -o bind /sys /mnt/sys chroot /mnt make sure that /etc/sysconfig/kernel:INITRD_MODULES contains 'ext4' run mkinitrd update your bootloader (e.g. run lilo) exit from chroot umount /mnt/proc /mnt/dev /mnt/sys umount /mnt/usr /mnt/boot /mnt/var /mnt reboot
Linux (opensuse) is a very flexible OS you can put everything were you want and changing is easy. Grub is also very flexible you can boot always and everything. Except for the hardcoded data in initrd this kills the flexibility.
This construction looks to me like the sentence "Every color is beautifull if it is black"
No, there is nothing wrong with the initrd - changing your root filesystem is not a minor change, it's not realistic to expect it to 'just work'.
This was the last step in the process. Without any problem I can now boot my ext4 root. I don't do this everyday but it was easyer than I thought. Thanks to everybody. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-05-20 23:20, Hans de Faber wrote:
Here is the line "/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246JDWS911276-part5 / ext4 defaults 1 1 "
¿No other? Not relevant all lines are OK, its a 100% copy of my running ext3 root partition. Only ext3 is changed in ext4 and part6 in part5
You haven't copied the output of the file -s command I suggested.
But I think I have found the source of the error In the file:///boot/initrd-2.6.31.12-0.2-desktop is hard coded the disk+partition+filesystem.
How do you know?
Unpack and open the file with okteta
Mmmm.... That's just an hex editor. Instead: cp /boot/initrd /tmp/initrd.cpio.gz gunzip /tmp/initrd.cpio.gz then you can view /tmp/initrd/cpio with mc, for instance, or expand it into a tree. The configuration appears to be in /tmp/initrdtree/config/, moun.sh and storage.sh, and a few more, perhaps.
That is new to me. And I have changed the root filesystem in 11.2 sucessfully.
I changed also my rootpartion succesfully, you can override the disk and the partition in grubs menu.lst. But you can't overide the filesystem in grub and thats the problem
You may be right. Bug 577798 - mounts a reiserfs partition and reports ext3. I hadn't realized the implications. My memory remembered the incident incorrectly. It booted correctly because my initrd was correct and matched the filesystem.
Weird.
Thus the question is now how to generate a new initrd
mkinitrd
Yes and how do I put in the new parameters ???? IF I boot the new partition I don't have a complete OS.
The tool is probably "mkinitrd_setup", and I think it uses "mkinitrd.config" as a config file (saved in the cpio). In my case, it contains one line: - -k /boot/vmlinuz-2.6.31.12-0.2-desktop -i /boot/initrd-2.6.31.12-0.2-desktop The script has this syntax: usage: mkinitrd_setup [-s|--scriptdir <scriptdir>] [-i|--installdir <installdir>] [-d|--debug] [-o|--offset <offset>] [-h|--help] Install mkinitrd scripts. Options are: -s|--scriptdir Install initrd scripts from dir <scriptdir> -i|--installdir Install initrd scripts in dir <installdir> -d|--debug Enable debug output -o|--offset Use <offset> between script numbers. But the files given to -k or -i are not configuration files. Things do not add up.... You might expand the cpio tree, manually replace "ext3" with "ext4" on all files with a text editor, manually recreate the "initrd.cpio.gz" archive from the tree, and replace the original initrd archive with it. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkv1zKkACgkQU92UU+smfQUSRACfS3mtXPuXC0wtjk1wIad/3bq7 KhEAoIzUPMWVLgaY0e0NZGQ2wtdp+UYm =5uUv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hans de Faber wrote:
Hi Listmates,
Using:
OS: Linux 2.6.31.12-0.2-desktop x86_64 System: openSUSE 11.2 (x86_64) KDE: 4.3.5 (KDE 4.3.5) "release 0"
I want to migrate my rootdisk from ext3 to ext4, but after the migration in the startup fsck.ext3 starts and the boot stops.
This is before the root filesystem is mounted? -- Per Jessen, Zürich (11.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R.
-
Hans de Faber
-
Patrick Shanahan
-
Per Jessen
-
Philipp Thomas