Very frustrated. I have used Unix for ages so I understood the SysV startup stuff. But I have not had a lot of luck with Upstart. The other day I noticed that on every reboot my disks are getting fsck'd. I just recently put an ext2 on /tmp so this takes a while (the ext4 drives just rip through their journals).
The problem is no one is unmounting them on a KDE restart (4.X). I started out looking at /etc/init.d/umountfs and putting some logging in there. It never runs. This is despite that /etc/init has an upstart job that is supposed to run all the runlevel stuff.
I also tried to log some info in /etc/init/mountall-shell.conf which looks like it tries to do a umount -a on shutdown (which is probably not a good idea; you need to unmount in a particular order). That doesn't seem to happen either. I am not even sure how to troubleshoot this further. I suppose I need to see if the reboot( command has the same problem. Or if I shut down kdm first if it goes away.
I have/had a PC with several hard drives, and a mix of ubuntu and windows on multi boot.The old boot drive died screaming, and I need to start again. (But my data is safe! yay!)
Is there anything special about which drive can be the main drive to start booting from? Or to put it another way, can I install to any of the other 3 and expect it to work, or do I need to switch them around so a different drive is on the connections for the recently dead one?
I have servers which contain SATA disks and SAS disks. I was testing the speed of writing on these servers and I recognized that SAS 10.000 disks much more slowly than the SATA 7200. What do you think about this slowness? What are the reasons of this slowness?
I am giving the below rates (values) which I took from my test (from my comparisons between SAS 10.000 and SATA 7200);
dd if=/dev/zero of=bigfile.txt bs=1024 count=1000000 when this comment was run in SAS disk server, I took this output(10.000 rpm)
(a new server,2 CPU 8 core and 8 gb ram)
1000000+0 records in 1000000+0 records out 1024000000 bytes (1.0 GB) copied, 12.9662 s, 79.0 MB/s (I have not used this server yet) (hw raid1)
I have just installed 10.04 as an upgrade from 9.10.
I am having difficulty because none of the USB drives I am using are unmounting as they should be. normally speaking when erasing data from my USB key when you come to unmounting it it will ask if you would like to send this data to the recycle bin thus giving you back the extra storage space on the device. 10.04 isnt allowing me to send these items to the recycle bin ad doesn't give the option to do this.
10.10 MMeerkat - When I use a USB-stick or external hard drive, I don't get the "unmount" option but instead it says "safely remove drive".When I click this, Nautilus immediately crashes and is gone.Is this a known bug in 10.10?
I've spent the better part of an afternoon looking for a solution to a problem: backing up my installation of 10.10 as an image file to an external hard drive. My research has yielded a lot of suggestions for clonezilla, dd, and partimage/particlone, but those don't seem very appealing, due to a number of issues (can't backup live, copies free space as well, doesn't handle ext4, etc). Also why is clonezilla 150mb?
I'd like a simple solution that can clone an entire disk (used space only) to an explorable image file on a separate hard drive and be able to do it while the operating system is running on the disk. I used to use apricorn ez gig to do this on windows and it worked like a charm, but I can't seem to find a similar solution that creates and explorable .iso image file with linux. I've used superduer on osx, which is awesome and i wish there was something like that for ubuntu/linux.
I get the following error each time I try to safely remove the USB stick (by right-clicking on the USB stick icon on the desktop and choosing "Remove safely") code...
It used to work without errors when unmounting the USB from Nautilus window, but now, I get the same error when unmounting from there as well. Is it safe to assume that the stick can be removed even though the error message is displayed? What might be the cause? Also, I do not have any Nautilus-windows opened nor any applications that are locking any files on the USB stick while removing it.
I want to move my / partition to the end of my drive (sda). To do this with gparted, I have to unmount it, but I'm not comfortable with the idea of unmounting root partition... Should I do it from a live cd? More important : is the operation safe?
I seem to be having some issues. I want to do the following. I want a script to run prior to any GUI starting (so that if it does crash close or whatever it is not effected).I am able to run the script after the system is booted and it works exactly as I want it to. Once the GUI opens I have a window open and maximize with no decoraction via devilspie. This way I have a desktop that can monitor the logs but not interact directly interact with the shell which is actually recording the logs.
The problem is, when I try and use a simple Upstart script to start it the script does not seem to be working. If I do a ps -A it seems to be still running. What it should be doing is recording what the serial input to the log file I am using. In fact... it doesn't seem to be capturing anything. If I try and run the script manually after the computer has booted (with the Upstart script run) to a GUI it crashes the system.The script I am running is simply to record any incoming data from a Serial connection. It sets up the serial port then starts recording.The shell script is as follows:
uh, I screwed up. I mounted the wrong thing with ntfs-config. Now, this really isn't a big deal but... It'd be nice to have it organized and a 11 GB partition not mounted on boot
We are using Ubuntu 10.04LTS server on Vmware Vsphere estate. We are using LVM and have / and /var on separate partitions.
We have been experiencing an odd issue with sda1 always being fsck'd after every reboot. We seem to have traced this to the start/kill scripts in rc0.d and rc6.d. It appears that the reason the disk is not being unmounted is because some of the scripts are never being run because they are prefixed with S. We renamed and reordered the scripts to reflect what we thought should be the correct order - i.e. not halting the system before unmounting disks. System reboots cleanly now.
Before list of rc0.d and rc6.d respectively: lrwxrwxrwx 1 root root 17 2010-11-18 15:06 K01apache2 -> ../init.d/apache2 lrwxrwxrwx 1 root root 22 2010-11-16 17:03 K01zabbix-agent -> ../init.d/zabbix-agent lrwxrwxrwx 1 root root 22 2010-11-30 08:16 K03vmware-tools -> ../init.d/vmware-tools
[Code]....
basically are we expected to do these changes as part of building new servers for production use? Quite happy to do this but just surprised that this is the default.
I have run into a problem that I've tracked down to being a conflict between the "Upstart" init system, and how it handles multiple (alias) IP addresses per physical interface. The summary of the problem is that the interfaces are being configured in the background in parallel with the starting of daemons. One "feature" of this (apparently intended for pluggable devices that would add or remove an interface) is that the network daemons are restarted each time an interface is added (and presumably deleted). But this is a disaster when applied to alias IP addresses.
I first saw the effects of this when during booting Ubuntu Server, the screen showed a message about OpenSSH daemon being restarted ... several times a few seconds apart each. At the time I didn't know what was causing that, but didn't worry because it ultimately was running when I needed it.
But now that I am deploying these servers for specific duty with many IP addresses per system (per network interface), the symptoms are becoming serious, and I need a solution.
1. The IP addresses are coming online too slowly. Apparently the time it takes to restart each daemon is being added to each address being configured.
2. It appears to be disrupting some daemons sometimes. Occaisionally, some daemon just ends up being hung somewhere, or dies. Too many restarts.
3. Sometimes few or even no alias addresses get configured. This might be due to a daemon getting hung, and the whole sequence just not finishing.
4. The "nsd" name server as packaged by Ubuntu doesn't deal well with this at all. It needs all its IP addresses to be up when it starts, or else it won't start. The Ubuntu package of it doesn't including any if-up script at all, although I'm not sure that would do any good.
What I need is a way to configure all these alias IP addresses so they are all configured immediately when the point in time is reached to bring up network interfaces for the first time. These are all static, and all are aliases on ethernet NIC cards plugged into PCIe cards, or integrated in the mainboard. None of them are pluggables. I did run a manual test of "ifconfig" in a loop configuring 2540 alias IP address on eth0 and it only took 2 seconds (no if-up triggers or daemon restarts here). So I know it's fast if nothing else is done between these steps.
Even for pluggable physical interfaces, I see no reason to even try to step through every alias (if it has aliases) with a daemon restart. If an alias IP address is added on later, then I can understand doing it. But if you have a list of 100 aliases for a physical interface, they really should all be done ... or at least attempted ... at once, and do any triggers needed after that.
So, how can I configure or modify Ubuntu Server 9.10 to do that?
I have each alias listed in the "/etc/network/interfaces" file with a separate "auto" and "iface" section for each one, with sequential sub-interface numbers appended to the interface name. I tried it without those sections (e.g. just "address" and other items in sequence) and that prevents the system from even coming up (bootable CD to the rescue to undo that). At least cntrl-alt-del did reboot it.
I tried to attach the /etc/network/interfaces file, but I don't know if it worked because I see no confirmations about it. if it didn't attach and you need to see it, say so, and I'll just paste it in a followup.
Like the title stated Anyone with experience or suggestion, please do share. I've tinkered all night with this thing. Never get the VBox service I created to start.Here is my final code before I dried my brain.
I recently discovered upstart is launching sshd on my machine even though I disabled it with `sudo update-rc.d -f ssh remove`. I tried to find a way to prevent upstart from launching ssh by default, but the best I can think of is removing /etc/init/ssh.conf (I just uninstalled openssh-server).I'd like to disable it without doing this, though. This would make it easier to enable sshd when I need it
From what I've read, it appears that the respawn stanza in /etc/init/mysql.conf would give me the restart option if the daemon crashes, but I want to make sure other safety features of mysqld_safe are present as well.My /etc/init/mysql.conf is the original. I've tried changing the exec stanza from /usr/sbin/mysqld to /usr/sbin/mysqld_safe but the job fails when I sudo service mysql start.mysql.conf
I have an external hard drive (1TB MyBook) mounted via fstab by UUID to a directory. When copying/writing/reading a lot of files from it, it randomly unmounts and remounts as a different device.
It'll start as /dev/sdb1, I'll set a lot of files to copy to it and then it'll unmount and re-acknowledge itself as /dev/sdc1, the file copying process will crash and the current directory in terminal will display an I/O error. Running mount -a remounts it back to the directory specified in fstab as /dev/sdc1 and the loop continues. If it's just idling, there's no issue, only does this under load.
- Nautilus open in browser mode (the default)?- I click the eject symbol to unmount a usb stick in the side pane.- The annoying red exclamation police light looking thing pops up telling me that nautilus crashed.- Not only is the usb stick unmounted, but the device file also disapears (e.g. no longer listed by fdisk).- This problem does NOT occur when I use other methods to unmount (e.g. umount on command line, or right-click on desktop icon and select eject action), only when I click the eject symbol in the nautilus side pane
been puzzling over this for a while, searched forums and net but no issues/solutions found. I have the above device plugged in and working fine. However when un-mounting - either through dolphin or device notifier, I get the report that the item is unmounted but then when removing USB cable from the Zen, it closes down and then rebuilds the entire 16GB collection - this takes quiet a bit of time and I worry that I may end up frying the Zen. Is there a fix for this in Suse or is it the zen. it doesn't happen on my work machine running windows though.
I have a volume that shows as the following when I do a df -h. How would I go about unmounting it so I can run an e2fsck on it, then remounting it? normally it mounts when the server starts, so i'm not sure how to manually do it.
Sometimes I get a problem with the basic "umount" command. I get an error message telling me that for one reason or another, the device couldn't be unmounted. Usually, it says the device is busy, when I can't see how it possibly can be. When this happens I'll use "umount -l" or "umount -f" or sometimes "eject" but I'm still not happy, because at the back of my mind I'm worried about damaging the integrity of the device's filesystem. What's the CORRECT way to deal with this problem?
I stupidly unplugget my USB-cable, which was connected to my Nokia music phone, just as if I were in Windows. What do I do? I've lost my music on the phone, or, it seems it may be there (the correct mass of data), but my phone now tells me there is no music... Can I recover this? And - what is the correct way to unplug a USB unit in Ubuntu? To make it work, and find the phone/drive - I just typed "sudo lsusb" in the terminal, and it found and opened the memory automatically... How should you unmount the USB, and maybe even how do I get my data back?
I have a server with Ubuntu 8.04.4 LTS completely patched up to date.I tried to mount a windows share using smbmount and unmounting it with smbumount. I did it as a non root user (let's say "someuser") and managed to mount the share without problems with "smbmount \\server\share xxx" where "xxx" was a directory on the user's root. After it I could see the shared files in the xxx directory, as it was supposed to be...
The problems came when trying to unmount it. Using "smbumount \\server\share xxx" didn't work giving "This utility only unmounts cifs filesystems." error message. Then I tried "smbumount xxx" and worked. I couldn't see the files in xxx directory anymore, and I could even delete xxx directory.
But now, when looking at /etc/mtab file, I still can see the share listed as mounted! The line is: "//server/share /home/someuser/xxx cifs rw,mand,nosuid,nodev,user=someuser 0 0". Also, df command lists the share as mounted too. But, as I said, the share is not really mounted, and I can even delete xxx directory without any problem... /proc/mounts doesn't list the share as mounted either... And, obviously, fstab file has no entry for this mount.
Moreover, /etc/mtab file group changed from root to someuser!I don't really understand what happened, but I assume some bug with smbumount or smbmount. Anyway, what does really worry me is how to fix this mess... I already changed mtab file group back to root, but I don't know how to return the mtab file to a consistent state.My main question is: can I simply edit mtab file and remove the inconsistent line?? I know one should never have to manually edit this file, but can it really be done in a situation like the one I'm describing? What could happen if I do it?
Also, I'm worried about if I don't do something to fix the inconsistency I could have problems when trying to shutdown the computer, or in any other situation. So, should it be safe to leave things unfixed and let everything return to normality when the system is rebooted?
I'd like to reconfigure vsftpd so that it does not start on boot (and I can enable/disable it using service vsftpd start/stop).
Though I've seen posts in the forums that stated that upstart jobs can be disabled by moving the /etc/init/job.conf file, other sites commented that the original file will be recreated on updates.
The other two suggestions were to alter the upstart script such that either the process starts on never:
Code: start on (never and filesystem and net-device-up IFACE!=lo) stop on runlevel [!2345]
Has anyone got a working apache upstart script? I'm running 10.04, and want the nice supervision stuff from upstart to run my apache instance. I've googled (especially for things like replacement-initscripts) but not hit anything concrete.
I'd like to create a couple of upstart scripts for some network service daemons (eg. usenet downloading service, torrent service, media management services, etc).Basically they should start after the network service is started and the system is running (runlevel 2?) but I'm just wondering if anybody has an example script or more specific start/stop conditions that I can use.
I have posted this somewhere here before and solved it but can't seem to find it. Just waisted 50 minutes googling and checking man pages for upstart. By the way; are man pages written by someone using their tows to type and getting beaten by a stick for every character they type? It seems missing a lot of info. Anyway, I know smbd is started with /etc/init/smbd.conf and there is a line like:
Code: start on local-filesystems Now it needs to be started on? (manually) I can't seem to find any useful information but did seem to find the upstart man pages a hundred times or so (same info same missing parts). I would love to get involved writing documentation for these things if only I know what I was doing.
