This isn't good. For many reasons, not the least of which is that by not having separate partitions, you're unable to upgrade in the manner I described earlier.i got the entire disk devoted to root. or /. there is no swap space
Having dedicated swap space is a very good idea, regardless of how much RAM you have.as i got 4GB of RAM. i never run out of RAM
Personally, I've run into problems when using ext4, so I'm still using ext3 on all my computers. As usual, YMMV.and while it is running it works well. great, in fact. it is specifically how it tries unmounting the system when shut down. or some feature say maybe APM is preventing auto-fsck to work correctly. i found workarounds but no real fixes. nothing else is wrong with it.
could having the file system set to Ext2 vs Ext4 be a problem? honestly i have never noticed a single difference one way or the other in terms of stability or performance
I don't know. But I do know that if I were you, even though it would be a hassle given how your drive ISN'T partitioned, I'd take the plunge and do a clean reinstall, this time making sure I did it the preferred way. Back up everything important, then wipe the drive and do a clean reinstall, that's what I'd do!for the record, this bug happens on both laptops. one running Kubuntu, (just got done installing it at home), and my STO computer running Ubuntu w/ Kubutu-desktop. both have auto-fsck failures. both won't unmount the root file system properly on shutdown. so the issue is not with one computer. i installed via two different disks too. when i view the kernel output on shutdown (i prefer verbose, it's fun watching it scroll on the screen) it never even mentions unmounting filesystems. not once. it does have a 'fail' flag on some kernel msg daemon but that is it
both have SATA hard drives, perhaps i got them configured for IDE or something?
Upvote
0