Slackware :: File System And Mounted Point Information Log During Boot?
Jul 25, 2011I want to make sure that all my file systems and mounted points are OK during boot time. Which log file in Slackware shows such info?
View 3 RepliesI want to make sure that all my file systems and mounted points are OK during boot time. Which log file in Slackware shows such info?
View 3 RepliesI am using Gentoo Linux and for a while now, the root file system is mounted read-only on booting. For obvious reasons, this is quite annoying as most services do not start up correctly (I do not use a separate file system for /var). After the system is up, I have to log in, remount the root file system read-write, fix /etc/mtab, mount all other file systems in from /etc/fstab and then start up all the missing daemons. I know that there are ways to make a system run properly with a read-only file system, but I would rather restore the old behaviour of a writable root file system.
The strange thing is that after running mount / -o remount,rw, the file system is mounted in writable mode without any errors. I suspected some problem with fsck, but now I have disabled automatic file system checks on the partition (tune2fs -c0 -i0).When I run dmesg, only these lines mention the partition at all, although I am not sure if not something gets lost because /var/log is not writable:
EXT3-fs (sda5): mounted filesystem with writeback data mode</code>
EXT3-fs (sda5): using internal journal
The line in /etc/fstab looks like this:
[code]....
I have an ntfs partition that I wish to access as a normal user(non-root). For this I did the following. As root I created a folder /windows and did a chmod 777 -R on /windows. Then I added the following line to /etc/fstab
Code:
/dev/sda3 /windows ntfs-3g defaults,nosuid,nodev,umask=000 1 0
Now, the partition is mounted alright but the problem is that when any other user (non-root) creates a files in /windows (say by executing touch newfile) the newly created file has the owner and group set as root. The non-root user can create the file and he can also delete the file, however, he cannot change the permissions of the file and also the owner:group is always set as root:root. How do I get across this problem, i.e. how do I mount a partition, so that a non-root user can also change the permissions and ownerships of the files he creates.
Fsck is not check any file system which are not root file system at boot time.
Normally it run: /sbin/fsck -A -R -C -a
But this command doesn't do anything.
I've tried to strace it, and looks like this:
Code:
Under my 'Places' in my file manager, I have a '21 GB file system' How can I
1. Have that 21 GB auto mounted every time I login? I now need to right click and select 'mount'?
2. Give it a name so that it won't call 'a9f28af4-71db-4e49-8c05-f652bf808cc1/' under my directory '/media/'?
A non techie friend has helped an even less techie friend by contacting me by email to discuss an ailing laptop. A few emails were exchanged, with more details, and it was not looking good because it seemed that suddenly the CD drive was not responding, nor any USB devices, the wireless icon was gone, but Ubuntu still seemed to work (for now), with wired ethernet also working. I was struggling to think of what could be done, with the favourite routes of Live CD and Live USB apparently gone.
After a few more hours - another email: 'It's now working! After so many reboots it checked disc for errors and repaired itself! Is there some way of doing that when needed anyway?'I see there is 'Disk Utility', and this would presumably fit the bill, but how does it do checks and repair when the damaged file system is being run, and is currently *mounted*? I thought utilities like fsck(?) could only be run on unmounted file systems? Have I misunderstood the disk utility fs check repair function? And anyway, what might be a good answer to my (nontechie) friend's question 'After so many reboots it checked disc for errors and repaired itself! Is there some way of doing that when needed anyway?'
For the record: (quote) It is a toshiba EA60-155 Model number PSA67E-00300C8J. He put in extra ram to install ubuntu. He thinks he may have deleted something! There is a 'trash' file on his USB drive with loads of stuff in it and he doesn't know how or why but because it won't now read the drive on her laptop we cant replace it! (end quote)
I have two servers, 82 and 70.My exports file on 82 reads /...70(rw)on 70 I have a mountpoint called mnt_for_82I execute on 70mount -t nfs -o rw ...82:/ mnt_for_82I go to server 70 and indeed can read and travers the mounted subdirectories. However, I try to create a file or subdirectory under the mount point on 70 and I get a *Permission Denied* error.I'm sure there is a simple explanation for this issue as well as a correct nomenclature for what I'm trying to do in nfs
View 4 Replies View RelatedI have just been gifted with a Linux dedicated server for the next six months, with an option to renew after that time has expired, and I'd like to set it up for FTP/P2P use. I do have some familiarity with Fedora from work, but only as a pre-installed desktop OS. The company providing the server has asked me to choose a OS, so of course I picked the one with which I already have some knowledge. They've also asked me to provide partition and mount point information, and it's here that I'm having some problems. I've spent most of my free time today reading everything I could about partitioning for a server, and I'm still not comfortable making this decision on my own.
The server comes with two drives - one 500GB and one 1TB, and 8GB RAM. My thinking is to use the 500GB drive for the OS, and the 1TB for media storage. I know I still have a good bit of learning to do, but I just want to get the blasted thing set up so I can get on with the hands-on part of figuring out how it works.
I just found that I could perform write operation using a normal user account to a file system I mounted with the commands as followed:
sudo mount -t ntfs /dev/sda1 /mnt/disk/
This is the corresponding entry in the output of "mount" command:
/dev/sda1 on /mnt/disk type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
As far as I remember, when using a normal user account, I had to use "sudo" to perform any write operations (mkdir, rm, etc) to a device mounted using "sudo". But now it seems to be changed.
Do I remember wrong, or did Karmic have any updates change this setting? (I never manually changed user settings, except that I added a root user, but I never used it.)
OS: Karmic(up2dated)
Kernel: Linux stephen-laptop 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009 i686 GNU/Linux
I need to know particular mount point mounted or not before send data to that mount point.Are there any commandsi used this command. mount -t nfs 172.16.102.50:/root/ESSR_share /root/shared_storage/pc50 -o rw,hard,intr but it take long time (when machine(172.16.102.50) is not available)
View 4 Replies View Related10.04 LTS: Is there a way to hide an icon of a mounted file system from the GNOME desktop?
View 8 Replies View RelatedI'm running an Acer Aspire 1830T-3721 dual-booting Windows 7 with Ubuntu 10.10 (Desktop).
Background: So first I dropped my laptop a couple feet while Windows was running. The laptop immediately shut off and then tried to boot. Booting Windows results in an unfortunate "Windows has encountered a problem communicating with a device connected to your computer. The error can be caused by ... faulty hardware ... Status: Oxc00000e9 Info: An unexpected I/O error has occurred." But Ubuntu booted fine, and could access my NTFS files fine, so I was trying to work on the problem from there. I try a few utilities, looking at the partition table, etc without actually applying any changes.
Then I run a fsck on the drive. It loudly warns me that if I continue on a mounted drive, then I'm going to mess things up. In a moment of stupidity I push on, thinking that surely it would ask me for more configuration, or confirmation, before actually starting. The fsck runs for about 1 second before I Ctrl-C it, running some preliminary stuff and then just starting pass 1.
After this, Ubuntu won't boot anymore. Instead, it hangs just after the init-bottom script runs. If I boot with init=/bin/bash, I can get to a shell, and see that my file system is still there, but not sure what else to do.
I've been running off of a SysRescCD LiveCD, from which I've looked at the drive with testdisk. Testdisk reports that "the hard disk seems too small" while showing me the partition table.
I ran a fsck on the Linux partition; it fixed a bunch of things. There has been no apparent effect on the boot behavior.
I can access all my files, back them up, and reinstall Ubuntu, but I'm hoping there's a better solution, perhaps one that will also help me repair my Windows installation (but I'm looking at one problem at a time here).
I have mounted a iomega file system on a cetos os machine using
mount.cifs //filserver-ip/directory /home/my-home/mounted-file -o
user=username
(** mounted as root) The mounting works fine.
The problem arises when I try to create a sub-directory inside the mounted directory. All the newly created sub directories become write protected.
I am accessing this file system from R software and it needs to write/create directories in side this mounted directory.
how can newly created sub-directories will become automatically writable, so that R can create new sub-directories and write data inside those directories.
I have an NTFS file system nfs-automounted on our RedHat servers. Users can read and write to the file system no problem, and can create new files, edit them, and delete them to their heart's content. The only issue is that utilities such as "dos2unix" cannot create temporary working files:
$ dos2unix events.0818.dat
dos2unix: converting file events.0818.dat to UNIX format ...
Failed to open output temp file: Operation not permitted
dos2unix: problems converting file events.0818.dat
This isn't limited to "dos2unix"; any other utility that creates a temporary working file gets the same problem. If I copy the file to a local file system like /tmp, it works fine. Here's the kicker: this works fine on Solaris systems. I can take the "dos2unix" utility over to a Solaris system that has that exact same NTFS file system automounted via NFS, and it works. No issues creating temporary working files at all.
I am running the latest suse release downloaded directly from their website. I ran the installation after buring the dvd and everything seemed to be working fine. after the installation i ran updates and used it for a little bit. When i shut it down that night and went to restart it I got an error that stated the OS wasnt there. I then went through the installation and everything and it retained the information from the installation before (web history etc.) but for some reason every time I reboot or shut it down the system is not able to read the startup information from the hard drive and will not come on without me re installing it.
View 9 Replies View RelatedSo 2 days ago everything was all fine on my machine. Has been for about a month, but all of a sudden as of yesterday I have no sound, I am seeing IRQ interupts on boot, During boot I am seeing file system is not clean, , and swap space is being used for the first time while doing normal task, etc. These are 2 new hard drives in RAID 1 with ReiserFS. I should have used a newer FS but thats a whole other argument.
Anyways here we go.
The system is Debian Lenny amd64
Physical RAM 4GB + 6GB swap
/var/log/messages
Code:
Feb 21 07:35:09 Sarah kernel: imklog 3.18.6, log source = /proc/kmsg started.
Feb 21 07:35:09 Sarah rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="3994" x-info="http://www.rsyslog.com"] restart
code....
my partitioning layout was as follows
Vista Recovery
Windows 7
GRUB
Extended
-->Fedora 12 (ext4)
so, I shrunk my recovery in Windows 7 successfully, and booted into my Fedora 12 live cd to run Gparted, and move the partitions so that the free space could go towards fedora, I did such, and then I couldn't expand the partition to my dismay. Next, I woke up this morning, tried to boot to fedora to run SSH, grub loaded, but when I tried to boot fedora, I got the "File system check failed" error, and when I tried 7, it just went to a blank screen with a single "_" in the top left-hand corner.
I would like to know if there is a way to do an unattended check on the root file system on my servers, *and* send emails in case of errors.
I know you can schedule a root file system fsck during boot time - but the root file system will be mounted read-only - so if fsck finds any problems - it can't email away a warning, or write the result to a file - or can it?
Essentially I would like my servers to do a self-check of the root file system periodically - and to email me if it fails. I just can't think of a way to get it done.
I was updating slackware-current via slackpkg and while it was downloading/installing latest kernel (and other apps) my battery went off and now the system can't boot. I was thinking to boot through a live cd and through chroot command to re-install all the new packages. Would it work?
View 6 Replies View RelatedI decided to use my old computer for torrent downloads and perhaps for mirroring the slack -current. However, the computer is rather weak: Celeron 1,2Ghz, 256 MB RAM. So, which slack release is better to use? I aim to use the jfs file system, but I'm not sure it is good choice.
View 4 Replies View RelatedI need to enlarge the root file system on a Slackware 13.0 32-bit system; it's in a simple logical partition (/dev/sda6) -- no LVM, mirroring etc. This might be a good opportunity to change from ext4 to jfs, too.Routine procedure, no? No!First off I booted Knoppix 5.31 but found it doesn't have ext4 support (no efs2ck and running fsck results in "fsck.ext4: not found").So I booted Slackware 13.0 32-bit CD-1 only to get the same as with Knoppix.I do have a GParted-liveCD 0.3.4-11 but have had mixed experiences with it so am reluctant, despite having backups.
View 11 Replies View RelatedI start playing with Slackware and I am amazed about its endless possibilities. There is a security advisory for Firefox and 4.0.1 must be installed. Do I need to compile my own FF 4.0.1 build? Or, instead of inventing the wheel, could Slackware's Firefox 4.0.1 package be pulled from somewhere? if my question sounds naive, just trying to get to the point and catch up with security issues.
View 14 Replies View RelatedWhilst my office is decorated I have to move my computer. To make this as easy as possible I have setup my first ever wifi. An access point (wired to adsl router). It is working by using wicd and I am wireless at the moment. What security should I put in place (wicd says unsecured). I am probably quite safe as the nearest road or house is 200m away but I would like to learn what I need to do as this is the first time in over 20 years of computing that I have gone wireless.
View 8 Replies View RelatedI've recently had my file system irrecoverably corrupted after a hard lock-up. This has happened to me before, a couple weeks ago, and both times I've had to reinstall. I don't know what is causing the lock-ups (possibly the binary nvidia driver..), but I would like my file system to be intact or at least recoverable next time it happens.What is the "safest" way to mount things?
I'll be using ext3 with data=journal, but I've read that disk write caching combined with a kernel crash or power loss can still screw things up. Supposedly, mounting with barrier=1 helps some, but doesn't work with LVM? Would it be wise to turn off disk write caching completely? I understand there's a performance penalty, but if it helps keep the file system consistent in case of disaster.
I've just installed Slack 13.1, this was a "clean" install. All seems to be working well except for the dvd-rw, but this is a show stopper, if it doesn't get resolved in a few days I'll have to go back to 13.0.
The drive is detected correctly, but if a cd is mounted it gets errors, and is unable to set it up (it doesn't appear on the desktop).
Here is the info from dmesg:
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: ATAPI: TSSTcorp CDDVDW SH-S223Q, SB03, max UDMA/100
ata3.00: configured for UDMA/100
scsi 2:0:0:0: CD-ROM TSSTcorp CDDVDW SH-S223Q SB03 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[Code].....
As I know, lly includes a control file. Takelibfreetype6_2.3.9-5ubuntu0.4_i386.deb for example, its control file includes the following content:
Package: libfreetype6
Source: freetype
Version: 2.3.9-5ubuntu0.4
[code]...
2nd and 3rd might be linux kernel problems but may help someone else so I included here.1st -- run level 4, /etc/rc.d/rc.4 and xdm -nodaemonJust installed 13.1 on an odd system, including building a new kernel.One thing I do is have the system boot to a command prompt and then run /etc/rc.d/rc.4 to start XBut I found that the rc.4 uses xdm -nodaemon flag and it was causing problems so I removed and all is pretty good. I still see some odd behavior with the virtual ttys sometimes.2nd -- when building a new kernel, I found I need the device-mapper butcouldn't tell if that was a linux kernel issue or something to do with lilo, I didn't want and don't need multiple disk devices like for LVM or MD so I didn't plan to have this enabled.3rd -- CONFIG_EXT4_USE_FOR_EXT23 When that kernel config option was selected and I have only an EXT4 filesystem, the filesystem was mounted as an EXT2, even though the kernel had no EXT2 feature. /etc/fstab specified EXT4 but the mount command showed EXT2. A silent problem that could leave an unpleasant surprise since EXT2 hos no journaling.4th -- I had to run lilo -C by hand in a virtual tty before finishing the install. This was what I had to do when installing 13.0 on different hardware. It seems that the lilo part of the install needs some sorting out.
View 9 Replies View RelatedJust wondering how can I add the Hi/Lo and the current day information like wind, humidity, etc... to my conkyrc.
Right now here is what I have,
Code:
Location: ${execi 3600 conkyForecast -i --location=USTX0617 --datatype=CN}
Conditions: ${execi 3600 conkyForecast -i --location=USTX0617 --datatype=CC}
${font ConkyWeather:size=36}${execi 3600 conkyForecast -i --location=USTX0617 --datatype=WF}${font}
[Code]....
I'm trying to install bibble5pro. The only packages they provide are binaries:x86_64.deb, i386.deb and i386.rpmI converted the rpm binary to tgz and installed it on my slackware-current (works fine).Then I tried to install it on slack64-current and slack64 13 (both multilib). I tried both rpm2tgz and deb2tgz. The .tgz package gets converted and then installs without any errors. When I run bibble5pro I get the following:
Code:
Install Path: /opt/bibble5pro
LD_PATH: /opt/bibble5pro/lib:
[code]....
I just upgraded to 13.37, and for some reason wicd now cannot connect to my wireless point. It keeps saying the password is wrong, when I know for an absolute fact that it is correct (even changed the password to '1' just to make sure, and no dice. Which is weird because even though its the exact same version of wicd, and not only that, it no longer seems to be able to see networks with my built in card, so having to use a USB card. Anyway, googling turned up very little. Seems to be a common problem across distros, and some people reported that downgrading to 1.6.x fixes it.
So, I ran
Code:
removepkg wicd
And it uninstalled wicd. Downloaded wicd-1.6.2.1-x86_64-1.txz from a 13.0 mirror and did
Code:
installpkg wicd-1.6.2.1-x86_64-1.txz
While in the correct directory. It installed, and I ran wicd. But checking the version number when it loaded, it says its 1.7.0 again.
Not really sure why this happens. I'm assuming there's some remnant of wicd that removepkg doesn't dump, and its preventing me from installing this older version of wicd. What do I need to do for this? If anyone has a surefire way to make 1.7 work again, that would be fine.