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 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's devsd partition table for arenas: > partition name already in use: "part arenas 99518702 597111894" > can't update /dev/sdXX/data's devsd partition table for isect: partition > name already in use: "part isect 597111894 621991554" > can't update /dev/sdXX/data's devsd partition table for swap: partition > name already in use: "part swap 621991554 623040130" > can't update /dev/sdXX/data's devsd partition table for cache: partition > name already in use: "part cache 623040130 625137282" > > the numbers are what's in the partition table +63 > they are the same, no matter if I set sdB0part to these numbers or the > ones from the partition table > > Am 26.03.2013 15:35, schrieb erik quanstrom: >> 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 is no reason to use fdisk >> partitions at all.) >> >>> Where do I set the environment variable? I tried adding >>> sdB0parts='p1 0 38913' >>> to cmdline.txt, but nothing happens. >> >> i misspelled it. it should be "sdB0part". no "s". my bad. >> >> - erik >> > >
