A few days ago I upgraded from debian 7 to 8. First I update, upgrade and dist upgrade - change source list and again update, upgrade and dist upgrade.When inserting a USB disk on key, it works okay. When plugging my WD "My passport" backup USB disk it does not work. The automatic mount works, but the disk can be accessed.I tried to do it manually in a format that worked on debian 7..Manual mount fails too.
umount My passport
fdisk -l (to see device name)
mount -t vfat -o rw /dev/sdb1 /media/kuku/usb_mp4
dmesg | tail
[ 2381.080822] sd 9:0:0:0: [sdb] No Caching mode page found
[ 2381.080828] sd 9:0:0:0: [sdb] Assuming drive cache: write through
What are the tmpfs's and how can I reclaim that space, and what is /dev/dm-0 and why is that taking up so much space?
I have 2 LVGs vgdisplay -v
Code: Select allroot@SETV-007-WOWZA:~# vgdisplay -v DEGRADED MODE. Incomplete RAID LVs will be processed. Finding all volume groups Finding volume group "WOWZASERVER"
After deleting the log files, I was able to regain access to my GDM session. But I still cant find out what /dev/dm-0 is, and where all the 75 GB is being taken up.
I just noticed, however, even though I can access the drive A-OK via browser, terminal, and web services (Our wowza) when I enter gParted I get this error for sda, my primary OS drive!
Code: Select all Libparted Bug Found!
Error informing the kernel about modifications to partition /dev/sda2 -- Invalid argument. This means Linux won't know about any changes you made to /dev/sda2 until you reboot -- so you shouldn't mount it or use it in any way before rebooting
Now that I'm in gParted I see 3 partitions: [URL] ....
It reports now, that I have used ALL of my disk space.
Post Log delete, and fresh reboot, this is what Code: Select alldf -h outputs
Running Debian stable. I added the following command to rc.local and made it executable:mount -t cifs -o username=ted,password=computer,uid=mooreted,gid=users "//192.168.1.121/Storage Volume" /mnt/vortexAfter rebooting dmesg throws the following error:
I eventually gave up and migrated to mdadm. Works just fine. Having upgraded to jessie and solved one problem
I find the next one. When I boot into jessie my RAID device (just a data partition not /) is not found causing the boot to fail as per problems reported here
After booting I can mount my RAID device but if it's in the fstab when booting it fails. Also, I notice that some of my lvm device names have changed. After a bit of hunting around I found a couple of solutions pointing to running dmraid as a service during boot and changing the entry for the RAID device in fstab to use the UUID.
This seems to work. However this seems to be a workaround and as the lvm device paths for my / and /usr partitions have also changed, I'm wondering if there is a bug here as mentioned in the second link?
The / and /usr paths changed to /dev/dm-2 and /dev/dm-3 from the /dev/mapper/ form.
I got a little problem with Xubuntu here. Every time after I boot the system, I find one of my partitions from fstab not mounted where it's supposed to be. I do mount -a, and it replies: "mount: /dev/sdb6 already mounted or /mnt/data busy". Checking lsof of neither device nor mount point gives me nothing, and checking the output of mount I see device isn't mounted anywhere.
It gets better than this: after some time, device can be mounted just fine, this time is from 11 to 12 minutes. If something is doing anything with my device that takes whole 11 minutes, how come I don't know what it is? How can I mount device on boot? Some more (ir)relevant facts:
1. This partition is the biggest - 376 Gb
2. Here's my fstab line for this device:
Code: /dev/sdb6/mnt/dataext3defaults02 3. After the installation, I changed the mount point in fstab, and using /dev/sdb6 instead of UUID is a result of blind experimentation
If i click the ntfs partition from nautilus, it prompts to type password. If i type the password and enter, i see this message:
Code: Select allUnable to access “alldisksda5” Error mounting /dev/sda5 at /media/user1/alldisksda5: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sda5" "/media/user1/alldisksda5"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/sda5': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.
It seems like ifconfig used to show which DNS servers were being addressed, but something has changed, I need to know whether I am referencing what I think I am... I have search this forum, googled, and come up empty... did the metrics go away with 8.2? Was I dreaming at 7.5?
I'm running KDE in Jessie and also have Gnome installed. When I connect a usb drive it gets mounted at /media/username/disklabel. I would like to have it mounted at /media/disklabel which is how it worked in Wheezy. How can I make that change?
I have been building a debian jessie system reasonably successfully but have come unstuck with libpam-mount. On a previous Ubuntu saucy system I simply installed it, created the appropriate pam_mount.conf.xml file and mounts would happen when users logged on and dismount on logoff. With jessie I can see that there is a libpam-mount package in main but when I try apt-get install it fails. If this package has been obsoleted (as one of the messages indicates might be the issue) what is the jessie way of handling this?
Here is my sources.list Code: Select alldeb http://mirror.aarnet.edu.au/debian/ jessie main non-free contrib deb-src http://mirror.aarnet.edu.au/debian/ jessie main non-free contrib
i am a new user to linux, i installed debian on dual boot with windows 7but now i am unable to access the ntfs drives used by windows originally from the debian OSi am wondering what could be the problem and how can i solve it
I have a relative fresh install of jessie in which I face a high cpu usage of java (top shows about 165% CPU and 12% MEM). The problem occurs right after booting the computer. These values stay constantly high for days if I leave the box running. This happens even if the computer is just sitting there without doing anything.
I have to kill java to go back to normal. So, when I do a Code: Select allkillall -KILL java the problem goes away. After that it doesn't reappear and I can use all apps installed without a problem.
Currently I am based on openjdk Code: Select allupdate-alternatives --display java java - auto mode link currently points to /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java - priority 1071 slave java.1.gz: /usr/lib/jvm/java-7-openjdk-amd64/jre/man/man1/java.1.gz Current 'best' version is '/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java'.
But I have also tried the SUN version with the same result.
Where to look to find more information on what exactly java app is using so much resources and how I can solve it? I guess I could just put somewhere in rc.d a kill java command and forget about it but I would really like to find out whats going on...
When i'm tried google there is lots of bootlogd related document there. [URL] .... Yes there is documentation. But I'm only need "enable boot logging","reading boot log". Bootlogd not worked on jessie/stretch.
I am having trouble using touch pad in jessie. My touch pad was ok when it's in wheezy but after i updated to jessie, i can't really get used to it.
I don't know whether i setting it up wrongly, sometimes, my touchpad will keep dragging, without releasing. And if I click the bottom right of the touch pad, it's not right click; instead i have to use two fingers.
etc. So how can i change to back to a more traditional usage? Also, do jessie have a setting like ubuntu saying disable touch pad while typing?
After installing Jessie, apt-get gives me a huge list of packages with the suggestion to autoremove them. Now, I've tried auto-remove once and was left with a naked Gnome, so I was wondering if there's another way to find out which packages I should keep and which I can safely remove. Is it safe to delete packages that cannot be found using the search function for the stable release? I checked them one by one here URL....How about linux images that won't appear in the above search?
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
After changing my video cards from gigabyte HD5450 and saphire X550 to two saphire r7 240s one of my debian installs no longer supports rotating the monitors either with 'Monitor Settings' or xrandr. The only difference between these 2 Jessie installs is that one was upgraded and the other one was fresh. The problem is with the upgraded one. On the fresh installed debian I just put the ati proprietary driver so I won't do further testing on it but xrandr was working fine on it before that.
I tried going over the ATIHowTo [URL] .... and everything looks good. Tried purging the non free firmware and reinstalling. I verified the version numbers of libxrandr2 and kernel of both installs. It is either some scrap left over from wheezy or a configuration file I am not aware of.
So what actually happens is xrandr does not say anything, blanks out all windows on the screen with only their background color and title bar showing, changes the lxpanel to its background pattern except for 2 blanked out boxes almost to the right of the screen( I have 10 tray icons there before it blanks), activates the screen I wanted to rotate with the proper rotation. On my main screen I can't click on anything. On the rotated screen I can right click and I get my openbox right click menu like I do on my main monitor before the command but when I try to run something nothing happens. The only way I can get out of this situation is to go to ctrl-alt-f1, log in as root and type 'service lightdm restart'.
Both of these monitors are connected to the primary video card, an ati r7 240 saphire. The main one is on vga and the other one is on DVI. I also have another monitor connected to HDMI but it's not being used. I have yet another monitor connected to the VGA of the secondary GPU I don't think it's a problem is it? I tried not using 'xrandr --setprovideroutputsource 1 0' and it still did the same thing.
I tried just launching openbox with no LXDE and it did the same thing.
Also another strange thing is when I stop the lightdm service and try to 'startx' or 'xinit' my screens go blank; numlock, control-alt-delete and control-alt-f1 do nothing and the only thing I can do is an emergency REISUB. I didn't configure this install to use startx or xinit yet but should it really lock up my system?
On the affected system my script looks like this (I already did this step by step and the 'rotate left' line is causing the problem):
I am using Jessie with XFCE and I tried to write a service which executes a script to change my wallpaper. When I try to start the service with systemctl start wallpaper.service it fails and I get the outout below from systemctl status wallpaper.service
I don't think it to be a permissions issue, they are -rw- r-- r--
This service is called by a timer that goes off daily. Below is wallpaper.service
I've recently noted that the boot process in my Jessie installation is occasionally taking longer than usual, not dramatically as in "really hanging", but still noticeably slower, during which some messages are printed along the lines of
Code: Select alla starting job is running (2 of 5) and also after that, once lightdm (I'm using the MATE desktop) comes up the screen gets painted slower as well.
Unfortunately, once the system is up and running there's no longer trace in the logs (either traditional syslogs or journalctl) of such messages, however what comes to mind is that I've just recently enabled persistent logging in systemd: could this be the reason of such (occasional) slower boot process?
Other than that, what else could cause such behaviour? What should I eventually check to ensure things are OK?
I built a kernel-module for a new usb wifi-card. This worked well and resulted in a 8821au.ko-file. But now I'm trying to load this kernel module since half an hour and it doesn't work. I copied the ko-file into /lib/modules/3.16.0-4-amd64/kernel/drivers/edimax. If I just type
Code: Select allsudo modprobe 8821au
I get a
Code: Select allmodprobe: FATAL: Module 8821au not found..
But if I enter the full path inside the /lib/modules/3.16.0-4-amd64-folder:
to /etc/modules but this also doesn't seem to work. When booting I get an error-message, but it's too fast to read it and I can't find the right log-file, where the booting-part with the "[ OK ]"-messages is reported.
So my driver is ready, the onliest thing which I can't get working is loading it as a kernel-module.
(==) Log file: "/var/log/Xorg.0.log", Time: xx (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) open /dev/fb0: No such file or directory
My usual aptitude safe-upgrade routine has not throw any errors. I do remember a libxcb-* package updating (or installing?) on the last run. This is the only relevant package I can recall.
I'm trying to upgrade my Win8/Wheezy 64-bit machine to Jessie 8.1 by installing from the amd64-bit netinstall iso image on a USB flash drive. I had done the previous, Wheezy, install on a disk partition that was whole-partition LUKS/LVM drive, with separate logical partitions for swap, root, and home.
Before doing the upgrade, I booted to the BIOS to ensure that my UEFI system had the correct, CSM and Legacy modes enabled in it, so that installer would boot using the non-efi BIOS mode.
Step one of the upgrade was to boot the netinstall and enter the rescue mode so that I could manually do the cryptsetup/LVM business. When I returned to the installer, I mounted the now-recognized logical partitions normally, choosing to format only the swap and / partitions.
During the entire process, I had to go into rescue mode one more time to manually mount the unencrypted /boot partition, along with my /home partition. I copied a backup of my old /etc/crypttab from the latter, and after returning to the installer, finished the install. That finish included installing grub on my hard drive's main boot partition.
Everything seemed to finish with no problems. However, when I try to boot the debian bootloader, I get tossed to grub rescue with the message that '/grub/x86_64-efi/normal.mod' doesn't exist. At this point I returned to the installer, mounted the /boot partition, and saw that there grub-install didn't create that an x86_64-efi directory at all. Instead, it had created an i386 directory. The exact name escapes me at the moment.
I *think* that my install was clean other than the last bit that was related to installing the bootloader. How to reinstall the bootloader in such a way as to make all of this work.
updated my jessie by apt-get dist-upgrade and there was an error said there was something wrong with some database, and I needed to run some command, but after the upgrade I forgot to run the command. After I rebooted my system I found there was not any password needed for a normal user or the root. But if I change to the emergency mode, a root password is needed.
Recently tried to make RAID1 on MBR partitions scheme on Debian Jessie - debian-8.1.0-amd64-DVD-1. The issue - I have unable to boot from second drive after grub-install /dev/sdb by any ways. RAID1 itself for / swap and home is fully functional. Decided to try the same thing on GPT, same story. How to boot from second drive on most recent Debian Branches?