I had a Linux server with Wheezy, I have 2 internal drive, one for linux OS, the other our Video On Demand drive that must be accessible to Windows and online. (That's why I chose NTFS, with our large video files, FAT will not work, and EXT isn't compatible with windows sharing, and I haven't gotten FTP to work right .
So I upgraded to Jessie today, and everything went smoothly until I tried to access my NTFS drive. (Named WowzaStorage)
I used FSTAB to auto-mount the drive (/dev/sdb1) to /media/ntfs/ on boot. All of this worked swimmingly on Wheezy, but since the update, something got mucked up and I cannot figure it out.
When accessing the mounted NTFS folder in /media/ (if it even shows up) gives me a 'Cannot be found' 'Input/Output error'
When in gParted to examine the drive, I can select it and view all the correct info, but I keep getting "error informing the kernel about modifications to partition /dev/sdb1/ --invalid argument"
Now first I thought maybe the NTFS driver was faulty and I removed 'ntfs-3g' and reinstalled it.
Now when I am in Terminal, after i umount and mount sdb1, I can CD to the drive but not the folders on it... Also using the File Browser, I get errors, and missing folders.
I get "Unhandled error message: Error when getting information for file '/media/ntfs': Input/output error"
I upgraded from Wheezy to Jessie yesterday and no longer have sound. I don't think anything is muted. I checked alsamixer and everything is on. MOC, VLC, speaker-test and aplay are all giving me errors. MOC refuses to load.
Code: Select allccc@de:~$ speaker-test
speaker-test 1.0.28
Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave Playback open error: -2,No such file or directory Code: Select allaplay /usr/share/sounds/alsa/Front_Center.wav ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave aplay: main:722: audio open error: No such file or directory
Code: Select allccc@de:~$ mocp Running the server... Trying JACK... Trying ALSA... ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave Trying OSS...
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.
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.
I've upgraded a server on our LAN from fully functioning Wheezy to Jessie. All seems fine except remote administering using Putty from my windows workstation when issuing reboot from command line, it goes down and reboots but stops at login prompt asking for username and password and does not come back on the LAN network. This server does not normally have a monitor or keyboard so my ability to remote admin this server in effect is disabled.
If I log on, it will come back on the LAN network. I've checked the logs but can't see any errors. Is it in the configuration of Jessie somewhere or perhaps a Grub issue. I have 5 other production Wheezy servers that I intend to update to Jessie once I understand how to deal with this problem.
I just upgraded to jessie and now Samba won't let me log in anymore. I merged smb.conf manually. It now looks like this (removed comments):
Code: Select all[global] workgroup = WORKGROUP dns proxy = no bind interfaces only = no log file = /var/log/samba/log.%m max log size = 1000 syslog = 0
[Code] .....
With smbclient logs as follows: Code: Select allsmbclient -L 192...
Enter user's password: session setup failed: NT_STATUS_UNSUCCESSFUL
If I provide a wrong password, it raises NT_STATUS_LOGON_FAILURE, also if retry with the correct password.
Not sure about what resolved the issue. But after I purged samba, reconfigured it, added the users AND set www-data's shell to bash again (which was changed during the update), it now seems to work
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?
I eventually gave up and migrated to mdadm. Works just fine. Having upgraded to jessie and solved one problem
[URL] ....
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
[URL] ....
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.
[URL] .....
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 had a pretty much standard installation according to some tutorial (I don't remember, which one) for courier, including ssl. After upgrading from Wheezy (7) to Jessie (8) everything continued working fine, excep ssl connections to pop or imap.
In the log I get this error message while connecting to imapd-ssl:
--- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 341 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE ---
TLS over STARTTLS is also not working and does not invoke a log-entry. So I want to solve the ssl-problem first. I guess the STARTTLS-problem is automatically solved then.
My update procedure was:
Editing /etc/apt/sources.listapt-get updateapt-get upgradeapt-get dist-upgradeKeep all configuration files regarding courier.
I have just upgraded to Jessie and everything seems to be OK apart from printing from a windows machine to my print share. This was working previously under wheezy. I can print a test page from Cups without any problems, but when I try and print from windows, Samba seems to crash completely and is constantly writing these messages to the logs. Then I lose access to the other shares, presumably while it repeatedly crashes.
STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid [2015/09/22 12:02:03.989596, 0] ../source3/lib/util.c:785(smb_panic_s3) PANIC (pid 3704): assert failed: pjob->jobid == jobid [2015/09/22 12:02:03.991930, 0] ../source3/lib/util.c:896(log_stack_trace) BACKTRACE: 27 stack frames:
A few weeks ago I have installed Debian Jessie on KDE Desktop Version. I have a problem with the Display Manager Kdm, if i log out session the monitor turns off (DVI No Signal), the only option that I have it's forced shutdown or reboot via power button. I try another DM lightdm and this works fine. But i liked to know why log out session crash on Kdm.
Adding : TerminateServer=true at the end of /etc/kde4/kdm/kdmrc (Section :[X-:*-Core], solve the issue.
Device Boot Start End Sectors Size Id Type /dev/sdb1 16065 584830259 584814195 278.9G f W95 Ext'd (LBA) /dev/sdb5 16128 584830259 584814132 278.9G 7 HPFS/NTFS/exFAT
I have 2 hard drives both are 278.9GB in a mirror raid 1. Why does 2 partitions show up? Are they referring to each physical hard drive? I want to believe that this is the same partition and not two different physical hard drives since both are in the same 'start' and 'end' range. Is that correct?
I`m unable to mount my second hard drive I use to store my music and pics and wonder if it is to do with the error "failed to initialise HAL!" which I get every time I start Debian Lenny (AMD64 architecture). I have had this since doing an install (fresh) a few hours ago.
The drive is an ntfs one but when I click its icon in the computer section it says it cannot mount it and gparted says it cannot read the file system.If so how would I get the error box to stop appearing and how do I mount the ntfs drive?
When I plug in my external USB Hard drive which is formatted as a single NTFS partition, it is recognized and mounted automatically, a nautilus window pops open. Unfortunately it is not writable. The reason is: the partition is mounted "ntfs" (which lacks write support) instead of "ntfs-3g". This is the output of mount after plugging in the drive:
$ mount | grep sdc1 /dev/sdc1 on /media/4EBC5FB82435B0EE type ntfs (rw,nosuid,nodev,uhelper=devkit,uid=1000,gid=1000,dmask=0077)
I want this partition to be writable by just plugging it in.
The partition should not have any errors because a) I fsck'ed it windows and b) mounting it manually works:
$ sudo mount -t ntfs-3g /dev/sdc1 /media/disk_/ $ mount | grep sdc1 /dev/sdc1 on /media/disk_ type fuseblk (rw,allow_other,blksize=4096) $ devkit-disks --mount-fstype ntfs-3g --mount /dev/sdc1 Mounted /org/freedesktop/DeviceKit/Disks/devices/sdc1 at /media/4EBC5FB82435B0EE $ mount | grep sdc1 /dev/sdc1 on /media/4EBC5FB82435B0EE type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096) $ gnome-mount -nbtd /dev/sdc1 $ mount | grep sdc1 /dev/sdc1 on /media/disk type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
How can I get ntfs drives to be mounted as writable by default, preferrably without having to modify fstab?
Basically, I have no trouble booting off a really old kernel like 2.6.18-6. If I try to boot off the newest one installed with Lenny, I get errors such as "mounting /dev/ on /root/dev failed...ditto for /sys on /root/sys" almost as if it's failing to find the drive. This finishes up with "target filesystem doesn't have /sbin/init" and I'm dropped into a busybox shell.It's an ordinary SATA drive, which is being used as an OS drive only. It seems as if something has changed with the newer kernel, but I have no idea where to start or what to look for.
Previously it was only trying to mount the partition (after asking for the root password) in /media/datas
Is it normal that now it tries to mount it only for my current user in another folder?
If I look in the /var/log/messages, I only see this:
May 22 23:53:06 Tieum-Latitude gnome-session[2092]: Thunar: Failed to open "/media/mb/datas": Error when getting information for file '/media/mb/datas': Input/output error
I have 4 drives in my system. Two are SATA and configured in a RAID 1. This is my main drive for the system. The other two drives are IDE drives used to bulk temp storage. Before the upgrade my RAID drives were:
/dev/sda /dev/sdb
I'm not sure what the IDE drives were. Now after the upgrade the IDE drives are:
/dev/sda /dev/sdb
and the RAID SATA drives are:
/dev/sdc /dev/sdd
Needless to say on reboot the raid blow up and the system would not boot. I was able to get it working for now by removing the IDE drives. My current mdadm.conf file is as follows:
Now I assume that I could change the devices to the new devices names. However I was hoping for a better way to do this. The IDE drives are only semi permanent. Is there a way to configure mdadm with partition labels like you can in fstab?
After yesterday's apt-get dist-upgrade, I lost my higher screen resolutions. Only had 800x600 and 640x480. After trying to re-install the Nvidia drivers several different ways without success, I ended up purging xorg and xserver and then starting from scratch, re-installing the drivers. In doing so, I either found the problem, or created another, ha.I think part of the problem was that I mixed Nvidia proprietary and debian installations and the update broke the drivers.I am now unable to install xorg or xserver because I can not remove/purge libgl1-nvidia-alternatives.
and this morning's updates broke x. I get a blank screen instead of the login. I'm running an Nvidia 7900GS. I tried re-installing the Nvidia drivers... no good. I switched to the nv drivers and got further; I got the login screen, but when I try to log in it gives me the KDE splash screen and then takes me back to the login screen. I'm not sure what to try next.
Yesterday, I ran a security update that upgraded my Squeeze kernel from 2.6.32-48squeeze8 to 2.6.32-48squeeze9.
Ever since then, my suspend to ram (STR) function is broken.
The machine will suspend normally, but will not resume. When I try to awaken the machine, I can hear the fan in the tower start up (the subject machine is a desktop computer, please see below for specifics), but the machine seems to be otherwise dead (e.g. the monitor stays blank, pressing the "caps lock" key on my keyboard does not activate said keyboard's "caps lock" led, Ctrl-Alt-F[x] has no effect, etc). My only recourse at that point is a hardware reset (ouch!).
I tried running Code: Select allpm-suspend from a terminal, with no joy. Same result running Code: Select allecho -n "mem" > /sys/power/state from a terminal.
I checked the /var/log/pm-suspend.log file and noticed that each Code: Select all...performing suspend line used to (before said kernel upgrade) be directly followed by a Code: Select all...Awake. line, but, now, all said Code: Select all...performing suspend lines are followed by an Code: Select allInitial commandline parameters... line.
Before this, STR has worked well ever since I first loaded Squeeze on this machine back in 2012.
Code: Select allSqueeze 6.0.10; 2.6.32-5-amd64
Intel i7-980 Gulftown CPU Asus P6X58D Premium Motherboard EVGA GeForce GTS-450 Graphics Card G.SKILL Ripjaw DDR3-1600, PC3-12800, 1.5v RAM (6x4GB sticks, 24GB total) Crucial RealSSD C300 128GB SSD Western Digital Caviar Black 1TB HDD Corsair HX850 PSU
I'm running debian testing on my laptop. This morning when I ran apt-get update && apt-get dist-upgrade, I was greeted by the following errors:
Code: Select all
Calculating upgrade... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information to resolve the situation:
The following packages have unmet dependencies:
libcurl3-gnutls : Depends: librtmp1 (>= 2.4+20131018.git79459a2-3~) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
A quick search found out that package librtmp1(2:2.4~20150315.gita107cef9b-dmo1) is already installed.
I do have some packages set on hold, however I don't think that's the problem:
Code: Select all$ dpkg --get-selections | grep hold hostapd hold libgcrypt11:amd64 hold linux-image-amd64 hold
My sources.list on which I haven't touched for a very long time:
Code: Select alldeb http://mirrors.163.com/debian/ testing main non-free contrib deb-src http://mirrors.163.com/debian/ testing main non-free contrib
deb http://mirrors.163.com/debian-security/ testing/updates main contrib non-free deb-src http://mirrors.163.com/debian-security/ testing/updates main contrib non-free
deb http://mirrors.163.com/debian/ testing-updates main contrib non-free deb-src http://mirrors.163.com/debian/ testing-updates main contrib non-free
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 installed Debian Jessie on my Hummingbaord. I use it with apache, owncloud and minidlna but after some days i rebooted the system and then i can't log in with SSH anymore.
The message I get:
Access denied Using keyboard-interactive authentication. Password:
And this again and again, although I enter the right password. If I login directly on the Hummingboard all works normally...
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.
Configuring gpsd with Wheezy was a breeze. Just had to run "sudo dpkg-reconfigure gpsd", answer a few questions, and it worked like a charm. With Debian Jessie the following happens:
tsi@sxf-tsi:~$ sudo dpkg-reconfigure gpsd Warning: Stopping gpsd.service, but it can still be activated by: gpsd.socket Creating/updating gpsd user account... tsi@sxf-tsi:~$
How does one bring up the gpsd configuration dialog with Jessie?
I've after latest jessie update a problem with service samba restart. If I use "service samba restart", there is a timeout (after long time) and error.
Output of "systemctl status samba.service":
Code: Select all● samba.service - LSB: ensure Samba daemons are started (nmbd and smbd) Loaded: loaded (/etc/init.d/samba) Active: failed (Result: timeout) since Mo 2014-10-20 02:16:57 CEST; 7s ago Process: 6205 ExecStart=/etc/init.d/samba start (code=killed, signal=TERM)
Okt 20 02:16:57 server systemd[1]: samba.service start operation timed out. Terminating. Okt 20 02:16:57 server systemd[1]: Failed to start LSB: ensure Samba daemons are started (nmbd and smbd).
[Code] ....
Whats going wrong. "service samba restart" should bring no error message if the service is not running previously.
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?
