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?
View 9 Replies
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 use debian jessie 8.1 and when i boot it, pc start fsck block clean etc.. but the fsck control is activated every on boot?
View 14 Replies View RelatedWhen 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.
View 4 Replies View RelatedI'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 upgraded a wheezy box in qemu to jessie (without systemd!) and now I didn't get an output from the console to a hostterminal using curses.System and grub starts with terminal output, but after around 6 to 8 lines of output the terminal gets black. As far as I found out it seems that the init process switches to graphical output. I tried out all found kernel options from nomodeset up to nofb,Are their other options to stop switching to framebuffer and graphical mode.
View 0 Replies View RelatedI am self teaching everything I need to develop a home-based web server (linux/apache/php/mysql/html/css/etc...) It's quite an undertaking, but not beyond my abilities. I thought this question could have gone in either the linux - software or linux - hardware forum, and certainly not in the n00b section, but I figured it's best be put in the linux - server forum, since that's what this is related to.
I have been looking into the software and hardware RAID solutions for linux because I wanted to make sure that the boot drive of the web server I set up is mirrored with transparent disk fail/replace/recovery. I mean, setting up a boot drive for RAID1 sounded perfectly logical to me, and why wouldn't it to anybody else? So, since I knew RAID controllers were expensive, I looked into the native software RAID support in linux. My findings have revealed an issue with software raiding a boot drive in not only linux but windows as well. Apparently, if the primary drive fails (not the mirror), you have no other option but to power down the system to properly replace the failed disk, reboot, play some config crap, resync the drive, do some more config crap, reboot again, and -hopefully- it'll be ok. Well, that procedure is simply out of the question since the idea behind RAID is to transparently proceed as if nothing happened.
I'd like to know if it's even possible to RAID1 the boot drive for transparent and automatic fail/hot-swap/recover WITHOUT rebooting the system and with no intervention on my part other then replacing the drive whether it be a software raid or hardware raid solution. Eventually, what I'd like to do for a drive configuration is have 3 RAID volumes on the server configured like so:
RAID volume 1 = boot drive w/ webserver installed
RAID volume 2 = database files
RAID volume 3 = flatfile storage
Each raid volume will be a RAID1 of a 1TB drive (total = 6 x 1TB drives)
I've seen a lot of people having failure issues with the software RAID in these forums. Is this more common than not? I'm certainly not opposed to buying a hardware RAID solution as long as they're reliable and provide transparent/automatic recovery. So what's the best way to RAID1 the boot drive for transparent/automatic failover?
I'm a beginner + in debian (ie I know how to launch basic command under a shell), and I very new to configuration problem.I have a running perfectly file server for probably more than 2 years that I never touch. That's the debian problem, when it's unning, it's forever, no reboot at all.I recently bought 2 new sata drive 1TB5, that I add to my system by adding to my old system a SATA PCI board without any problem.But, one of these 3 month old drive is already dead.So I try to replace it and that's where problem started.....First I did a#mdadm --manage /dev/md1 --remove /dev/sdb1, of course without sucess because sdb is dead
#mdadm --detail /dev/md1
/dev/md1:
Version : 00.90.03
[code]...
We have the following server at collocation: [URL]
Provider's technicians were working for 3 hrs but finally were unable to set up hardware RAID1 on it.
What could prevent them from doing it? Is it difficult to set up RAID1? It is mentionned as basic function in specifications.
They said debian not booting after raid configured...
opensuse 11.2 64 bits installed in a RAID1 software array. Everything worked smooth during installation, the system boots, the mdx partitions are in their places, did the upgrades, configured the way i wanted, booted several times... all ok. Then i wanted to test the RAID and since its RAID1 i just disconnected 1 drive and started the computer. All what i got is
GRUB loading stage 1.5
GRUB loading, please wait...
Error 21
Connect the drive back and the system works ok.
Disconnect the other drive, then i got
GRUB loading stage 1.5
GRUB loading, pleas wait...
(hd1,0)/message: file not found
and a simple boot menu (in character mode) shows up with the 2 options SUSE LINUX and Failsafe -- SUSE LINUX (no version number)
[Code].....
I,ve upgraded Debian Testing to Gnome 3.18, acrivate from Online Accounts file integration of Google service.
In Nautilus left panel i see my Google Drive accounts but is impossible to mount , i have a generic error (impossible to mount position).
How i can fix this?
Same problem on Arch (Laptop).
I am running Jessie 8.2, upgraded from Wheezy about a week ago.
KDE Desktop, static IP
NetworkManager.conf shows:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true
dns=none
The dns=none is to keep NetworkManager from overwriting /etc/resolv.conf (which shows):
nameserver aaa.bbb.ccc.ddd
nameserver aaa.eee.fff.ggg
nameserver aaa.hhh.iii.jjj
search mydomain.com
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...
I installed a raid1 on a debian lenny box with only 1 drive "--raid-devices=1" because I didn't have the other drive yet. When I got the other drive, I used "mdadm --grow /dev/md0 --raid-devices=2" and "mdadm --manage /dev/md0 --add /dev/sdb1" The original drive is sda1. I watched /proc/mdstat until it was completely synced, and after a reboot, the system will not reassamble the raid. It fails with "mdadm: no devices found for /dev/md0" This is where root is, therefore, I get nowhere. From a rescue cd I can disable the other drive and shrink back down to 1 device and it boots fine.
View 1 Replies View RelatedConfiguring 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?
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?
linux-image-3.14-0.bpo.1-amd64
linux-image-3.14-0.bpo.2-amd64
linux-image-3.16-0.bpo.2-amd64
linux-image-3.16-0.bpo.3-amd64
linux-image-3.2.0-4-amd64
How about results shown by deborphan?
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.
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
[code]....
DE: lxde
version: Jessie
using xorg file: no
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):
Code: Select allxrandr --setprovideroutputsource 1 0
xrandr --output VGA-0 --primary --mode 1680x1050 --pos 0x0 --rotate normal
--output DVI-0 --mode 1680x1050 --pos 0x1050 --rotate left
--output HDMI-0 --off
--output VGA-1-1 --off
lxpanelctl restart
Additional info:
Code: Select all$ inxi -G
Graphics: Card-1: Advanced Micro Devices [AMD/ATI] Oland PRO [Radeon R7 240]
Card-2: Advanced Micro Devices [AMD/ATI] Oland PRO [Radeon R7 240]
Display Server: X.Org 1.16.4 drivers: ati,radeon (unloaded: fbdev,vesa)
Resolution: 1680x1050@59.88hz, 1680x1050@59.95hz
GLX Renderer: Gallium 0.4 on AMD OLAND GLX Version: 3.0 Mesa 10.3.2
[Code] .....
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 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:
Code: Select allsudo modprobe -v ./kernel/drivers/edimax/8821au.ko
it seems to work:
Code: Select allbuiltin ./kernel/drivers/edimax/8821au.ko.
But lsmod doesn't show me the module after that.
I also added
Code: Select all./kernel/drivers/edimax/8821au.ko
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.
My laptop fan sensor shows fine in psensor in sid. But today I downgrade to jessie and sensor for fan gone. I check if fancontrol is running but I can not manage to make it work
sensors
Code: Select allacpitz-virtual-0
Adapter: Virtual device
temp1: +55.0°C (crit = +108.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +55.0°C (high = +87.0°C, crit = +105.0°C)
Core 0: +55.0°C (high = +87.0°C, crit = +105.0°C)
Core 1: +54.0°C (high = +87.0°C, crit = +105.0°C)
[Code] ....
I google and have tried but no luck
Code: Select allacpi_enforce_resources=lax
This is an Asus laptop with controllable fan. I am not sure if fan is running by Bios, and how it might run. But I feel the laptop seem quieter and at higher temperature than it was under sid.
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.
View 4 Replies View RelatedI installed jessie 8.1 and wmii ( Version: 3.10~20120413+hg2813-8) and I use a basic wmiirc.
Code: Select all:~/.wmii-3.10$ ls -la wmiirc
-rwxr-xr-x 1 root root 8033 août 1 17:28 wmiirc
If I want to run wmii the system says:Code: Select all:~$ wmii
wmii: fatal: another window manager is already running
Some information :
Code: Select all~$ update-alternatives --config x-window-manager
Il existe 3 choix pour l'alternative x-window-manager (qui fournit /usr/bin/x-window-manager).
Sélection Chemin Priorité État
------------------------------------------------------------
0 /usr/bin/wmii 60 mode automatique
1 /usr/bin/metacity 60 mode manuel
2 /usr/bin/mutter 60 mode manuel
* 3 /usr/bin/wmii 60 mode manuel
I've always used Debian with a single monitor and no need of proprietary drivers, because I usually don't do graphics or multimedia. Now I'm asked to set-up a machine with 3 nvidia video cards (770) and 4 monitors and everything went south. I started with just 2 monitors connected to 2 different video cards, not wanting to push my luck.
I installed a fresh Jessie and followed the instruction to install the nvidia drivers and tools from the Wiki. Everything went smooth. After reboot I executed (as root) nvidia-settings and I configured the two monitors to be one to the right to the other, with BaseMosaic option (at this point just one monitor was active) I saved the configuration to /etc/X11/xorg.conf , I even executed nvidia-xconfig as suggested, I rebooted and nothing happened, only one monitor was working, while the other -- looking again in the nvidia settings -- was still disabled.
I then tried with xinerama option and things are even worse, since now both monitors are black. I can login in one textual shell, but then I don't know what to do, since in my 10+ years of linux ... I never had to mess with X server. Is there a way to at least recover a working X without reinstalling everything?
I'm just completing an upgrade from wheezy to jessie and get the following error
Code: Select allProcessing triggers for initramfs-tools (0.120) ...
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
E: intel-microcode: unsupported kernel version!
With a message like this I'm wondering if it's safe to reboot as well as how to resolve.
Is this somehow related to the change to only update the microcode on boot as reported earlier in the upgrade?
Code: Select allintel-microcode: microcode will be updated at next boot
I installed elog 2.9.2+2014.05.11git44800a72 on my Jessie system. When entering a new post just a simple plain text editing box is shown instead of the WYSIWYG editor, and no drag and drop area for attachments is shown. When I start the elog service with "systemctl start elog" I get this suspect message in the journal: "FCKedit NOT detected".
Indeed, I see that the elog installation creates a symlink which I guess is supposed to point to the fckeditor installation, which nevertheless is missing:
Code: Select allroot@static-3-080:/usr/share/elog/scripts# ll fckeditor
lrwxrwxrwx 1 root root 15 Oct 25 2014 fckeditor -> ../../fckeditor
root@static-3-080:/usr/share/elog/scripts# ll ../../fckeditor
ls: cannot access ../../fckeditor: No such file or directory
I installed ckeditor 4.4.4+dfsg1-3 but his did not fix the problem. I'd say that either the elog package is broken or that it misses a dependency on a package providing FCKedit. Or maybe my system is misconfigured?
