It has probably already happened to you: Creating volume /dev/sda2 failed with error -1008 Did it tell anything useful to you? Maybe if Storage gave you some more info, you could have continued, fix the problem by yourself.
This project has been already discussed during CSM Workshop. Here are some hints: aschnell: The infrastructure is available, just add some hundred messages to getErrorString() in Storage.cc. aschnell: One could of course also use exceptions but that looks like a task for more than a weeks work. mvidner: The method link is Storage::getErrorString. A quick and dirty way would be to simply add the raw identifiers from enum ErrorCodes: case DISKREMOVEPARTITIONINVALIDVOLUME: return "DISKREMOVEPARTITIONINVALIDVOLUME";
Looking for mad skills in:
yast enhancement storage ux usability
This project is part of:
Hack Week 11