The folder contents could not be displayed
Backend currently unmounting
drwx------ 10 userhere group 260 Aug 23 19:40 ..
?????????? ? ? ? ? ? sftp:host=192.168.8.80,user=adhoc
ls: cannot access 'sftp:host=192.168.8.80,user=adoc': Input/output error
$ ps aux|grep fuse
This container won't start after exhausting its memory. There are no relevant or helpful messages in dmesg or vzctl.log as well. Standard troubleshooting such as disabling PPP etc has not helped.
2017-07-06T23:33:29-0400 vzctl : CT 888171 : Locked by: pid 166029, cmdline vzctl start 888171
2017-07-06T23:33:29-0400 vzctl : CT 888171 : Container already locked
2017-07-06T23:33:29-0400 vzctl : CT 888171 : Container was stopped
Here is a simple MP3 player and now there's a reason to understand why the supplied cable has some kind of capacitor and is very short. These devices can be VERY finicky and any voltage fluctuation or difference is enough to cause issues.
Take for example the error messages from Linux Mint:
[804829.895414] usb 1-1: USB disconnect, device number 11
[806961.109030] usb 1-1: new high-speed USB device number 12 using xhci_hcd........
This was a surprising bug but I unplugged all drives for an array md127. At first it was just 1 drive and mdadm seemed to notice this. I unplugged the second drive taking the array offline but mdadm did not realize it was offline and still showed a non-existent disk as being part of it. This created problems trying to unmount it or even to stop this array with mdadm freezing.
As for how to fix it I can only think of making sure you are not in a mounted path of........
The only solution after trying many suggestions was to simply restart the "vz" service (definitely not preferable).
Even doing an ifdown and ifup for venet0 did not help.
Bringing up interface venet0:
Configuring interface venet0:
net.ipv4.conf.venet0.send_redirects = 0
RTNETLINK answers: Network is down
Some errors from log:
CPT ERR: d2dc60........
rm: remove regular file `/vz/lock/1200.lck'? y
vzctl start 1200
Container already locked
vzctl start 1200
Starting container ...
vzquota : (error) can't lock quota file, some quota operations are performing for id 1200
vzquota on failed 
vzquota off 1200
vzctl start 1200
vzquota on 1200
root@rttbox ~]# vzquota off 1200
vzquota : (........
-bash-3.1# shutdown -rn now
Connection to localhost closed by remote host.
Connection to localhost closed.
Sometimes I work with embedded systems/custom kernels without any of the fancy init scripts and other common Linux basics that most would expect. This means that often the "reboot" command (which uses an init script) will never work, not only that but it will hang the server and a manual power cycle or reboo........
I backed up everything in the /mnt/sd_card directory thinking that some dataloss could occur for some reason but purposely left my microSDHC unbacked up thinking that "it won't touch that since it's external" and Samsung's and other manufacturers website even say this (that it won't be affected and not to worry etc).
Apparently I was wrong, my microSD was "undetected" and asked to be formatted after the upgrade (there goes 3-months worth of family photos). No........
umount: /home/diret/mount: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
I tried everything (fusermount -u) to unmount it but the only thing that worked was actually doing this:
ps aux|grep sshfs
Then I identified the sshfs connection and did:
kill -kill pid........
Moving to RAID was a pain.
What you have to do is the following from an existing install:
Create your mdadm RAID 1 array on your spare hard drive.
Start it with the missing disk.
rsync the entire contents of your current / to the md partition.
Here's a good way of doing it:
rsync -Pha --exclude=/proc/* --exclude=/sys/* --exclude=/mnt/* /. /mnt/md2........
From a LiveCD or if you're doing something like converting your non-RAID install to mdadm here's how you would chroot properly (you have to mount your proc, sys and dev on the running system/LiveCD to your chroot environment if you want things to work right, especially if you need to run update-initramfs due to a driver change etc..)
*replace "path" with your mount/chroot path
mount -o bind /proc /mnt/path/proc
mount -o bind /dev/ mnt/pa........
Adding IP address(es): 192.168.5.8 192.168.5.9
Setting CPU units: 1000
Error: undump failed: Invalid argument
Error: iptables-restore exited with 2
Error: Most probably some iptables modules are not loaded
Error: rst_restore_net: -22
Container start failed
Stopping container ...
Container was stopped
Container is unmounted
Error: Failed to undump VE
vzquota : (erro........
Different distributions such as Debian and Centos behave differently when trying to shutdown your system.
shutdown -H now on Debian does not do what you'd expect. The system won't power down, it will halt and do everything but power down.
shutdown -PH now will do the job though (actually power the system off). This is important to test especially if you are not near the system. If you just use -P it forcefully shuts off which is not........
I installed 5.5 with a 300GB RAID 1 partition (boot is also on this partition). It booted up fine the first few times until after I used a Live CD and accessed the array, and it became named /dev/md127 for some reason.
Now whenI boot into CentOS I get a kernel panic and different errors, once I got "invalid superblock", even though the array is fine (it didn't happen again, probably because I was sure to dismount and stop the mdadm array properly).
heartbeat is stopped for some reason
Anyway hnode2 was active and the services are running fine but I see heartbeat has been stopped somehow.
Here is the last log I see of heartbeat:
Sep 9 17:15:32 hnode2 heartbeat: : info: MSG stats: 9/1762471 ms age 0 [pid16738/MST_CONTROL]
Sep 9 17:15:32 hnode2 heartbeat: : info: cl_malloc stats: 716/51784021 152624/74519 [pid16738/MST_CONTROL]
Sep 9 17:15:32........
Clone any OS partition perfectlyIn one box I needed to copy the boot partition to another disk while retaining the MBR and other data.
I simply ran this command:
[code:1:1b1ff110ca]dd if=/dev/hda1 of=/dev/hdb1[/code:1:1b1ff110ca]
[b:1b1ff110ca]if[/b:1b1ff110ca] = source patition
[b:1b1ff110ca]of[/b:1b1ff110ca] = destination partition
Here's an interesting article on it