> I will
> investigate further...
It turns out that usb boot is more complicated than it needs to be. With
readparts= the partitions are set up automatically, but then they are thrown
away again, I think because partfs is being started more than once. I will
leave it to the original authors to l
> Can I do something in the kernel command line
> to mount it automatically, so I can get my root fileystem from there?
If the command line contains 'readparts= bootargs=local!/dev/sdXX/fossil'
and the kernel is built with partfs and fossil in the bootdir section,
this should work automatically (w
I think that's already partly being done, I found /srv/partfs.sdXX, I
just need to mount that. Can I do something in the kernel command line
to mount it automatically, so I can get my root fileystem from there?
Sorry, I'm still very confused by the whole boot process.
Am 27.03.2013 08:59, schrieb
> Also, the disk still doesn't show up as sdB0 or sdXX or something like
> that in /dev; still only sdU0.0
> Do I have to do something to make sdB0/sdXX appear?
disk/partfs /dev/sdU0.0/data
Also, the disk still doesn't show up as sdB0 or sdXX or something like
that in /dev; still only sdU0.0
Do I have to do something to make sdB0/sdXX appear?
Am 26.03.2013 16:53, schrieb Friedrich Psiorz:
> No I get these errors when booting:
>
> can't update /dev/sdXX/data's devsd partition table f
No I get these errors when booting:
can't update /dev/sdXX/data's devsd partition table for nvram: partition
name already in use: "part nvram 63 64"
can't update /dev/sdXX/data's devsd partition table for fossil:
partition name already in use: "part fossil 64 99518702"
can't update /dev/sdXX/data'
On Tue Mar 26 10:27:02 EDT 2013, f.psi...@gmx.de wrote:
> Hmm, ok, I'm more confused now than before.
sorry. evidently i'm not good at explaining this.
> do I have to put all partitions there? Or just the 'plan9' partition
> that fdisk created?
put all the partitions in. (but remember, there i
Hmm, ok, I'm more confused now than before.
do I have to put all partitions there? Or just the 'plan9' partition
that fdisk created?
Where do I set the environment variable? I tried adding
sdB0parts='p1 0 38913'
to cmdline.txt, but nothing happens.
Am 26.03.2013 14:56, schrieb erik quanstrom:
> On
On Tue Mar 26 09:48:30 EDT 2013, f.psi...@gmx.de wrote:
> I recompiled the kernel as you said, and noticed that it doesn't
> complain about missing partfs during boot anymore; however there is no
> additional sd*, still only sdM0 and sdU0.0, which still doesn't show me
> any partitions.
i'm sorry.
I recompiled the kernel as you said, and noticed that it doesn't
complain about missing partfs during boot anymore; however there is no
additional sd*, still only sdM0 and sdU0.0, which still doesn't show me
any partitions.
Am 26.03.2013 14:07, schrieb erik quanstrom:
> On Tue Mar 26 08:52:50 EDT
On Tue Mar 26 08:52:50 EDT 2013, f.psi...@gmx.de wrote:
> I'm currently trying to set up a usb-hdd as my root filesystem; I found
> out, that I have to use partfs to actually see the partitions I create,
> however they don't show up after the next reboot; i have to use fdisk's
> and prep's w comman
I'm currently trying to set up a usb-hdd as my root filesystem; I found
out, that I have to use partfs to actually see the partitions I create,
however they don't show up after the next reboot; i have to use fdisk's
and prep's w command (without actualy modifying the partition table), to
see the pa
12 matches
Mail list logo
