zekemx, I know I am
very late to the party, but I just ran into the same problem you had. I also spent about an hour figuring out wtf was going on and I think I know what it is and how to fix it. Mind you most of this is guesswork so don't take any of this as fact, and I also recommend you check all your commands before trying them, your system is different so be sure to update all references to the correct ones. \
First off, the drive shows up when I check dmesg, but it can not be mounted. Manually mounting it may work, but it is always read only, not great.
I opened gparted through the mageia control centre (I'm on Gnome btw). It complains about the partition table being broken, and asks if I am willing to loose it, I say yes, and create a new partition and format it. Still no go.
At this point I figure it has to be something more basic broken, so I fire up good ol' dd and go
- Code: Select all
sudo dd if=/dev/sdc of=/tmp/borked.iso
to dump the entire stick to an iso file (for speed, you can reduce the size should you want to, I had a small stick so it was quick enough to just dump the lot).
With all the data in a file I do
- Code: Select all
od -Ax -tx1 ./borked.iso | less
I compared that with partition table and mbr mentioned in this post
http://www.linuxjournal.com/article/8366?page=0,3 and it is way different, perhaps that's my issue? I figure that since there is nothing on the drive and it doesn't work I've got nothing to loose. So I fire up dd again.
- Code: Select all
sudo dd if=/dev/zero of=/dev/sdc bs=512 count=1001952
this will overwrite your first 512 mb with just null. After that I fire up gparted again and create a partition and format it, now it works! The drive can be removed and when inserted the partition is automatically mounted, just as it should be.
My guess is that you had the drive mounted when you ran the mandriva-seed.sh script? I know I did (didn't realise at the time), and I think this caused the issues. When unmounted the mbr and partition tables were broken beyond (easy)recovery. Nuking them and starting over fixed it for me.