Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
During Boot Time Screen reports /home has no ext3 barrier. I formated each partition during the Slackware Install Process. The labels are as they should be.
Question is can I just format /home, it's a clean partition, haven't tried to run kde desktop for the new user, caught the missing extension format during post install configuration as root . Redoing this slackware64-13.37 install would just take too much time on top of the days I've already spent for neighbor's ThinkPad.
Has anyone had this happen to them? Can someone tell me how they fixed it? Thanks
If you have never used that filesystem and there is no important data on it you may try mkfs, but I think the user's home dir(s) should have been created (but probably the installation was unable to do that).
#dmesg | less
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda5): mounted filesystem with ordered data mode
The above output displays for sda1, sda2, [sda3 does not appear mounted during boot], sda4 Extended<sda5, sda6, sda7
Can anyone explain what is wrong & what to do exactly for sda3 /home partition? Can I run setup to just get /home ... or will that wipe out the rest of the install??? I only did adduser but have not tried to open /home for fear of what it will do? Thanks
How long should it take for 90G /home to format with mkfs ? How do I know the program is not stuck?
Did the following trying to figure out howto get /dev/sda3 -> /home to reflect ext3 in /etc/fstab. I used ext3 thinking it would be more stable than ext4 was it a mistake? Thinking that before all the auto configuration of install setups. So there must be a manual way to fix the missing ext3 FS. Conceptually it seems a simple fix but I looking to learn the technical specifics. Do I unmount /dev/sda3, then mkfs ext3 , & then mount /dev/sda3?
"df" tells you what filesystem[s] is/are mounted - if you want to see everything try "mount". Not a lot of reason to use that in this case.
If /dev/sda3 isn't mounted you can't umount it.
Try adding the filesystem type to fstab - "parted -l /dev/sda" as root will tell you that.
*Edit:* be aware that this will overlay mount the /home you have already setup - all your users (except root) will effectively disappear. Better (from single user mode) to mount /dev/sda3 somewhere else and copy the current /home (including hidden files) to where you mount /dev/sda3. Then umount /dev/sda3, fix fstab and reboot.
Should all work.
by default disabled on ext3 and enabled on ext4. Further more someone said :
It is only an info-level message. IIRC write barriers are disabled by default on EXT3 (but are enabled on EXT4) and this message shows up during boot time on recent kernels. If either your PC is plugged on an UPS or runs on battery like a laptop, write barriers are quite useless.
Found on Linux Mint Forum 6/12... I'm working on ThinkPad
So /dev/sda5 is suposed to be /
/dev/sda3 " " " " /home Linux or 83 but no ext3 format.
So home is not mounted. Correct? I under how to goto runlevel 1. Don't understand,
will overlay mount the /home you have already setup
I just added one user and don't care if it disappears, I can just add the user again. What do you mean by overlay the /home I already setup, apparently its not setup.
Thought I would just see a list like when I fdisk -l
syg00 I am communicating on my laptop.. so I just copy the output from the ThinkPad... I'm working in root and am in runlevel1.
Didier Spaier, during install I chose /dev/sda3 for home and slow format- but its 90GB and I could not see the progress of format and I think it didn't work. Plus I used a DVD disk they spin too fast. Think Install failed to format ext3. Thank you so much. So I do this in runlevel1 as root and do I have to mount /dev/sda3 first?
Don't think /dev/sda3 is mounted is mounted?
#df -hT - lists everything correctly Except It does not list /dev/sda3