Howdy, folks.

I'm using Ubuntu 6.06 LTS Dapper Drake on an Acer 5601AWLMi laptop.

I'm not here because of troubles with getting it to work. It worked fine, until what I did.

Background:

The acer comes with a small recovery partition to reset everything to factory default, a 40 GB windows partition and a 45 GB storage partition. Everything seems to use fat32, so that was all fine and dandy. When installing Ubuntu, I took a 10GB chunk of that 45 GB storage partition and made it into an extended partition with a 1GB swap logical drive and another 9 GB swap logical reiser fs drive (mounted as /).

Linux installed. I got networking, sound, and my blasted printer working. I installed all my favourite software (although I am used to Debian and I found Ubuntu's versions to be slightly older than what I'm used to). And, I found that I didn't have enough space in my /home directory.

As root, I deleted everything in the 35GB vfat partition and also reformatted it to reiserfs. I then copied everything from the /home directory (one user directory) to the newly reformatted drive and changed ownership appropriately. I killed x11 and gdm and all that. From the console I made fstab mount this drive (/dev/hda3 /home notail 0 1). I then rebooted and it worked fine.

I was able to check my email and use amsn et cetera. The only problem now is that after about 2 minutes of usage, the screen freezes; I lose my mouse and keyboard. It hard locks and I have to manually force my poor laptop to shut down. No scans are performed by Ubuntu after that to check the drive.

What should I do? Was I wrong in using "notail" as an option? Keep in mind that I used it because I wanted this drive to mimic what the / partition said to keep congruency.

Any suggestions/ideas are more than welcome and I thank you all ahead of time.

~Dave

Okay. Here's what I did wrong. My fstab line should have looked like:

Next, I forgot to perform an fsck on the drive to make sure there were no errors. Seeing as it crashed, I don't know if it just had the errors or if they came after the crash, but it did have errors nonetheless. I had to reboot into a "recovery mode" (because I'm not keen enough to just kill x again, unmount the drive, and do it all without the special boot). I used:

It told me that it only had one error and I had to use --rebuild-tree to fix it. So, I did:

I changed my fstab and we're home free.

Thanks to you all for reading and/or posting. I always feel like such a n00b whenever I post a question and I do appreciate your help.