OK,but it is going to be in the morning, though, when I try, I just finished this "history", my hand has a cramp, from all the typeing!
It is pretty long, and may still be a little hard to follow, I did not check the spelling, etc to well (sorry),..but at the end, at least I realize what I did to cause this, and won't ever do that again,!!! Don't know if we can fix it or not, maybe,..but am pretty sure I do know, how to be sure it dose not happen again. here is the history:
History , OB HDD (Samsung portable USB HD 300 gb)
When I made my decision to no longer use windows, and install Linux Mint 10, on the computer, as the main OS, at that time, I had Linux installed along side windows xp, had been this way several months, as being a new user of Linux, that was how I installed it the first time, sort of a "trial" period.
Since I liked it so much, I decided, I no longer had any reason to keep windows, and "wipe the HD and to re-install, Linux,as my main OS.
So any way, before I did that, I installed Linux Mint 10, to the Samsung,(OB HDD), for a short period of time, used it, everything seemed to work pretty well. I had insatlled some other pachages, software, done some testing and it worked well.
So I copied, all the files that I had on the 1st Linux installation, IE: my home dir,desk top, photos, music,etc,.put them all a folder,in the Samsung. The windows junk I was not to concerned with, but I did make a Zipped package,with every thing that I had on My documents, mostly cause I had a lot of text files, some html, and .bas files, going back as far as 2 or 3 years, occasionally, I need to look through them, for something, anyway,... So I had everything pretty well saved or backed up, but as files I could copy, after the new Linux install, not a "backup" in the sense of a entire system back up that can be re-intalled, just copied files.
OK, so I successfully wipe the HD, install Linux Mint, everything went fine. I got all the files I wanted copied back to my new home,desk top,etc. Intalled the packages I use , etc.
I am doing some work with Freedos, and still had not used the newest freedos 1.1 that came out recently, other then a little usng virtual box, and was eager to set up a dos partition, install freedos1.1, and start doing some things with that.
So, knowing that I can not resize the partition, while it is mounted, I installed, KDE partition Manager, and also Gpart,to the samsung OB HDD, (USB device), at this time it was working fine, and booted well, etc. So booting with the Samsung, I successfully resized the HD (LINUX partition, ) on this computer, created another primary partition for dos, aprox 2.7 gb, more the enough space. Sucessfully installed Freedos, and updated grub,.. everything seems to be fine so far.
At this point, when I updated grub, I did that with the samsung also attached, and mounted, ..so my "boot menu " was, like this when I first turn on the computer,
1 Linux Mint..
2 Linux Mint recovery mode
3 The memory test option,
4 another memory test option,
5 fredos partition..
6. Linux Mint, on the OB HDD (the Samsung)
7 Recovery mode for Linux Mint on the Samsung,..
It dose not read exactly like I wrote it, but basicly that is it. Every item booted, and ran as it should, with no problems.
OK, In order to get the freedos, and the Samsung into the boot menu, I ran update-grub, after booting the main computer, and they were added to the menu like they should be.
So, later, I decided to do the same thing with my lap top, a ACER Aspire 1 series,..I can give more details on that, but don't think it matters to much.
The same every thing went fine, in the Linux install, the laptop is running fine, with Linux Mint,..
I have not yet tried installing freedos to it, because this "problem" with the samsung came up, and it "side tracked me",..
I had copied some files , from the samsung, to the laptop HD, but because of the permissions thing I was haveing some trouble, or it was kind of "cumbersome", haveing to open every thing as admin,don't remember very well, exactly why, but it occured to me, that it would be better, to run update-grub, and get the Samsung/linux, system into the boot menu,
part of my thoughts were to be able to do the same, resize the partition, and set up the freedos partition,..and I wanted to do that before, I got to many files,etc, installed,..just in case if anything went wrong, I would not have very much on it yet, and it would be easy to start over.
When I ran update-grub, with the samsung attached. So anyway, I did update grub, and it seemed to have updated ok, I had the Samsung in the boot menu, and it would boot ok,..
It seems to me, but now I am have some trouble remembering,
I had selected, to boot with the Samsung,
it booted fine, and then from the terminal, of the now active, mounted Samsung, (Linux Mint 10 also),
XXXXX I ran update-grub, and thinking on it, I can not imagen why, or what made me think I needed to do that, so I think that is my "fatal" error. XXXXX
It was at that point, everything sort of "locked up", the terminal "hung", never executing the update grub,.. I was unable to get the prompt, back, in the terminal, so I closed the window (fatal error #2 !!??),..I did get the warning, that there was a unfnished process, going,..but chose to ignore it, after waiting sometime, maybe half a hour, for it to finish, and it didn't,..there was no sign of activity anywhere, on the laptop, or the Samsung,... So after I closed the window,
I found I could not "safely remove" the drive,( Samsung).. and when I unicorns down from the menu, the laptop did not comletely shut down, like it should normal,..it "hung" on the closeing screen, with the Linux logo in the middle,..so I shut it off manually. I disconnected the Samsung, and re-booted, the laptop , the laptop booted fine, and was un affected,.. however from this point on, the Samsung with Linux, has been stuck in this, "frozen" state,..unreadable,acessable, saying it is not mounted, but it is, etc,... I suspect it is still "stuck" trying to update grub, that that is the meaning of this :
fsck.ext4: Device or resource busy while trying to open /dev/sdc1
Filesystem mounted or opened exclusively by another program?
So any way I am glad I took the time, to write this, if nothing else, I now know I should not have tried doing that, running upadte-grub, from the device, when it alread had been updated, in the main systems, boot menu,..and this is what comes up, when the machine is first turned on, I know what I was thinking, now, but that isn't really important, it was because, the Samsung,with linux, would not boot by itself, I had to boot with the system first, then add the samsung to the boot menu, once added to the menu, it would boot fine, and run with Mint. If I disconnected, the 0 HD ( in my bios), and placed the 1 HD (being the Samsung) at the top, as the first one to boot, it won't boot by its self, ( this is on the big computer ,IBM), on the laptop, similar, but it offers a selection, if you hit f12, the menu says, 1 boot with hd, 2 boot with usb,(samsung blablabla), 3. Network boot,(never did work),...
But the same if I tried booting with USB, it would not, it had to be added to the grub boot menu. I was trying to change that, and I "broke" it, don't know if it can be fixed, any other way then a complete format,..But now I know it was not just a "accident",.. I should not have tried to update-grub, from it, it never occired to me this would happen, maybe it shouldn't have, if it is a "bug" of sorts,..in a way it is, because I thought, the worse the would happen is I would get some kind "error, can not update grub", and be able to cancel, ...???..
Hope you can follow this, I am going to post it, sorry about the spelling and it is late, Probaly tommorow, I can edit for the spellinh, but I am to tired now. It is a long drawn out ,"history",...But this is something I also try to teach my son, "don't do so many things, so fast, and then when the computer "locks up", and nothing works, you can not remember, what all it is that you did",.. if it breaks, the only way to repair it is if you can go back step by step, and review what you did, then you might figure out what you did to "break" it, but at least know not to to that again.
quote] 1.Boot from the live disc.
2.Plug in the OB HDD.
4.Immediately reboot the computer.
5.Try to run the fsck command as before. (making sure like you did before to use the correct partition and no mounting)
[/quote] Is what worked.
Thanks for all your time on this,..