auto-mount, Amarok, total system lockups??

[lessgov2007]

I'm experiencing lockups on Jaunty periodically. It's a full freeze, mouse frozen, no keyboard responses, no hard drive activity, and the only way I can get out is to force a shutdown by holding the power button. I've experienced this since the installation, but have not quite figured out what is causing it. Everything is running good aside from the total lockups. It appears to me that it occurs when I have Amarok running, and doing other things such as surfing the net, etc. I checked the log files, nothing out of the ordinary there.

One thing I am thinking... I had my secondary 40GB hard drive auto-mounting at start up, because all my music, videos, documents, etc, are stored on there for the time being. I am thinking it may have something to do with the way I was mounting the hard disk, as Amarok was reading off this drive to read the music collection. I did notice the system was slow to read anything off this drive. So, I took it off auto-mount. It does read the drive a lot faster now. So, I am waiting to see if this cured the lock ups or not.

Here's what I did to auto-mount the hard disk. I created a folder to mount the drive too. I added "/dev/sdb1 /home/haunted/40GB ext4 defaults 0 0" to the fstab. <-- I'm thinking I should have done this differently as it was reading from this drive slowly when mounted this way. Now it's not auto-mounted at all. I have to click the drive after boot-up to have the system mount it, and it reads quickly now. So, perhaps that's the issue? Only time will tell I suppose. If anyone can tell me if I should have done this differently please let me know.

[lessgov2007]

Re: auto-mount, Amarok, total system lockups??

Okay I have solved this one. I had added "/dev/sdb1 /40GB etx4 defaults 0 0" to my fstab to automount a second hard drive of mine. I noticed the system was taking forever to read this disc, which lead me to believe that was causing the instability. It's the second hard disk that contained my music collection that Amarok was trying to access, and something was causing an issue there freezing the entire system up, no mouse, no keyboard, no hdd activity. I removed my automount and have not experienced a freeze since. It's probably just the way I was mounting it, possibly needed to specify something in the fstab differently, but I dunno what. It's not even a concern anymore, because I was merely doing the automount temporarily anyways.

[dibl]

Re: auto-mount, Amarok, total system lockups??

Amarok is a glorious piece of work. However, if you just want to play some music that you have saved on your hard drive, you might want to try alsaplayer -- very simple, and gets the job done.

[flarson]

Re: auto-mount, Amarok, total system lockups??

As long as you do have an ext4 filesystem on that drive that entry should be just fine. You say you had all you multimedia on that drive before installing jaunty? If that is true it is unlikely that the filesystem is ext4, unless you specifically upgraded the filesystem from ext3.

[lessgov2007]

Re: auto-mount, Amarok, total system lockups??

As long as you do have an ext4 filesystem on that drive that entry should be just fine. You say you had all you multimedia on that drive before installing jaunty? If that is true it is unlikely that the filesystem is ext4, unless you specifically upgraded the filesystem from ext3.

It's etx4, I just use it to back things up to, try out distros, etc, etc. I just copied my media stuff to it when I reformatted my main disc to install Kubuntu the other day.

Everything is working now. Just something about using the automount made it read the drive extremely slow. However, if manually mounted it works just fine, so it has something to do with the way I mounted the drive, because the entire system was reading it slowly, not just Amarok.

I have over 2,000 mp3's, have to have fully featured music player. Basic players just don't cut it for me. Amarok is running fine now, no problems. :-)

haunted@haunted-desktop:~$ df -T
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/sda1 ext4 151873632 26816884 117341936 19% /
tmpfs tmpfs 186008 0 186008 0% /lib/init/rw
varrun tmpfs 186008 348 185660 1% /var/run
varlock tmpfs 186008 0 186008 0% /var/lock
udev tmpfs 186008 148 185860 1% /dev
tmpfs tmpfs 186008 12 185996 1% /dev/shm
lrm tmpfs 186008 2392 183616 2% /lib/modules/2.6.28-11-generic/volatile
/dev/sdb1 ext4 38472372 36113028 405040 99% /media/disk

[vinnywright]

Re: auto-mount, Amarok, total system lockups??

first if the dir. you made for the mount was /home/haunted/40Gig then your fstab should have ben

/dev/sdb1 /home/haunted/40Gig ext4 nosuid,user,defaults,rw 0 0

and that would have worked in oler kernels now that wear expekting a UUID insted of a /dev entry I'm not shure but the ...nosuid...may take care of that.

in your second post you sead you added ..........

/dev/sdb1 /40GB ext4 defaults 0 0

to fstab that would inply that your mounting it on /40Gig and thats fine if the folder you made is called 40Gig and on the / root directory NOT in /home/haunted/40Gig like you sead in your first post.
an absolute path is requierd!!

tradishinaley /mnt/ is used for mount points to add drives or filesystems to.

so something like ......../mnt/storege or /mnt/40Gig would be logical.

VINNY