DamnSmallLinuxThis forum is for the discussion of DamnSmallLinux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So here is my new problem, I added a new hard drive, and i can mount it using:
sudo mount -t ext3 /dev/hdf1 /media
and that works fine. I can then cd to /media and see whats in there. But I now want to mount that every time DSLinux boots up. So I added a line in /etc/fstab that looks like this:
/dev/hdf1 /media ext3 auto,users,exec 0 0
And now when I restart my computer I get this "EXT3-fs warning: Maximal mount count reached, running e2fsck is recommended" after it checks /etc/fstab on startup, is there something wrong with the entry I put in fstab? I google "mounting a ext3 file system automatically in /etc/fstab" and read on how to do it, but I think my effort was futile. I also tried a couple different options in fstab, none of which worked.
it seems like you can access the mount, right? if so, it doesn't seem like too much to worry about.
i guess you could unmount it and run fsck on it to see if that makes it happy and stops the message. afaiknew 0 0 in the options tells fsck that the disk doesn't need to be checked, but maybe something else supercedes that. (?)
btw, what is hdf? a raided disk, i guess? i've never heard of hdf, only up to hdd.
yeah, i can still access the mount. i'm not to worried about the the message i get, it's just a warning. the only thing i want to be able to do is have hdf mount up when i boot the computer.
i thought hdf was kind of odd too. my main drive is hde i don't know why. i have hde and hdf on the same ide cable and hde is set as master hdf is slave.
That's kindof odd, admittedly, but perhaps your motherboard also supports SATA which is set to some sort of legacy mode? Does hdf automount properly on boot?
Oh sorry I thought it was working. You could also try this. Change your fstab to the way it was and than edit your bootlocal.sh
In the /opt directory you should find the bootlocal.sh file. Than you can add it like this (using hda3 as my example)
sudo mount /dev/hda3 /mnt/hda3
Save your changes and then set the permissions on the file to allow execution (Open emelfm...highlight filename....righ-click...Properties....Permissions then set the permisions by clicking all the buttons under EXEC). Reboot the machine and see if the partition is mounted. Watch for error messages.
well that worked, thank you very much. i still get the warning (actually i get two of the same warings now) but i figure i'll just run e2fsck on hdf1 and if it works it works if not it's just a warning.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.