[...] > Logs attached, still no good. > Ok, fine, at least the commands are getting executed again. One basic question: has this system + this configuration ever worked with setup-storage? If yes, any clue which version that was. Although there is no archive of experimental versions its possible to reproduce an earlier state by building from an SVN revision of choice.
> I have to take a break for an hour, it takes that long to commute. It's also > late there. shall we resume tomorrow? > > > I don't really know how long I'll stay awake myself, but at least I'll give you more things to try which you can do whenever you get to it: - add some exit 1; to usr/sbin/setup-storage in the first lines to make it abort right away to get setup-storage out of the game. - manually execute the following commands in the shell: parted -s /dev/sdb mklabel msdos parted -s /dev/sdb mkpart primary "" 32256B 134249471B parted -s /dev/sdb mkpart extended "" 134249472B 60022480895B parted -s /dev/sdb mkpart logical "" 134249984B 2281724927B If the last command triggers the well-known errors message "Error informing the kernel about modifications to partition /dev/sdb5 -- Device or resource busy." then it's nothing got to do with setup-storage (although this might still mean that we have to find a way to work around this inside setup-storage). If it does *not* trigger that error message, move the exit 1; that you added before further to the end of usr/sbin/setup-storage, reboot, retry. I'd suggest binary search - try one of the first lines, then one of the last lines, then in the middle, ... Thereby, if it's setup-storage's fault, we should be able to nail down which command is causing the trouble. Thanks a lot for your efforts, Michael
pgpLr9jnfxtBQ.pgp
Description: PGP signature
