Greg Freemyer wrote:
IIRC, if you change the partition setup outside of yast, it gets confused and won't allow you to "modify" the partition setup.
I haven't changed the setup outside of yast. I did set up the original config using gparted under ubuntu (why can't I find gparted in the opensuse repositories?). But yast partitioner didn't complain when I first ran it. Only when it tried to change things.
My assumption is that the yast-partitioner keeps config info somewhere and it compares that to the actual partition table.
If they disagree you get the message your seeing.
So your choice is to continue maintaining your partition setup outside of yast, or let yast blow away the current setup and start from scratch.
Assuming your using a traditional partition table, you can also manually blow it away with:
dd if=/dev/zero of=/dev/sdf count=1
Then force the kernel to re-read the partition table. I don't recall how, so I just reboot.
The machine is doing more important things with most of its resources and that will take a week or so, so a reboot is not an option for now. A quick google turned up partprobe but when I run it :( # partprobe /dev/sdf Error: Error informing the kernel about modifications to partition /dev/sdf3 -- Device or resource busy. This means Linux won't know about any changes you made to /dev/sdf3 until you reboot -- so you shouldn't mount it or use it in any way before rebooting. Error: Failed to add partition 3 (Device or resource busy) Warning: The kernel was unable to re-read the partition table on /dev/sdf (Device or resource busy). This means Linux won't know anything about the modifications you made until you reboot. You should reboot your computer before doing anything with /dev/sdf. I don't understand how /dev/sdf3 can be busy. (a) It has never been used. (b) there isn't actually an entry in the file system called /dev/sdf3 (there's just sdf, sdf1 & sdf2) ! Is it sensible to try the dd command and then repeat the partprobe? Another option I have is to remove the disk (it's SATA in a hot swap cage). I could then put it back in the same bay or in a different bay (which I think would make it appear as /dev/sdh since there's already a /dev/sdg). Would that enable the kernel and/or partitioner to untangle their kni*kers? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org