date int64 1,220B 1,719B | question_description stringlengths 28 29.9k | accepted_answer stringlengths 12 26.4k | question_title stringlengths 14 159 |
|---|---|---|---|
1,509,752,415,000 |
I tried to install Debian Stretch (9.4.0) together with desktop environment LXQt.
Hereby I installed a raw and clean system without any additional packages first and then set the recommended and suggested packages to 0 via file /etc/apt/apt.conf.d/10noinstall-recommends.
Afterwards I installed the following (basic) packages via CLI:
xserver-xorg-core
lxqt-core
lightdm
After reboot into the fresh system first problem detected was the fact that my screen freezed during input of log-in data into lightdm. Hereby neither keyboard nor mouse pointer showed any reaction. This problem could be solved by installing the additional package xserver-xorg-input-libinput. Now log-in does not freeze anymore and will succeed.
Second problem was the issue that most of the graphical desktop environment icons are not getting displayed. Therefore I installed the package lxqt-qtplugin, but I could only reach the whole amount of icons when installing the additional icon theme package lxde-icon-theme. This by default integrated icon-theme adwaita-qt5 seems to have some problems I guess?
Third problem is the issue that common users (except root) do not have permissions to log-out, reboot, shutdown etc. the system. As a normal user clicking on the related buttons in the start menue does not have any effect. I am not yet sure how to fix this issue?
Did anyone of you experience similar issues? This did not appear on only one machine, the exactly same things happened when installing this combination into a VM. Maybe LXQt is more in a late beta state than fully reliable at present?
|
The first problem of freezing screen can be solved by installing the package xserver-xorg-input-libinput
Second problem could be solved by switching the icon theme to standard gnome theme, then it worked fine
Third problem was solved by installing the package lxqt-policykit which will install policykit-1 as a dependency
| Debian 9.4.0 (Stretch) with LXQt - anyone experienced the same issues? |
1,509,752,415,000 |
Sometimes after I turn on the desktop PC, randomly one of the 4 cores goes to 100% and the machine "freezes".
Well, I have htop running on it from a remote connection and I can see that all processes are still working.
An interesting thing that happens is ex.: a youtube video will continue playing its audio but the screen becomes all frozen, even the mouse won't change its position.
At the top of the list at htop, this time was kworker with 100% cpu usage, but other times there was no process at 100%. The cpu 1 (core index 0) was at 100%. So, the core 0 was being actively used by about 10% and the remaining bar was all red, filling 'til 100%. I think that red filling indicator is IO wait right?
Then the load average will not stop increasing.
So I guess it is related to some kind of IO, I would guess video IO? What commands I could use to test it?
In this case, I can't even create a new remote connection, it won't accept, will just freeze the attempt. So I will start such command on a loop and monitor its output whenever the next freeze happens.
|
Yes, it is probably video io. Because there is a kworker on 100%, there is also an interrupt overflow.
Interrupts are handled on linux in two steps: 1) the direct interrupt handler collects all of the interrupt data in a temporary queue 2) the workers are working not in the interrupt handlers, but as separate kernel threads. They are essentially processes - but without a user space, they run entirely in kernel.
Is has being so, because the interrupt handlers... interrupt. It can happen any times, ignoring any locks, etc. Thus, they should do as few complex data structure handling, as it is possible. The problem is similar as you can call only a few functions from a user space signal handler. Thus, they collect the interruot data in a queue and then the workers process these queue, already out of the kernel space.
Now the problem is that video chips don't interrupt too much, the task of the video drivers is only to set up a the vga settings and to produce a mapped buffer to screen. They shouldn't interrupt too many, but despite that it happens a lot.
The youtube audio doesn't stop because it is a multithreaded thing and its audio processing thread doesn't even know that the video player is hanged.
What is in your dmesg?
I suspect buggy vga hardware or a driver problem.
| how to determine the origin of: one core to be at 100% and "freeze" the machine? |
1,509,752,415,000 |
I'm using Arch Linux, and I was able to config ncmpcpp to work about three months ago. However today when I open it and press 2 for the Filesystem Browser it freezes while the CPU seems to be working hard (making loud noise). I can not switch to other tabs including back to 1 (Current Playlist). Same problem occurs for 5 (Playlist editor) and 7 (Output selector)
What can possibly caused this and how can I troubleshoot?
Things I tried but didn't help:
Changing the music directory to a much smaller one with about 10 songs and no sub directories
Renaming file database to data.old in the hope ncmpcpp will recreate the database
Inspecting file log in $HOME/.config/mpd - it has no record since three months ago.
Restarting mpd.service
Update mpd and ncmpcpp to the latest version (0.20.4 and 0.7.7 respectively)
|
It turned out the reason it freezes is because I enabled mpd.service globally, which presumably reads the default root configuration /etc/mpd.conf and causes the freezing. Why would root configuration be a problem? I don't know.
Instead I excute systemctl --user mpd.service and it works again.
See https://wiki.archlinux.org/index.php/Mpd#Autostart_with_systemd
Three months ago it worked because I started mpd directly by typing mpd in command line when I logged in as a user.
| ncmpcpp freezes at 2 Filesystem browser, 5 Playlist editor and 7 Output selector |
1,509,752,415,000 |
I've 415 gif files in a directory and trying to make a single pdf of them by using the following command:
convert /path/to/*.gif file.pdf
But it cause for hanging/freezing of the entire system. In other words it makes the system very slower and I've to Ctrl+c (kill) the process (which also consume some time for stopping).
How do I face this issue/problem? Is there any better/alternative mechanism (command/program/work-around) for doing this task?
Note: I'm working on my simple Desktop PC (3+3 GHz P4 processor and 1GB og RAM) with Trisquel GNU/Linux 7.0 LTS. The convert program is a member of the ImageMagick suite of tools.
|
You are probably using a lot of ram and causing swapping. A simple test using /usr/bin/time -v in front of the command when run on say 5 files, and again on 10 files will show that the Maximum resident set size is approximately double for twice as many files.
So rather than doing them all at once, convert them one at a time, or say ten at a time, then concatencate the pdfs. It will take longer, but less memory.
rm -f /tmp/file.pdf
for i in *.gif
do convert "$i" /tmp/a.pdf
if [ -s /tmp/file.pdf ]
then gs -q -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=/tmp/b.pdf /tmp/file.pdf /tmp/a.pdf
else mv /tmp/a.pdf /tmp/b.pdf
fi
mv /tmp/b.pdf /tmp/file.pdf
done
| `convert`ing *.gif to file.pdf hangs/freezes the system |
1,509,752,415,000 |
I am using the latest Ubuntu Linux with a custom kernel (4.2.0-36-generic), in which I have disabled the CONFIG_STRICT_DEVNEM, because I need to dump and search some terms in memory during a project.
However, when using:
dd if=/dev/mem to print it on screen,
dd if=/dev/mem of=/home/user/Documents/file.dump to save it as a file, or
dd if=/dev/mem | hexdump -C | grep 'term' to directly find what I'm looking for,
the system freezes and reboots while in the process.
I have checked with df -h and my disc has plenty of free space. Also, the process always stops after writing a 2.1Gb to 2.5Gb, out of a 8Gb RAM and before reaching addresses that start with 4 (if these make any difference). In addition, checking /var/log/syslog and /var/log/kern.log shows nothing relevant before the freezing.
Also, using parameters bs=1G count=2 successfully copies the first 2GB of the memory but then trying bs=1G count=2 skip=2 to get then next 2GB again freezes the system.
Would you suggest any solution so it is possible to dump the full memory or some other way to directly search terms in memory?
|
I think you may run into some memory area used by PCI/ACPI or some such hardware. There might be a memory mapped device that doesn't like being accessed. I can't tell what address exactly causes the problem, but it's usual for some special areas to be located just under the 4 GB limit.
On one machine with 4 GB memory, the kernel prints the following on boot:
BIOS-e820: 0000000000000000 - 000000000009e400 (usable)
BIOS-e820: 000000000009e400 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000cf690000 (usable)
BIOS-e820: 00000000cf690000 - 00000000cf6e0000 (reserved)
BIOS-e820: 00000000cf6e0000 - 00000000cf6e3000 (ACPI NVS)
BIOS-e820: 00000000cf6e3000 - 00000000cf6f0000 (ACPI data)
BIOS-e820: 00000000cf6f0000 - 00000000cf700000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000130000000 (usable)
Part of the usable memory is above the 4 GB limit at 0x100000000 and there seems to be holes between 0xcf700000 and 0xfec00000.
The areas corresponding to "usable" memory are also shown in /proc/iomem, marked as "System RAM". (the file also contains information about the other memory areas.) You might be safer just reading from those areas.
$ grep "System RAM" /proc/iomem
00001000-0009e3ff : System RAM
00100000-cf68ffff : System RAM
100000000-12fffffff : System RAM
| Accessing /dev/mem freezes Ubuntu |
1,509,752,415,000 |
We have two completely different computers both running Mint 17.2, one Xeon server with ECC memory and the other is an i7 laptop with normal memory. Both have 8GB of RAM with default swap.
Both are used to play a CPU-demanding Flash Player game (~ 50% of CPU) in the latest Google Chrome with the latest integrated Flash Player.
Both have the recommended kernel installed:
$ uname -r
3.16.0-38-generic
The problem is, they both freeze almost every day, with an inability to switch to the console using Ctrl+Alt+F1, so I don't even know what happened.
It could be important that we have AP isolation enabled in our router and SSH is not set-up.
|
Since you have a couple of computers you can access from one computer to the other (if the system is still running and network) using SSH for instance, that way you may be able to check what happened and kill the process/es you need.
From cas comment:
The flash game is probably doing something that is triggering a nasty bug in the video driver or in X.
| Inability to switch to the console using Ctrl+Alt+F1 when Mint freezes |
1,509,752,415,000 |
I have been using F19 for a couple of days until I've decided to do an yum update. Everything went well but after reboot I can't get past the login screen anymore. I enter my username/password, then the login screen disappears and Fedora freezes, displaying only the login screen background image. I've tried logging in through terminal Ctrl+Alt+F3 but after entering my details the terminal just hangs and I can't do anything (I can input commands but there's no reaction).
Do you have any idea how to fix this?
|
My comment was a little long so I'm putting it in an answer; although I have NOT had to do this myself, it's where I would start.
1) Check if there is a previous kernel listed on the grub boot menu. If so, try that one. If that works, all you have to do is edit /boot/grub2/grub.config here:
set default="0"
The 0 is relative to the first entry, so if you want to use the next one down instead, change it to "1".
2) If that does not work, there is the possibility of rolling back an update using yum. It looks to me like the basic idea is you use yum history list to view a table of recent activities (works for me), then you can use yum undo [N] where N is an ID index from the table.
Of course for that, you at least need to be able to boot in to a terminal. If you can ssh, you could try that. If there is a "rescue mode" option in your grub menu, try that. Otherwise, boot a live CD and mount your partition so you can change from a graphical boot to a console boot (might help...).
That means changing the /etc/systemd/system/default.target symlink, which right now is to /usr/lib/systemd/system/graphical.target. As root:
rm /etc/systemd/system/default.target
ln -s /usr/lib/systemd/system/multi-user.target /etc/systemd/system/default.target
And reboot...
| Fedora 19 freezes after login |
1,509,752,415,000 |
I have this strange issue. scp is hard locking my server.
I have tried memcheck, tried downloading big files using wget, tried speed test in openssl and everything works just fine, yet every time I try to copy something (from or to the machine) using scp, it hard locks the machine.
Not even sysrq magic key combos work.
What could be the cause of this? I have no idea where to look.
Edit: I just managed to crash the system using nfs server.
|
I suspect there's an obscure bug in either your Ethernet driver, or your Ethernet device's firmware or hardware. Can you trigger the bug by scp'ing to localhost? If not, try replacing the components:
upgrade your network device's firmware, in case the firmware is at fault;
try another network device (e.g. plug in a PCI Ethernet board), in case the firmware or hardware is at fault;
try a different driver version, in case the driver is at fault or the other version manages to work around a firmware bug.
| scp hardlocking my server (both ways) |
1,509,752,415,000 |
On my main home computer I am running fedora 39. It was not originally running fedora 39, I've upgraded through at least 2 previous releases.
My problem is that every few hours my system either completely freezes, or I still can move the mouse around the screen but cannot do anything else. I cannot Ctrl-Alt-F* do drop to a console or anything like that, the only solution is to reboot.
I've been dealing with this problem for years, I have a feeling it is related to my graphics card (AMD Radeon 5700 now, but I had an AMD RX 480 in the past in the same computer with similar issues) , but I do not remember where that feeling comes from.
On each new boot, I take a peek at the end of journalctl -k -b -1 but I don't see anything repeating there across occurrences, or anything that draws my attention.
I've recently updated my BIOS , but that doesn't seem to have improved anything
I wanted to say that I have kernel dumps enabled but nothing was ever recorded in /var/crash, however I now see I have a dump from november, looking through the dmesg log there I see
[ 7082.889352] BUG: kernel NULL pointer dereference, address: 0000000000000000
[ 7082.889361] #PF: supervisor read access in kernel mode
[ 7082.889366] #PF: error_code(0x0000) - not-present page
[ 7082.889370] PGD 0 P4D 0
[ 7082.889377] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 7082.889384] CPU: 11 PID: 0 Comm: swapper/11 Kdump: loaded Tainted: G OE 6.5.9-200.fc38.x86_64 #1
[ 7082.889391] Hardware name: Micro-Star International Co., Ltd MS-7B00/B350 GAMING PRO CARBON (MS-7B00), BIOS 1.50 08/02/2017
[ 7082.889395] RIP: 0010:dc_stream_get_scanoutpos+0x5b/0x80 [amdgpu]
Maybe I've seen something like this in the past and that is why I suspect amdgpu. But again, I get freezes daily while apparently I only had a kernel bug once, months ago.
Thank you for reading so far, my question is: Does anyone have any ideas about how I can use software to track down the problem?
The only idea I have is to start swapping out hardware and see if that fixes anything, but that will cost and if I go down that way, I might as well upgrade my computer, which I'd like to not do for a few more years.
Thank you very much
|
A while back on my Fedora machine I had exactly the same problem that you described. I would be using my computer then it would randomly freeze but usually the mouse would continue to move.
Initially I thought there was a problem with my Asus GeForce 8800 GT graphics card. However I removed the graphics card and I still had a these random freezes.
Nothing in the logs because I had to reboot.
I had a copy of memtest86 so I decided to run a test on the memory and as soon as I started running Memtest86 I got a lot of errors.
So I was thinking that either one of my memory banks was badly seated or had developed an error.
I checked the seating of the memory sticks and everything was ok. However I noticed there as a lot of dust in one particular area of the memory stick nearest the the processor fan. I removed all the memory sticks and carefully vacuum cleaned the memory modules as well as the memory sticks and reseated the memory sticks back in the modules. From then on I've not had any random freezes.
Perhaps your problem is the same and running Memtest86 is very simple. Download the right version if you boot from bios as opposed to uefi. Let us know how it goes.
| Finding the cause of system freezes - Fedora 39 |
1,509,752,415,000 |
Whenever I'm trying to boot the Debian 11 is getting stuck at the following
Welcome to Debian GNU/Linux 11 (bullseye)!
systemd[1]: Set hostname to <arm>.
systemd[1]: Failed to open netlink: Function not implemented
systemd[1]: Failed to allocate device monitor: Function not implemented
systemd[1]: Failed to allocate notification socket: Function not implemented
systemd[1]: Assertion '*_head == _item' failed at src/core/device.c:46, function device_unset_sysfs(). Aborting.
systemd[1]: Caught <ABRT>, dumped core as pid 799.
systemd[1]: Freezing execution.
|
Is the system originally installed as Debian 11, or has it been upgraded from an earlier release of Debian?
The fact that you are reaching the "Welcome to Debian..." message suggests the system is getting past the initramfs phase and reaching the real root filesystem, but on transitioning from the initramfs's mini-systemd to the real full-featured one, things quickly go wrong.
It certainly looks like systemd is trying to use some kernel features but is getting back "Function not implemented" errors, and then triggering an assertion.
(Assertions are primarily a development tool and they should never be a primary error-checking mechanism on a production-grade software. If a critical system component like systemd is hitting assertions, it means something is wrong in some way the developer did not really consider worth writing error messages for. If you can find out the root cause of your problem, you might want to create a bug report for systemd, describe what caused you to get here, and suggest a better error message.)
This might happen as a result of a failed upgrade, with the system attempting to run on a mix of old and new libraries, but normally the package dependencies should make such a situation impossible. Maybe if the system has crashed mid-upgrade at exactly the wrong time?
Perhaps you have added some package repositories that are incompatible with Debian 11, and the package management system has replaced some of the system's normal software packages with ones from the incompatible repository, and now the system cannot work as a result. In other words, you may have made a FrankenDebian: a freakish combination of unrelated, mutually incompatible packages.
A third possibility is if you have installed a custom kernel: it would then appear that your minimalist kernel configuration was too minimal, and some kernel features that are necessary for systemd to function were completely disabled.
Whatever the reason might be, the fact is the issue causes systemd (the process #1 on the system) to fail, which makes most ways to access the system non-viable. If you have installed a custom kernel, but still have a standard kernel installed, try telling your bootloader to boot the standard kernel instead. (I see your hostname is "arm". If it means you are using a processor of the ARM architecture, I think your bootloader might not necessarily be GRUB, but something else.)
Otherwise, you might try adding a boot parameter init=/bin/bash to give you a single shell session running as root as process #1: if this works, you can at least get some access to the system (while in a read-only state) to gather more information. In such a state, all of the normal userspace start-up processes are not executed, so you will have to do everything manually: that includes getting the root filesystem out of read-only mode, mounting any other filesystems as needed, and configuring any network interfaces if you need them.
If the mount command works, you could then do a mount -o remount,rw / to get write access to the root filesystem; then, if the package management tools are working, you could look at /var/log/dpkg.log to figure out which packages were updated or removed recently, and would have a chance of undoing the most recent package operations, which might have caused the problem. If the network configuration commands don't work at this point, you might have to download any necessary packages on a different computer and transfer them to this computer on a USB stick or other removable media.
If a large number of packages has been replaced/removed recently, and/or you find the package management tools don't work, you might have reached the point where it's going to be simpler to just backup any salvageable data files and reinstall the system.
| What should be the reason for debian getting stuck at Assertion '*_head == _item'? |
1,509,752,415,000 |
I am a software developer and I come into contact with a lot of unstable software.
Recently I made a small game, which for some reason memleaks until the system hangs and is unresponsive. Usually, REISUB helps, but sometimes not even that and you need to do a hard poweroff.
Then it happened to me again with another program, so I thought to myself that this could easily be prevented by writing a script that monitors mem usage and if it crosses a certain value per PID over a certain amount of time, it gets a SIGKILL to take it down immediately.
Any ideas?
Thanks
|
Simple idea: check if memory exceeds a given value, and check again after some time. Hand out strikes, three strikes in a row will lead to a kill. Need to know: PID of process
#!/bin/bash
pid=$1
strike=0
#as long as process exists
while (kill -0 $pid 2>/dev/null) ; do
#get RAM usage in kB
ram=$(pmap -x $pid | tail -1 | awk '{print $3}')
#compare to threshold, 1,000,000kB
if [[ 1000000 -lt $ram ]] ; then
strike=$((strike+1))
if [[ strike -eq 3 ]] ; then
kill $pid
exit
fi
else
strike=0
fi
sleep 5
done
| Kill process if it takes more than xGiB of RAM in a given amount of time |
1,509,752,415,000 |
Its really annoying - every now and then the desktop completely freezes and sometimes even the UI look like a tetris game or something. And the keboard and mouse cannot be used so I have to use a SSH client from my android (Juice) to kill the userprocess i.e log out. This means I lose all open applications and not the least time. Counting the times the last hour this occurred 5 times, mostly when a webbrowser is open but the freezing is very very erratic.
According to the syslog the opensource nouveau-driver seems to be involved and my question is how I can get rid of this annoying problem? I have googled pretty much about the issue and the problem seems to be more or less common but I cannot find any trustly solution. For instance - can I replace the nouveau-driver for NVIDIA's or is it risky? Please, if there is a safe strategy I would be more than happy. Any other solution such as changing desktop? If those solutions are bad - and the desktop freezes, is there any other bash commands than the following:
pkill -KILL -u user
output from inxi -Fxz
System: Host: mx Kernel: 4.19.0-11-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: Xfce 4.14.2 Distro: MX-19.2_x64 patito feo May 31 2020
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: Dell product: XPS 8700 v: N/A serial: <filter>
Mobo: Dell model: 0KWVT8 v: A03 serial: <filter> BIOS: Dell v: A08 date: 04/16/2014
CPU: Topology: Quad Core model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell
rev: 3 L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57466
Speed: 1197 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 1197 2: 1198 3: 1198
4: 1197 5: 1195 6: 1199 7: 1199 8: 1198
Graphics: Device-1: NVIDIA GK208 [GeForce GT 720] driver: nouveau v: kernel bus ID: 01:00.0
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 2560x1440~60Hz
OpenGL: renderer: NV108 v: 4.3 Mesa 18.3.6 direct render: Yes
Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Device-2: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k4.19.0-11-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell
driver: r8169 v: kernel port: d000 bus ID: 03:00.0
IF: eth0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: Dell driver: ath9k
v: kernel port: d000 bus ID: 04:00.0
IF: wlan0 state: up mac: <filter>
Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-13:5
Drives: Local Storage: total: 1.36 TiB used: 9.25 GiB (0.7%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB temp: 32 C
ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO mSATA 500GB size: 465.76 GiB
Partition: ID-1: / size: 287.37 GiB used: 9.25 GiB (3.2%) fs: ext4 dev: /dev/sda3
Sensors: System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 62 C
Fan Speeds (RPM): N/A
Info: Processes: 249 Uptime: 20h 54m Memory: 15.62 GiB used: 1.79 GiB (11.5%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36
screenshots
1
2
3
|
TL;DR
You can replace it, and it's ok.
Step to do:
switch off nouveau.
install proprietary nvidia, link
remove nouveau.modeset = 0
Yes you can replace the nouveau-driver and I suggest you to do so if you cannot fix the build in ones. you can turn off nouveau by clicking e when you are in grub (which you may select run linux or recovery or other os). after that, you need to add nouveau.modeset = 0 in linux line (tips, you can click end key in keyboard to move cursor to the end of line). and then, you can click X which means run the current grub setup temporarily.
You may also set grub permanently by editing /etc/default/grub with string I mention above ― nouveau one. but you need to run sudo upgrade-grub after that.
after that, you can install proprietary driver. there is bunch of tutorial in the search engines. because you use debian, maybe you can refer this site.
if nvidia driver is successfully installed, make sure to remove the nouveau.modeset if edit the /etc/default/grub
| Linux desktop freezes caused by Nouveau driver |
1,509,752,415,000 |
Sorry if I'm not formatting this question correctly - I've never used StackExchange before - but I need some help with my Ubuntu freezes/crashes.
Since getting this distro (and especially since getting Regolith) I've been having a great experience on my laptop, and have been finding that I'm using a lot less memory and other system resources than I used to making all my programs run smoothly. However, for some reason, my system completely freezes almost every day at this point with no functionality whatsoever (not even allowing REISUB), leaving me with no choice but to hard reboot it every time. I generally don't lose much work and can get started again quickly, but I know doing this kind of thing a lot can really damage a system.
While I'm not entirely sure what the cause of this is, I have noticed that it always occurs after a few minutes or more of inactivity, and soon after returning to the laptop pressing the 'Play' button in an application such as RhythmBox or LMMS. Does anyone know why this might be, and how I could fix or avoid it?
Thanks in advance, Dominic
|
Sorry this is a late reply, I was doing a lot of testing to make sure I'd fixed the problem and forgot to check back on this. It turns out the Bluetooth speaker connection was messing up the system for some reason, so I tried connecting the speaker to my laptop headphone port manually (with a certain type of wire, I've forgotten what it's called now though). After a few days of playing music, videos, etc I haven't had a single crash, and I'm not even getting the slight audio jittering that used to be happening (;
I know this isn't really a fix, as clearly there's something wrong with the Bluetooth drivers or Acer hardware. However, I'm finding this solution satisfactory, and I hope it'll help anyone with problems like mine who looks at this in the future.
| Daily Ubuntu freezes following certain behaviour |
1,509,752,415,000 |
My system freezes and the only solution is to force shutdown it. I'm not sure but maybe the problem is due chromium-vaapi , any missconfiguration or something.
I'm in 5.4.13-arch1-1 #1 SMP PREEMPT.
Here my journalctl with the freeze.
Thanks a lot.
|
Actually, this is a GPU driver bug. It's already in your paste.
ene 22 18:59:01 dlag-pc kernel: i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0
ene 22 18:59:01 dlag-pc kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
ene 22 18:59:01 dlag-pc kernel: Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
ene 22 18:59:01 dlag-pc kernel: drm/i915 developers can then reassign to the right component if it's not a kernel issue.
ene 22 18:59:01 dlag-pc kernel: The GPU crash dump is required to analyze GPU hangs, so please always attach it.
ene 22 18:59:01 dlag-pc kernel: GPU crash dump saved to /sys/class/drm/card0/error
ene 22 18:59:01 dlag-pc kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
ene 22 18:59:01 dlag-pc kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
ene 22 18:59:01 dlag-pc kernel: i915 0000:00:02.0: Resetting chip for hang on rcs0
ene 22 18:59:01 dlag-pc kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
The bug is known to affect kernel:5.3 & kernel:5.4. It's already resolved in kernel:5.5 tree.
| System completly freezes often (maybe chromium-vaapi) |
1,708,708,060,000 |
I've come across a strange enough problem in the past days that I need to write my question down here.
I have a dual boot setup with Ubuntu on one NVME and Windows on the other. The Bootmanager is installed on the Ubuntu drive so I always start that first and then go to Windows from there. The Ubuntu system is used for work while I use Windows primarily for Hobbies and Gaming.
The whole system (CPU+GPU) is water-cooled.
I had the problem of Ubuntu freezing roughly once a day for a few weeks or even months now but it didn't really bother me enough to do something about it.
A few days ago, after taking everything apart, cleaning the water-cooling loop and putting all the hardware back together the freezing appeared way more frequently. I can't really keep the system running for more than an hour without it freezing completely up. And it's completely frozen then, programs stop, the cursor stops and even the clock stops going. Sometimes I can still hear people talking over Zoom for some more time.
I tried reseating the RAM and changing the slots so far but that did not make a difference.
I also tried reinstalling Ubuntu once which also did not make much of a difference.
I then thought there was an issue with the graphics card maybe and I took that one apart again this afternoon to retighten all the screws and make sure that I applied the correct amount of thermal paste which I seem to have.
After about 50 minutes of the system running a complete freeze occurred again.
All of this would indicate some sort of hardware issue with the GPU to me, but there does not seem to be any issue when running Windows. I played some games over the weekend for multiple hours nonstop (some of which are quite demanding) but no issue occurred.
Does anybody have any ideas on how I can fix that issue or even possibly find out what the problem is? I wasn't able to find any logs which could tell me what the problem is but I am also not too experienced with reading them so that could just be on me
Additional information:
All the components are running on the stock clocks and I did not do any overclocking. RAM was tested with XMP on and off.
The GPU is staying below 50°C and the CPU is staying between 60°C and 70°C.
Both components get hotter while gaming but there are no crashes or freezes while doing so
Used drivers:
I have so far tried nvidia-driver-525, nvidia-driver-520 and nvidia-driver-510 which all lead to freezes.
Sometimes the whole PC freezes at once but some other times only applications are affected first (not being able to add more text input) before the clock and cursor freezes eventually.
|
I eventually resolved the problem by replacing Motherboard CPU and RAM.
RAM was most likely not the issue but I wasn't able to test the Motherboard and CPU individually and the new board had DDR5 now.
| Ubuntu freezes after hardware reinstall |
1,708,708,060,000 |
Good day!
Trying to install linux on new SSD but everytime, no matter what i do, even in LiveCD linux freezes and i have to restart PC from button.
Tried to install PopOS, Fedora and Debian. Also used Ubuntu livecd.
PopOS just freezes before installing
Fedora one tried to install, got bootloader error(i think because i used automatic disk partitioning and needed to make /boot/efi manually). But then LiveCD just freezed to death..
Debian installed successfully, but got kernel-panic when i tried to apt-get update && apt-get upgrade. Then freezed to death.
Ubuntu LiveCD worked well for little more time than others, but got death freeze when i tried to use GParted
So, the question is, does LiveCD has logs? How i can find a reason of this freeze?Definately this is drivers problem.
Hardware:
Gigabyte B450 Gaming X
AMD 3500X
GeForce 1650
2 HDD(file storage NTFS), 2 SSD 2.5(one for windows NTFS and one for linux ext4+efi boot partition) and one M2(NTFS for games)
Linux freezes almost everytime i try to do disks operation(like partitioning). But i tried to do it only with SSD for linux(ext4)...
Only thing that i got in mind, is that i need to debug this debian kernel-panic, at least installed system has logs.
|
I think i found the problem. First i discovered, that PopOS runs smooth with only one RAM stick. 2 sticks on dual-channel or on single-channel - leads to crash.
So if you having such problem, try to look for X.M.P(extreme memory profile) in your BIOS Another info that i found, but not tried - increase RAM voltages a bit, be careful it can damage your PC, read guides before doing that. Enabling XMP worked for me.
| Linux freezing after few minutes of using |
1,708,708,060,000 |
I have been working on installing dual boot on my Acer Nitro AN515-51 laptop (with pre-installed Windows 10) for several days now, and am hoping some of you Linux gurus can help a very frustrated (but determined) newbie out.
TLDR:
I reinstalled Debian on a dual boot Windows 10 computer, but both the original Debian install and the new Debian freezes when I try to reboot the computer.
System specs
Graphics: Nvidia GeForce GTX 1050 ( 4GB VRAM); Intel UHD Graphics 630.
RAM: 8GB SDRAM (DDR4)
HD: 256MB Solid State Drive
lscpu | grep -i model reports this:
Model: 158
Model name: Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
There are 5 partitions on the disk:
/dev/nvme0n1p1 100MB EFI System Partition (FAT32)
/dev/nvme0n1p2 16MB Microsoft reserved
/dev/nvme0n1p3 134.6GB Microsoft basic data (NTFS)
/dev/nvme0n1p4 1GB Windows recovery environment (NTFS, hidden)
/dev/nvme0n1p5 102.8GB Linux filesystem (ext4)
My Windows 10 has always been UEFI enabled and Secure Boot enabled and the disk is GPT. I disabled 'Fast Startup' just in case it would cause issues.
DESCRIPTION of issue:
This computer previously had Debian 10.1 installed (by a friend, not by me), but I decided to reinstall it due to a rebooting issue where it would freeze upon attempting to restart through the GUI. When I tried to fix this issue, I broke Debian and was no longer able to login. I actually successfully reinstalled Debian, only to get this same rebooting issue (freezing when I try to restart through GUI).
Here are the steps I took to install Debian 10:
I first used Rufus 3.10 to create a bootable USB thumb drive. I tried several different .iso's. These were all created with GPT partition scheme, UEFI, FAT32. The first one I tried was the debian-10.4.0-amd64-netinst. This turned out to be missing some firmware that my hardware required to operate (which had to do with my Qualcomm Atheros QCA6174A wireless network adapter) which I added. I got all the way to the installing GRUB bootloader step. This is when I got an error saying that the GRUB bootloader did not install properly. The exact error I get is:
`Unable to install GRUB in dummy. Executing 'grub-install dummy' failed. This is a fatal error.'
I try to install anyway. It says I will need to boot manually with the /vmlinuz kernel on partition /dev/nvme0n1p5 and root=/dev/nvme0n1p5 with quiet passed as a kernel argument.
I then tried installing from a Debian 10.4 Live .iso with Cinnamon DE. After Debian Live booted up, I used Calamares to install Debian. I made sure to mount the EFI System Partition (ESP) to /boot/efi and that it is marked both as efi and boot and that the bootable flag is on. I did not format it. I set partition 5 as ext4 and mount root as /. I did format this partition. Then I proceeded with the install. I again get the same error that I got previously about not being able to install GRUB bootloader. I also get the error:
Installation failed
Command `grub-install --target=x86_64-efi --efi-directory=/boot/efu --bootloader-id=Debian -force` returned non-zero exit status 1.
Installing for x86_64-efi platform.
grub-install: warning: Cannot set EFI variable Boot0004.
grub-install: warning: efivarfs_set_variable: writing to fd 8 failed: No space left on device.
grub-install: warning: _efi_set_variable)mode: ops->set_variable() failed: No space left on device.
grub-install: error: failed to register the EFI boot entry: No space left on device.
I try this same process with Debian Live Mate, but same issue with grub bootloader installation. Debian didn't even show up on the boot menu options, only Windows Boot Loader.
Third time, I use Debian Live non-free CD .iso with Cinnamon. This comes with all the missing firmware so I can connect to my wireless network. I then login to the terminal to clear the dump files via sudo rm /sys/firmware/efi/efivars/dump-* And finally, Debian 10 is installed successfully. However, when I try to restart, again computer instantly freezes. I have manually reboot, and as Debian is starting up, I get messages such as 'problems loading UEFI' but it's so quick that I can't really read what it says.
I just want to restart my laptop properly through the GUI!
Does anyone have any suggestions as to what might be the problem here?
Thanks in advance :)
EDIT 1
I upgraded my Linux kernel by following the instructions in this Youtube video:
https://www.youtube.com/watch?v=_9UqAcVMro8
But the rebooting issue is still not resolved. Back to the drawing board...
EDIT 2
After running sudo dmesg -T, I don't see any error messages about UEFI. I do see a lot of messages about nouveau. One of them says WARNING: CPU: 3 PID: 151 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf1000.c:07 gf100 vmm flush +0x14e/0x190 [nouveau]
sudo journalctl does show the error messages that I always see when I boot up Debian, right before the login screen.
Problem loading UEFI:db X.509 certificate (-65)`
Also see these errors:
Lockdown: Hibernation is restricted; see https://wiki.debian.org/SecureBoot
wmi_bus wmi_bus-PNP0C14:01: WQ data block query control method not found
r8169 0000:03:00.1: can't disable ASPM; OS doesn't have ASPM control
ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20180810/nsarguments-66)
ACPI Warning: \SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20180810/nsarguments-66)
[Firmware Bug]: ACPI(PEGP) defines _DOD but not DOS
|
I am posting my solution in case someone else experiences the same issues as me.
I should also mention that on top of the rebooting issue, my computer started to freeze whenever I opened Firefox. This was after I did a sudo apt-get update and sudo apt-get upgrade
I fixed both of these issues by simply disabling nouveau kernel drivers.
| Debian 10 freezes when I try to reboot (dual boot machine) |
1,708,708,060,000 |
I run a CentOS 7 on VM11.The problem is whenever I type a letter on the file browser to activate search function that particular GUI stuck (but not other ones). Then I have to use Ctrl+Alt+F2 the kill the PID called"tracker-store" to unstuck the program.Any idea what might cause this issue?should I reinstall anything?
I also realize the hard drive reading speed is a bit slow under VM environment but still acceptable.
Here you can see the cpu usage is not very high either does it consume much memory.
|
Ok here is how I disable the gnome indexer.The issues seems disappeared. I don,t know how it worked and still wish someone can come up with an answer with more explanation.
In terminal:
[yourname@localhost ~]$ sudo yum install tracker-preferences
Password: ****
In desktop gui:
click search and indexing
uncheck everything and delete every thing
Test and works!
| Stuck on "tracker-store" during search file CentOS 7 |
1,485,483,815,000 |
I just found out that my mother had several virtualbox packages installed. But not virtualbox itself.
Namely, if I remember correctly, these three:
virtualbox-guest-dkms
virtualbox-guest-utils
virtualbox-guest-x11
And yes, these were installed on the host.
As she never used virtualbox, I probably installed it along with these packages long ago for testing purposes. And forgot to remove these packages along with virtualbox itself.
The question is:
Could this be the cause of system freezing? Well, I am unsure, if the whole system freezes. But the screen freezes almost every day. I am not at the machine, so I don't know if she could just press Ctrl+Alt+Backspace to restart the display manager.
She told me just now, that it happens regularly, almost daily, and she just presses the power button for a few seconds. Oh my god, I say.
So far I found these "suspects" and removed them.
Could you tell me what to look for further and where?
The system is Linux Mint 18.1 Cinnamon 64-bit.
|
There were multiple issues with this computer:
installed guest packages on the host system; removed
bad SSHD disk; replaced
swappiness was at standard value of 60, but as this computer uses normally 6 GB of RAM and has 8 GB RAM, it was swapping like crazy; set to 1
kernel was causing some of the issues; upgraded
Situation is now under control.
| virtualbox-guest-* installed on the host; could this be the cause of system freezing? |
1,485,483,815,000 |
I've got a strange problem with my dell Latitude E6530: everytime I put it to suspend mode (closing the lid, as per Power Manager configuration) and the virtualization daemons (libvirtd and virtlogd) are running the computer goes to suspend but at the last moment when the power led should blur out and in, the computer locks up and doesn't suspend. The screen is still powered, there's no disk activity. I've had this issue a couple of times now. I only know that it does not happen when the virtualization daemons are not running — no idea whether/why there should be a relation. Everytime I start libvirt services and try to close the lid, the laptop freezes while going to suspend mode. The only way out is to hard power off the beast for the magic Sysreq key doesn't work.
I'm runnig Manjaro 16.0 and Linux kernel 4.4.13-1 with proprietary nVidia drivers. Does anyone have an idea what's going on?
|
A couple of updates later (now with kernel version 4.4.17-1) and the problem seems to have disappeared. I guess that was a bug in the kernel but I'm still not quite sure. Time will tell.
| My Dell Latitude freezes upon suspending if libvirtd/virtlogd is running |
1,485,483,815,000 |
I just bought a E350M1 mainboard with onboard AMD Radeon 6310 Graphics Card.
I did (I think I did) the UEFI-Bios trick:
CSM activated
and plugged-in a usb-stick with an Ubuntu 13.10 Desktop i386 (made with lili Live USB Creator).
Unfortunately I got a screen like this:
I cant see a menu, I am only able to reboot via Ctrl+Alt+Del
I have no hd/cd/dvd/br/floppy only usb.
Any ideas?
|
Linux Mint 16 works.
Unfortunately I need to wait for release of other distributions.
| Blue gradient line on top and bottom instead of Ubuntu-USB-Grub-Screen |
1,485,483,815,000 |
Our Java application plays short notification sounds periodically (in response to user actions). On some hardward, our application will lock up after the 3rd or 4th short sound. We have to pkill java to recover.
We have the application installed on around 40 computers. All are running Linux. Half have Kubuntu 12.04 installed, half have Linux Mint 11 installed. All the Linux Mint 11 machines work fine and the Java app plays sound without locking up.
Initially (from the release of 12.04) all the Kubuntu machines also worked fine.
At some point, after an update, the Kubuntu machines started locking up when sound was played. If we turn off the sound notification option in our application, that is a workaround. The app will not lock up. But users want the sound.
When we discovered the problem, we stopped running updates on the Kubuntu machines and all those without updates (from months ago) continue to play sound from our app without the app freezing.
Even on the updated Kubuntu machines, lock up problem does not occur on all hardware. For example, on a Thinkpad X220 tablet, sound in our app works without problems. But on a ThinkPad E430, enabling sound in our app causes our app to freeze.
We cannot discover the pattern. What is causing the lockups on a recent Linux and some hardware while the older Linux is fine on all hardware we use?
Here's the info on some hardware where we do have the problem:
uname -a
Linux mynetbook-AO532h 3.2.0-41-generic #66-Ubuntu SMP Thu Apr 25 03:27:11 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
################################################################################
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
################################################################################
aplay --list-devices
Home directory /home/myuser not ours.
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Pro [Sound Blaster X-Fi Go! Pro], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
################################################################################
aplay --version
aplay: version 1.0.25 by Jaroslav Kysela <[email protected]>
################################################################################
cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0x58200000 irq 44
1 [Pro ]: USB-Audio - Sound Blaster X-Fi Go! Pro
Creative Technology Ltd Sound Blaster X-Fi Go! Pro at usb-0000:00:1d.1-1, full
################################################################################
hwinfo --sound
process 2393: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file ../../dbus/dbus-errors.c line 282.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
11: PCI 1b.0: 0403 Audio device
[Created at pci.318]
Unique ID: u1Nb.ZCVQnTUjxO7
SysFS ID: /devices/pci0000:00/0000:00:1b.0
SysFS BusID: 0000:00:1b.0
Hardware Class: sound
Model: "Intel 82801G (ICH7 Family) High Definition Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x27d8 "82801G (ICH7 Family) High Definition Audio Controller"
SubVendor: pci 0x1025 "Acer Incorporated [ALI]"
SubDevice: pci 0x0349
Revision: 0x02
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0x58200000-0x58203fff (rw,non-prefetchable)
IRQ: 44 (262 events)
Module Alias: "pci:v00008086d000027D8sv00001025sd00000349bc04sc03i00"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
################################################################################
lsmod
Module Size Used by
joydev 17693 0
rfcomm 47604 0
bnep 18281 2
bluetooth 180153 10 rfcomm,bnep
parport_pc 32866 0
ppdev 17113 0
acer_wmi 28418 0
sparse_keymap 13890 1 acer_wmi
snd_hda_codec_realtek 224173 1
snd_hda_intel 33719 3
snd_hda_codec 127706 2 snd_hda_codec_realtek,snd_hda_intel
snd_usb_audio 122982 2
snd_pcm 97275 3 snd_hda_intel,snd_hda_codec,snd_usb_audio
snd_hwdep 17764 2 snd_hda_codec,snd_usb_audio
snd_usbmidi_lib 29476 1 snd_usb_audio
arc4 12529 2
snd_seq_midi 13324 0
snd_rawmidi 30748 2 snd_usbmidi_lib,snd_seq_midi
snd_seq_midi_event 14899 1 snd_seq_midi
cp210x 21898 0
usbserial 47077 1 cp210x
ath9k 132428 0
uvcvideo 72627 0
psmouse 97485 0
snd_seq 61929 2 snd_seq_midi,snd_seq_midi_event
videodev 98259 1 uvcvideo
mac80211 506862 1 ath9k
serio_raw 13211 0
v4l2_compat_ioctl32 17128 1 videodev
ath9k_common 14053 1 ath9k
ath9k_hw 411239 2 ath9k,ath9k_common
snd_timer 29990 2 snd_pcm,snd_seq
ath 24067 3 ath9k,ath9k_common,ath9k_hw
snd_seq_device 14540 3 snd_seq_midi,snd_rawmidi,snd_seq
cfg80211 205774 3 ath9k,mac80211,ath
snd 79041 21 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_pcm,snd_hwdep,snd_usbmidi_lib,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 15091 1 snd
snd_page_alloc 18529 2 snd_hda_intel,snd_pcm
mac_hid 13253 0
lp 17799 0
parport 46562 3 parport_pc,ppdev,lp
usbhid 47238 0
hid 99636 1 usbhid
i915 477763 3
drm_kms_helper 46978 1 i915
drm 241971 4 i915,drm_kms_helper
atl1c 41718 0
i2c_algo_bit 13423 1 i915
wmi 19256 1 acer_wmi
video 19651 1 i915
################################################################################
cat /etc/modprobe.d/blacklist.conf
# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.
# evbug is a debug tool that should be loaded explicitly
blacklist evbug
# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd
# replaced by e100
blacklist eepro100
# replaced by tulip
blacklist de4x5
# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394
# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m
# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2
# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801
# replaced by p54pci
blacklist prism54
# replaced by b43 and ssb.
blacklist bcm43xx
# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps
# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi
# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp
# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr
# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac
################################################################################
cat /etc/modprobe.d/alsa-base.conf
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet --use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet --use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }
# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
################################################################################
lspci -vvx
[snip]
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
Subsystem: Acer Incorporated [ALI] Device 0349
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 44
Region 0: Memory at 58200000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee0300c Data: 4179
Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [100 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=1 ArbSelect=Fixed TC/VC=80
Status: NegoPending- InProgress-
Capabilities: [130 v1] Root Complex Link
Desc: PortNumber=0f ComponentID=02 EltType=Config
Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB- LinkType=MemMapped LinkValid+
Addr: 00000000fed1c000
Kernel driver in use: snd_hda_intel
Kernel modules: snd-hda-intel
00: 86 80 d8 27 06 04 10 00 02 00 03 04 10 00 00 00
10: 04 00 20 58 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 49 03
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00
[snip]
Here's a similar report for a machine that does not exhibit the problem:
uname -a
Linux netbook-Gate 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC 2013 i686 i686 i386 GNU/Linux
################################################################################
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
################################################################################
aplay --list-devices
Home directory /home/me not ours.
**** List of PLAYBACK Hardware Devices ****
card 0: ICH6 [Intel ICH6], device 0: Intel ICH [Intel ICH6]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH6 [Intel ICH6], device 4: Intel ICH - IEC958 [Intel ICH6 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Pro [Sound Blaster X-Fi Go! Pro], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
################################################################################
aplay --version
aplay: version 1.0.25 by Jaroslav Kysela <[email protected]>
################################################################################
cat /proc/asound/cards
0 [ICH6 ]: ICH4 - Intel ICH6
Intel ICH6 with Cx20468-31 at irq 21
1 [Pro ]: USB-Audio - Sound Blaster X-Fi Go! Pro
Creative Technology Ltd Sound Blaster X-Fi Go! Pro at usb-0000:00:1d.0-1, full
################################################################################
hwinfo --sound
process 2510: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file ../../dbus/dbus-errors.c line 282.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
18: PCI 1e.2: 0401 Multimedia audio controller
[Created at pci.318]
Unique ID: r0Vg.2VcHkXp8YSA
SysFS ID: /devices/pci0000:00/0000:00:1e.2
SysFS BusID: 0000:00:1e.2
Hardware Class: sound
Model: "Intel 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x266e "82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller"
SubVendor: pci 0x107b "Gateway 2000"
SubDevice: pci 0x0365
Revision: 0x04
Driver: "snd_intel8x0"
Driver Modules: "snd_intel8x0"
I/O Ports: 0x1c00-0x1cff (rw)
I/O Ports: 0x18c0-0x18ff (rw)
Memory Range: 0xb0040800-0xb00409ff (rw,non-prefetchable)
Memory Range: 0xb0040400-0xb00404ff (rw,non-prefetchable)
IRQ: 21 (58 events)
Module Alias: "pci:v00008086d0000266Esv0000107Bsd00000365bc04sc01i00"
Driver Info #0:
Driver Status: snd_intel8x0 is active
Driver Activation Cmd: "modprobe snd_intel8x0"
Config Status: cfg=new, avail=yes, need=no, active=unknown
################################################################################
lsmod
Module Size Used by
michael_mic 12540 4
arc4 12473 2
lib80211_crypt_tkip 17275 1
lib80211_crypt_ccmp 12789 1
rfcomm 38139 0
bnep 17830 2
bluetooth 158479 10 rfcomm,bnep
parport_pc 32114 0
ppdev 12849 0
snd_usb_audio 101566 2
snd_hwdep 13276 1 snd_usb_audio
snd_usbmidi_lib 24588 1 snd_usb_audio
joydev 17393 0
snd_intel8x0 33455 2
snd_ac97_codec 110213 1 snd_intel8x0
ac97_bus 12642 1 snd_ac97_codec
snd_pcm 80916 3 snd_usb_audio,snd_intel8x0,snd_ac97_codec
snd_seq_midi 13132 0
snd_rawmidi 25424 2 snd_usbmidi_lib,snd_seq_midi
snd_seq_midi_event 14475 1 snd_seq_midi
pcmcia 39826 0
snd_seq 51592 2 snd_seq_midi,snd_seq_midi_event
snd_timer 28931 2 snd_pcm,snd_seq
snd_seq_device 14172 3 snd_seq_midi,snd_rawmidi,snd_seq
cp210x 21610 0
psmouse 86520 0
ipw2200 146241 0
libipw 46732 1 ipw2200
tifm_7xx1 12937 0
cfg80211 178877 2 ipw2200,libipw
usbserial 37173 1 cp210x
tifm_core 15040 1 tifm_7xx1
snd 62218 18 snd_usb_audio,snd_hwdep,snd_usbmidi_lib,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
yenta_socket 27465 0
serio_raw 13027 0
pcmcia_rsrc 18367 1 yenta_socket
soundcore 14635 1 snd
pcmcia_core 21511 3 pcmcia,yenta_socket,pcmcia_rsrc
lib80211 14040 4 lib80211_crypt_tkip,lib80211_crypt_ccmp,ipw2200,libipw
snd_page_alloc 14108 2 snd_intel8x0,snd_pcm
mac_hid 13077 0
lp 17455 0
parport 40930 3 parport_pc,ppdev,lp
usbhid 41937 0
hid 77428 1 usbhid
i915 423564 2
firewire_ohci 40172 0
sdhci_pci 18324 0
firewire_core 56940 1 firewire_ohci
crc_itu_t 12627 1 firewire_core
sdhci 28241 1 sdhci_pci
drm_kms_helper 45466 1 i915
drm 197641 3 i915,drm_kms_helper
i2c_algo_bit 13199 1 i915
video 19115 1 i915
sky2 53628 0
################################################################################
cat /etc/modprobe.d/blacklist.conf
# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.
# evbug is a debug tool that should be loaded explicitly
blacklist evbug
# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd
# replaced by e100
blacklist eepro100
# replaced by tulip
blacklist de4x5
# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394
# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m
# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2
# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801
# replaced by p54pci
blacklist prism54
# replaced by b43 and ssb.
blacklist bcm43xx
# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps
# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi
# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp
# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr
# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac
################################################################################
cat /etc/modprobe.d/alsa-base.conf
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet --use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet --use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }
# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
################################################################################
lspci -vvx
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 04)
Subsystem: Gateway 2000 Device 0365
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 21
Region 0: I/O ports at 1c00 [size=256]
Region 1: I/O ports at 18c0 [size=64]
Region 2: Memory at b0040800 (32-bit, non-prefetchable) [size=512]
Region 3: Memory at b0040400 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: snd_intel8x0
Kernel modules: snd-intel8x0
00: 86 80 6e 26 07 00 90 02 04 00 01 04 00 00 00 00
10: 01 1c 00 00 c1 18 00 00 00 08 04 b0 00 04 04 b0
20: 00 00 00 00 00 00 00 00 00 00 00 00 7b 10 65 03
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00
|
I previously obtained the best results for playing sound in Java on Linux with the sun.audio.AudioStream and sun.audio.AudioPlayer. Those are "internal" classes and not recommended, but they worked better than anything else for me (for many years). Until the problem that prompted this question.
My new solution is just this: Runtime.getRuntime().exec(mediaPlayerCommand + fileName);
For the media player, I can use play on OpenSuse or mplayer on Ubuntu. I just place that command in my configuration file on the target OS and it works really well.
| Java application locks up after playing sound |
1,485,483,815,000 |
Very often, when I type something in Omnibox (address-bar), Chromium/Chrome crashes. W/ crash I mean that it freezes and refuses to any signals (mouse, keyboard etc.).
This is what got printed out to terminal (if browser is spawned through it):
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
I'm using Arch Linux and all system is up to date. Also, I'm dealing w/ this problem for like few weeks now... so it can't be tempory bug in any package because I have upgraded browser and other related packages too. Also, I have tried to downgrade packages as well — it sadly doesn't help.
On system w/ almost the same configuration all works and browser has never crashed even once.
I'm using Awesome WM, if it matters somehow, but problem persisted also when I was using Xmonad. It seems that Firefox works, but I would like to keep using Chromium or Chrome.
P.S. If any other logs are needed, please tell me in the comments and I will update the question.
|
I switched to Firefox for a while, but few weeks ago I tried Chrome once again. It was a big surprise to me; it works! Seems that system upgrade had fixed the bug in some point. I'm using Google Chrome 24.0.1284.2 dev from AUR now.
| Typing in Chromium's/Chrome's Omnibox crashes browser |
1,485,483,815,000 |
I encounter a bug that made my computer, under Debian 10, crash two times in ten days, and being unable to restart for ten minutes to half an hour.
Today during an Eclipse session, before while playing a game.
During my Elipse session today, I'm opening a web page on Firefox, and the computer frozes but the mouse is still able to move :
The computer is then unable to restart (even no display output) from 10:09 to 10:56
Here what my syslog says :
Feb 14 09:44:35 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: org.eclipse.m2e.logback.configuration: Initializing logback
Feb 14 09:44:40 bouleau gnome-shell[1842]: value "-1,000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Feb 14 09:44:40 bouleau gnome-shell[1842]: value "-1,000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Feb 14 09:44:40 bouleau gnome-shell[1842]: value "-1,000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Feb 14 09:44:40 bouleau gnome-shell[1842]: value "-1,000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Feb 14 09:44:41 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Feb 14 09:44:41 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Feb 14 09:44:41 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Feb 14 09:45:01 bouleau CRON[5284]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 14 09:46:48 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
Feb 14 09:46:49 bouleau org.gnome.Shell.desktop[1842]: Window manager warning: Window 0x6800003 (Eclipse) sets an MWM hint indicating it isn't resizable, but sets min size 449 x 300 and max size 2147483647 x 2147483647; this doesn't make much sense.
Feb 14 09:47:00 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: org.eclipse.m2e.logback.configuration: Logback config file: /home/marc/dev/Java/comptes-france/geographie/dev/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.16.0.20200318-1040.xml
Feb 14 09:47:00 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: org.eclipse.m2e.logback.configuration: Initializing logback
Feb 14 09:47:05 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Feb 14 09:47:05 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Feb 14 09:47:05 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Feb 14 09:47:14 bouleau PackageKit: daemon quit
Feb 14 09:47:14 bouleau systemd[1]: packagekit.service: Main process exited, code=killed, status=15/TERM
Feb 14 09:47:14 bouleau systemd[1]: packagekit.service: Succeeded.
Feb 14 09:49:06 bouleau _home_marc_eclipse_java-2020-03_eclipse_.desktop[1842]: Warning: NLS missing message: MavenImpl_error_lookup in: org.eclipse.m2e.editor.internal.messages
Feb 14 09:55:01 bouleau CRON[5564]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 14 09:58:21 bouleau rtkit-daemon[827]: Supervising 4 threads of 2 processes of 1 users.
Feb 14 09:58:21 bouleau rtkit-daemon[827]: Supervising 4 threads of 2 processes of 1 users.
Feb 14 10:05:01 bouleau CRON[5751]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 14 10:08:50 bouleau kernel: [147102.540747] list_del corruption. next->prev should be ffff8e7ab9011680, but was fffb8e7ab9011680
Feb 14 10:08:50 bouleau kernel: [147102.540759] ------------[ cut here ]------------
Feb 14 10:08:50 bouleau kernel: [147102.540760] kernel BUG at lib/list_debug.c:56!
Feb 14 10:08:50 bouleau kernel: [147102.540766] invalid opcode: 0000 [#1] SMP PTI
Feb 14 10:08:50 bouleau kernel: [147102.540768] CPU: 3 PID: 65 Comm: kswapd0 Tainted: P OE 4.19.0-14-amd64 #1 Debian 4.19.171-2
Feb 14 10:08:50 bouleau kernel: [147102.540769] Hardware name: System manufacturer System Product Name/P9X79 PRO, BIOS 1104 04/10/2012
Feb 14 10:08:50 bouleau kernel: [147102.540775] RIP: 0010:__list_del_entry_valid.cold.1+0x20/0x47
Feb 14 10:08:50 bouleau kernel: [147102.540777] Code: ae 49 b0 e8 90 24 ff ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 20 af 49 b0 e8 7c 24 ff ff 0f 0b 48 c7 c7 d0 af 49 b0 e8 6e 24 ff ff <0f> 0b 48 89 f2 48 89 fe 48 c7 c7 90 af 49 b0 e8 5a 24 ff ff 0f 0b
Feb 14 10:08:50 bouleau kernel: [147102.540778] RSP: 0018:ffffb2b6437d7bf0 EFLAGS: 00010246
Feb 14 10:08:50 bouleau kernel: [147102.540779] RAX: 0000000000000054 RBX: ffff8e7f0d1ad140 RCX: 0000000000000000
Feb 14 10:08:50 bouleau kernel: [147102.540780] RDX: 0000000000000000 RSI: ffff8e7f23ad66b8 RDI: ffff8e7f23ad66b8
Feb 14 10:08:50 bouleau kernel: [147102.540781] RBP: ffffb2b6437d7d80 R08: 00000000000004e3 R09: 0000000000000004
Feb 14 10:08:50 bouleau kernel: [147102.540782] R10: 0000000000000000 R11: ffffffffb0bfa6ee R12: ffff8e7f1e479b40
Feb 14 10:08:50 bouleau kernel: [147102.540783] R13: ffffffffaf86d890 R14: ffff8e7ab9011680 R15: ffff8e7ab90118c0
Feb 14 10:08:50 bouleau kernel: [147102.540784] FS: 0000000000000000(0000) GS:ffff8e7f23ac0000(0000) knlGS:0000000000000000
Feb 14 10:08:50 bouleau kernel: [147102.540785] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 14 10:08:50 bouleau kernel: [147102.540786] CR2: 00007efd0d905000 CR3: 00000006c440a001 CR4: 00000000000606e0
Feb 14 10:08:50 bouleau kernel: [147102.540787] Call Trace:
Feb 14 10:08:50 bouleau kernel: [147102.540794] __list_lru_walk_one+0xf9/0x170
Feb 14 10:08:50 bouleau kernel: [147102.540798] ? __lock_parent+0x70/0x70
Feb 14 10:08:50 bouleau kernel: [147102.540800] list_lru_walk_one+0x4a/0x70
Feb 14 10:08:50 bouleau kernel: [147102.540802] prune_dcache_sb+0x47/0x70
Feb 14 10:08:50 bouleau kernel: [147102.540804] super_cache_scan+0xf6/0x1a0
Feb 14 10:08:50 bouleau kernel: [147102.540809] do_shrink_slab+0x125/0x270
Feb 14 10:08:50 bouleau kernel: [147102.540811] shrink_slab+0x216/0x2b0
Feb 14 10:08:50 bouleau kernel: [147102.540813] shrink_node+0xe8/0x460
Feb 14 10:08:50 bouleau kernel: [147102.540814] kswapd+0x3cd/0x6c0
Feb 14 10:08:50 bouleau kernel: [147102.540816] ? mem_cgroup_shrink_node+0x170/0x170
Feb 14 10:08:50 bouleau kernel: [147102.540819] kthread+0x112/0x130
Feb 14 10:08:50 bouleau kernel: [147102.540821] ? kthread_bind+0x30/0x30
Feb 14 10:08:50 bouleau kernel: [147102.540825] ret_from_fork+0x35/0x40
Feb 14 10:08:50 bouleau kernel: [147102.540827] Modules linked in: snd_seq_dummy snd_seq snd_seq_device fuse bnep xt_conntrack ipt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nft_chain_nat_ipv4 nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink br_netfilter bridge stp llc vboxnetadp(OE) aufs(OE) vboxnetflt(OE) overlay vboxdrv(OE) uas usb_storage usblp intel_rapl snd_hda_codec_hdmi squashfs zstd_decompress xxhash loop x86_pkg_temp_thermal intel_powerclamp coretemp joydev nvidia_drm(POE) ath3k kvm_intel bluetooth kvm drm_kms_helper snd_hda_codec_realtek irqbypass drm snd_hda_codec_generic crct10dif_pclmul jitterentropy_rng crc32_pclmul hid_generic drbg ghash_clmulni_intel usbhid snd_hda_intel ansi_cprng intel_cstate eeepc_wmi hid snd_hda_codec ecdh_generic
Feb 14 10:08:50 bouleau kernel: [147102.540851] asus_wmi intel_uncore nvidia_modeset(POE) snd_hda_core sparse_keymap rfkill snd_hwdep video pcc_cpufreq intel_rapl_perf wmi_bmof pcspkr snd_pcm sg snd_timer mei_me snd mei iTCO_wdt soundcore iTCO_vendor_support evdev nvidia(POE) ipmi_devintf ipmi_msghandler parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sr_mod cdrom sd_mod crc32c_intel mxm_wmi aesni_intel ahci xhci_pci libahci aes_x86_64 xhci_hcd libata ehci_pci crypto_simd cryptd ehci_hcd glue_helper e1000e usbcore scsi_mod lpc_ich i2c_i801 mfd_core usb_common wmi button
Feb 14 10:08:50 bouleau kernel: [147102.540873] ---[ end trace 7712cfcfc33c5c74 ]---
Feb 14 10:08:50 bouleau kernel: [147102.540875] RIP: 0010:__list_del_entry_valid.cold.1+0x20/0x47
Feb 14 10:08:50 bouleau kernel: [147102.540875] Code: ae 49 b0 e8 90 24 ff ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 20 af 49 b0 e8 7c 24 ff ff 0f 0b 48 c7 c7 d0 af 49 b0 e8 6e 24 ff ff <0f> 0b 48 89 f2 48 89 fe 48 c7 c7 90 af 49 b0 e8 5a 24 ff ff 0f 0b
Feb 14 10:08:50 bouleau kernel: [147102.540876] RSP: 0018:ffffb2b6437d7bf0 EFLAGS: 00010246
Feb 14 10:08:50 bouleau kernel: [147102.540877] RAX: 0000000000000054 RBX: ffff8e7f0d1ad140 RCX: 0000000000000000
Feb 14 10:08:50 bouleau kernel: [147102.540878] RDX: 0000000000000000 RSI: ffff8e7f23ad66b8 RDI: ffff8e7f23ad66b8
Feb 14 10:08:50 bouleau kernel: [147102.540879] RBP: ffffb2b6437d7d80 R08: 00000000000004e3 R09: 0000000000000004
Feb 14 10:08:50 bouleau kernel: [147102.540880] R10: 0000000000000000 R11: ffffffffb0bfa6ee R12: ffff8e7f1e479b40
Feb 14 10:08:50 bouleau kernel: [147102.540881] R13: ffffffffaf86d890 R14: ffff8e7ab9011680 R15: ffff8e7ab90118c0
Feb 14 10:08:50 bouleau kernel: [147102.540882] FS: 0000000000000000(0000) GS:ffff8e7f23ac0000(0000) knlGS:0000000000000000
Feb 14 10:08:50 bouleau kernel: [147102.540883] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 14 10:08:50 bouleau kernel: [147102.540884] CR2: 00007efd0d905000 CR3: 00000006c440a001 CR4: 00000000000606e0
Feb 14 10:09:11 bouleau kernel: [147123.656466] rcu: INFO: rcu_sched self-detected stall on CPU
Feb 14 10:09:11 bouleau kernel: [147123.656472] rcu: 3-....: (5249 ticks this GP) idle=3b6/1/0x4000000000000002 softirq=2836759/2836759 fqs=2617
Feb 14 10:09:11 bouleau kernel: [147123.656473] rcu: (t=5250 jiffies g=5381237 q=838)
Feb 14 10:09:11 bouleau kernel: [147123.656475] NMI backtrace for cpu 3
Feb 14 10:09:11 bouleau kernel: [147123.656477] CPU: 3 PID: 31839 Comm: Cache2 I/O Tainted: P D OE 4.19.0-14-amd64 #1 Debian 4.19.171-2
Feb 14 10:09:11 bouleau kernel: [147123.656478] Hardware name: System manufacturer System Product Name/P9X79 PRO, BIOS 1104 04/10/2012
Feb 14 10:09:11 bouleau kernel: [147123.656479] Call Trace:
Feb 14 10:09:11 bouleau kernel: [147123.656482] <IRQ>
Feb 14 10:09:11 bouleau kernel: [147123.656487] dump_stack+0x66/0x81
Feb 14 10:09:11 bouleau kernel: [147123.656489] nmi_cpu_backtrace.cold.4+0x13/0x50
Feb 14 10:09:11 bouleau kernel: [147123.656492] ? lapic_can_unplug_cpu+0x80/0x80
Feb 14 10:09:11 bouleau kernel: [147123.656495] nmi_trigger_cpumask_backtrace+0xf9/0x100
Feb 14 10:09:11 bouleau kernel: [147123.656497] rcu_dump_cpu_stacks+0x9b/0xcb
Feb 14 10:09:11 bouleau kernel: [147123.656498] rcu_check_callbacks.cold.81+0x1db/0x335
Feb 14 10:09:11 bouleau kernel: [147123.656501] ? tick_sched_do_timer+0x60/0x60
Feb 14 10:09:11 bouleau kernel: [147123.656503] update_process_times+0x28/0x60
Feb 14 10:09:11 bouleau kernel: [147123.656504] tick_sched_handle+0x22/0x60
Feb 14 10:09:11 bouleau kernel: [147123.656506] tick_sched_timer+0x37/0x70
Feb 14 10:09:11 bouleau kernel: [147123.656507] __hrtimer_run_queues+0x100/0x280
Feb 14 10:09:11 bouleau kernel: [147123.656509] hrtimer_interrupt+0x100/0x220
Feb 14 10:09:11 bouleau kernel: [147123.656511] smp_apic_timer_interrupt+0x6a/0x140
Feb 14 10:09:11 bouleau kernel: [147123.656514] apic_timer_interrupt+0xf/0x20
Feb 14 10:09:11 bouleau kernel: [147123.656515] </IRQ>
Feb 14 10:09:11 bouleau kernel: [147123.656518] RIP: 0010:native_queued_spin_lock_slowpath+0x54/0x190
Feb 14 10:09:11 bouleau kernel: [147123.656519] Code: 81 e6 00 ff ff ff 75 5f f0 0f ba 2f 08 8b 07 72 56 89 c2 30 e6 a9 00 00 ff ff 75 47 85 d2 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75
Feb 14 10:09:11 bouleau kernel: [147123.656520] RSP: 0018:ffffb2b643a7fcd0 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13
Feb 14 10:09:11 bouleau kernel: [147123.656522] RAX: 0000000000180101 RBX: ffff8e7a36f71140 RCX: 0000000100000000
Feb 14 10:09:11 bouleau kernel: [147123.656522] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff8e7f1e479b40
Feb 14 10:09:11 bouleau kernel: [147123.656523] RBP: ffff8e7f14b7a500 R08: 0000000000000000 R09: ffffb2b643a7fc80
Feb 14 10:09:11 bouleau kernel: [147123.656524] R10: ffffe19718d8f340 R11: ffff8e7f15ccf490 R12: 0000000000000000
Feb 14 10:09:11 bouleau kernel: [147123.656525] R13: ffff8e7f1e479b40 R14: ffff8e79b6f71140 R15: 0000000000000000
Feb 14 10:09:11 bouleau kernel: [147123.656527] _raw_spin_lock+0x1c/0x20
Feb 14 10:09:11 bouleau kernel: [147123.656530] list_lru_add+0x64/0x1a0
Feb 14 10:09:11 bouleau kernel: [147123.656532] ? _cond_resched+0x15/0x30
Feb 14 10:09:11 bouleau kernel: [147123.656534] ? dput.part.34+0x32/0x140
Feb 14 10:09:11 bouleau kernel: [147123.656536] d_lru_add+0x34/0x40
Feb 14 10:09:11 bouleau kernel: [147123.656538] dput.part.34+0x124/0x140
Feb 14 10:09:11 bouleau kernel: [147123.656540] terminate_walk+0x83/0x100
Feb 14 10:09:11 bouleau kernel: [147123.656542] path_lookupat.isra.48+0xa3/0x220
Feb 14 10:09:11 bouleau kernel: [147123.656544] ? futex_wake+0x90/0x170
Feb 14 10:09:11 bouleau kernel: [147123.656545] filename_lookup.part.62+0xa0/0x170
Feb 14 10:09:11 bouleau kernel: [147123.656547] ? __check_object_size+0x162/0x180
Feb 14 10:09:11 bouleau kernel: [147123.656550] ? strncpy_from_user+0x47/0x1a0
Feb 14 10:09:11 bouleau kernel: [147123.656551] ? getname_flags+0x6a/0x1e0
Feb 14 10:09:11 bouleau kernel: [147123.656553] do_faccessat+0xac/0x250
Feb 14 10:09:11 bouleau kernel: [147123.656556] do_syscall_64+0x53/0x110
Feb 14 10:09:11 bouleau kernel: [147123.656558] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 14 10:09:11 bouleau kernel: [147123.656559] RIP: 0033:0x7f9a970b45c7
Feb 14 10:09:11 bouleau kernel: [147123.656560] Code: 77 01 c3 48 8b 15 c9 08 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 b8 15 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 99 08 0d 00 f7 d8 64 89 02 b8
Feb 14 10:09:11 bouleau kernel: [147123.656561] RSP: 002b:00007f9a8a83bb68 EFLAGS: 00000246 ORIG_RAX: 0000000000000015
Feb 14 10:09:11 bouleau kernel: [147123.656563] RAX: ffffffffffffffda RBX: 00007f9a713fa2f0 RCX: 00007f9a970b45c7
Feb 14 10:09:11 bouleau kernel: [147123.656563] RDX: 0000000080070057 RSI: 0000000000000000 RDI: 00007f9a78874508
Feb 14 10:09:11 bouleau kernel: [147123.656564] RBP: 00007f9a8a83bbe0 R08: 0000000000000008 R09: 0000000000000008
Feb 14 10:09:11 bouleau kernel: [147123.656565] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
Feb 14 10:09:11 bouleau kernel: [147123.656566] R13: 0000000000000001 R14: 00007f9a738ca330 R15: 0000000000000000
Feb 14 10:09:18 bouleau kernel: [147130.436561] watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [StreamT~ns #935:5811]
Feb 14 10:09:18 bouleau kernel: [147130.436564] Modules linked in: snd_seq_dummy snd_seq snd_seq_device fuse bnep xt_conntrack ipt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nft_chain_nat_ipv4 nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink br_netfilter bridge stp llc vboxnetadp(OE) aufs(OE) vboxnetflt(OE) overlay vboxdrv(OE) uas usb_storage usblp intel_rapl snd_hda_codec_hdmi squashfs zstd_decompress xxhash loop x86_pkg_temp_thermal intel_powerclamp coretemp joydev nvidia_drm(POE) ath3k kvm_intel bluetooth kvm drm_kms_helper snd_hda_codec_realtek irqbypass drm snd_hda_codec_generic crct10dif_pclmul jitterentropy_rng crc32_pclmul hid_generic drbg ghash_clmulni_intel usbhid snd_hda_intel ansi_cprng intel_cstate eeepc_wmi hid snd_hda_codec ecdh_generic
Feb 14 10:09:18 bouleau kernel: [147130.436585] asus_wmi intel_uncore nvidia_modeset(POE) snd_hda_core sparse_keymap rfkill snd_hwdep video pcc_cpufreq intel_rapl_perf wmi_bmof pcspkr snd_pcm sg snd_timer mei_me snd mei iTCO_wdt soundcore iTCO_vendor_support evdev nvidia(POE) ipmi_devintf ipmi_msghandler parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sr_mod cdrom sd_mod crc32c_intel mxm_wmi aesni_intel ahci xhci_pci libahci aes_x86_64 xhci_hcd libata ehci_pci crypto_simd cryptd ehci_hcd glue_helper e1000e usbcore scsi_mod lpc_ich i2c_i801 mfd_core usb_common wmi button
Feb 14 10:09:18 bouleau kernel: [147130.436604] CPU: 5 PID: 5811 Comm: StreamT~ns #935 Tainted: P D OE 4.19.0-14-amd64 #1 Debian 4.19.171-2
Feb 14 10:09:18 bouleau kernel: [147130.436605] Hardware name: System manufacturer System Product Name/P9X79 PRO, BIOS 1104 04/10/2012
Feb 14 10:09:18 bouleau kernel: [147130.436610] RIP: 0010:native_queued_spin_lock_slowpath+0xfc/0x190
Feb 14 10:09:18 bouleau kernel: [147130.436612] Code: 00 8b 07 85 c0 75 0d be 01 00 00 00 f0 0f b1 37 85 c0 74 38 89 c8 c1 e8 10 66 87 47 02 89 c6 c1 e6 10 75 3f 31 f6 eb 02 f3 90 <8b> 07 66 85 c0 75 f7 41 89 c0 66 45 31 c0 44 39 c1 74 67 c6 07 01
Feb 14 10:09:18 bouleau kernel: [147130.436613] RSP: 0018:ffffb2b649f57dc0 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13
Feb 14 10:09:18 bouleau kernel: [147130.436614] RAX: 0000000000180101 RBX: ffff8e7f1e479b40 RCX: 0000000000180000
Feb 14 10:09:18 bouleau kernel: [147130.436615] RDX: ffff8e7f23b62d80 RSI: 0000000000000000 RDI: ffff8e7f1e479b40
Feb 14 10:09:18 bouleau kernel: [147130.436616] RBP: ffff8e7bf10fd800 R08: 0000000000000000 R09: 0000000000000000
Feb 14 10:09:18 bouleau kernel: [147130.436617] R10: ffffb2b649f57dd8 R11: ffff8e7b710fd780 R12: 0000000000000000
Feb 14 10:09:18 bouleau kernel: [147130.436618] R13: ffff8e7b710fd800 R14: 0000000000000000 R15: ffff8e7f16fa5000
Feb 14 10:09:18 bouleau kernel: [147130.436619] FS: 00007f749bb34700(0000) GS:ffff8e7f23b40000(0000) knlGS:0000000000000000
Feb 14 10:09:18 bouleau kernel: [147130.436620] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 14 10:09:18 bouleau kernel: [147130.436621] CR2: 00007f9a70a96010 CR3: 00000005ea4ba005 CR4: 00000000000606e0
Feb 14 10:09:18 bouleau kernel: [147130.436622] Call Trace:
Feb 14 10:09:18 bouleau kernel: [147130.436627] _raw_spin_lock+0x1c/0x20
Feb 14 10:09:18 bouleau kernel: [147130.436630] list_lru_del+0x57/0x150
Feb 14 10:09:18 bouleau kernel: [147130.436634] d_lru_del+0x3d/0x50
Feb 14 10:09:18 bouleau kernel: [147130.436636] __dentry_kill+0x149/0x170
Feb 14 10:09:18 bouleau kernel: [147130.436638] dentry_kill+0x4d/0x190
Feb 14 10:09:18 bouleau kernel: [147130.436639] dput.part.34+0xf0/0x140
Feb 14 10:09:18 bouleau kernel: [147130.436641] do_renameat2+0x3cb/0x560
Feb 14 10:09:18 bouleau kernel: [147130.436643] __x64_sys_rename+0x1c/0x20
Feb 14 10:09:18 bouleau kernel: [147130.436646] do_syscall_64+0x53/0x110
Feb 14 10:09:18 bouleau kernel: [147130.436647] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 14 10:09:18 bouleau kernel: [147130.436649] RIP: 0033:0x7f74c1ddf6d7
Feb 14 10:09:18 bouleau kernel: [147130.436650] Code: e8 6e e9 07 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5b c3 66 90 b8 ff ff ff ff 5b c3 66 0f 1f 84 00 00 00 00 00 b8 52 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 89 d7 14 00 f7 d8 64 89 02 b8
Feb 14 10:09:18 bouleau kernel: [147130.436651] RSP: 002b:00007f749bb338c8 EFLAGS: 00000286 ORIG_RAX: 0000000000000052
Feb 14 10:09:18 bouleau kernel: [147130.436652] RAX: ffffffffffffffda RBX: 00007f74c1ba89d0 RCX: 00007f74c1ddf6d7
Feb 14 10:09:18 bouleau kernel: [147130.436653] RDX: ffffffffffffff40 RSI: 00007f748561a688 RDI: 00007f748561ae88
Feb 14 10:09:18 bouleau kernel: [147130.436654] RBP: 00007f748561a688 R08: 00007f74c1ba89d0 R09: 00000000000ffff0
Feb 14 10:09:18 bouleau kernel: [147130.436655] R10: 4403a5a2c8eaa330 R11: 0000000000000286 R12: 00007f74856d4c80
Feb 14 10:09:18 bouleau kernel: [147130.436656] R13: 0000000000002368 R14: 00007f749bb34700 R15: 00007f748561ae88
Feb 14 10:56:11 bouleau systemd-modules-load[389]: Inserted module 'lp'
Feb 14 10:56:11 bouleau systemd-modules-load[389]: Inserted module 'ppdev'
Feb 14 10:56:11 bouleau kernel: [ 0.000000] Linux version 4.19.0-14-amd64 ([email protected]) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.171-2 (2021-01-30)
Feb 14 10:56:11 bouleau systemd-modules-load[389]: Inserted module 'parport_pc'
Feb 14 10:56:11 bouleau kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-14-amd64 root=UUID=0e3b15aa-0b00-4c0b-a0e5-3e2038185527 ro quiet
Is Feb 14 10:08:50 bouleau kernel: [147102.540747] list_del corruption. next->prev should be ffff8e7ab9011680, but was fffb8e7ab9011680 a corruption :
in a package
or in a memory stick?
If it was in a memory stick, the computer might had restarted smoothly. But it didn't.
Is my issue related to it's power supply at the same time?
What else could I search for?
|
It went that my computer was broken : two memories sticks and one DIMM support on the motherboard were badly working and had to be removed or disabled.
The message :
next->prev should be fff f 8e7ab9011680
but was fff b 8e7ab9011680
hinted me to such failure. Because a pointer changing it's value by a single bit and this one being a very high value one, was very suspicious.
| Computer froze and unable to restart for tens of minutes : can my syslog show if the trouble comes from a memory stick, a package or its power unit? |
1,485,483,815,000 |
I've been using Fedora 15 for a couple months now and haven't had any problems. Last week I switched desks and got a new monitor, and now all of a sudden it will randomly freeze up.
Also sometimes without freezing it will make all title bars (including the system bar at the top of the screen) and system images (such as the images for the launcher on the left side of gnome 3) plain blue, and any text on them is just blocked out in darker blue.
It usually freezes some time after everything turns blue. I can switch to another terminal using Ctrl + Alt + F2 and reboot. I checked the messages log and found this:
kernel: [ 1706.856599] [drm] nouveau 0000:01:00.0: PGRAPH - TRAP
kernel: [ 1706.856602] [drm] nouveau 0000:01:00.0: PGRAPH - ch 4 (0x0000b45000) subc 5 class 0x8297 mthd 0x0e08 data 0x04380000
kernel: [ 1706.856611] [drm] nouveau 0000:01:00.0: VM: trapped read at 0x20ff202000 on ch 4 [0x00000b45] PGRAPH/TEXTURE/00 reason: PT_NOT_PRESENT
kernel: [ 1706.856695] [drm] nouveau 0000:01:00.0: magic set 0:
kernel: [ 1706.856698] [drm] nouveau 0000:01:00.0: 0x00408904: 0x8008700f
kernel: [ 1706.856700] [drm] nouveau 0000:01:00.0: 0x00408908: 0x20ff2020
kernel: [ 1706.856702] [drm] nouveau 0000:01:00.0: 0x0040890c: 0x40000e04
kernel: [ 1706.856703] [drm] nouveau 0000:01:00.0: 0x00408910: 0x20200000
kernel: [ 1706.856705] [drm] nouveau 0000:01:00.0: PGRAPH - TRAP_TEXTURE - TP0: Unhandled ustatus 0x00000003
kernel: [ 1706.856707] [drm] nouveau 0000:01:00.0: PGRAPH - TRAP
kernel: [ 1706.856709] [drm] nouveau 0000:01:00.0: PGRAPH - ch 4 (0x0000b45000) subc 5 class 0x8297 mthd 0x1b0c data 0x1000f010
kernel: [ 1706.856716] [drm] nouveau 0000:01:00.0: VM: trapped read at 0x20ff202000 on ch 4 [0x00000b45] PGRAPH/TEXTURE/00 reason: PT_NOT_PRESENT
My system admin thought it might be some loose RAM, but I tried taking out and putting back in all my RAM sticks and it didn't work.
I am using a graphics card that I took off an old machine, under Fedora System Settings it says my graphics driver is: Gallium 0.4 on NV86.
Is it time to upgrade to a new graphics card? If so it's not a big deal, I can get one that will fit my needs for around $50. I'm just not sure if that's the problem, or if it can be fixed with a different way.
|
It may be the nouveau driver, which many people advise to void like the plague. This link explains how to disable it and replace it with the native nVidia drivers.
| System freezing on Fedora 15 - graphics issue? |
1,485,483,815,000 |
The last weeks I have been trying to reinstall a Linux distro in my laptop Asus X553S these are the specs:
8 GB Ram
Pentium Processor N3700 4 cores, 1.6 GHz
Hard drive 20 GB for root partition, 100 GB home partition, 2 GB Swap
Integrated intel graphics card
I tried to use other distros as Mageia and Zenwalk (slackware derivated), in both cases occurs a "random freeze" it is a complete freeze, no mouse, no keyboard, no audio/screen events, it is required a hard reset with power button, no one special task before the freeze (looking files, using web browser, etc.), usually takes a few minutes (around 10 or 15 minutes), but in other scenarios occurs very quickly (2 or 3 minutes of usage), the RAM is not an issue their usage rarely is around 1 GB.
I discard a hardware issue because Windows 10 runs fine (slow but fine), I executed Memtest without issues, and actually around two years ago had an Antergos running fine (unfortunately during one update I left it unplugged, the energy drain out, and the SO was useless)
In the log files (messages, syslog, dbus and Xorg), nothing strange appears, and actually the first time that I tried to install and use Linux in that laptop, I had the same troubles (even with Ubuntu family distros, only with Antergos I could avoid the issue).
Any idea or suggestion in order to still investigating? (I would like to know the root cause before to go to the Arch family again).
|
I have the same CPU model and the same issue. Those low-end Intel CPUs have some issues with their power states on Linux.
Try adding kernel parameter intel_idle.max_cstate=1 in your /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"
(The line GRUB_CMDLINE_LINUX_DEFAULT is already there.)
After saving, run sudo update-grub. Then restart your machine and test it.
Background info:
https://bugzilla.kernel.org/show_bug.cgi?id=109051
https://wiki.ubuntu.com/Kernel/KernelBootParameters
| Random Linux freeze (Slackware, mageia, and others) |
1,485,483,815,000 |
Occasionally when I plug my Dell USB-C docking station into my laptop running Manjaro, the system immediately freezes completely and requires a hard reboot.
Other times, my external screens don't get detected until I unplug and replug the docking station. Keyboard and mouse always work though.
I've had these issues for quite some time and it's not just limited to Manjaro, I've had it with Ubuntu as well (both running KDE Plasma).
I'm running this on a brand new Dell XPS 13 laptop and experienced the same issues on a previous model.
Where do you typically look to start debugging issues like this? Which log files and/or tools would you use?
|
When freezing I'd use journalctl -b -1. It will show you the previous kernel messages until reboot.
In case of non detected screens, I'd look at /var/log/Xorg0.log or other Xorg*.log files. You might post the relevant part of the logs in your question.
| Debugging issues with docking station |
1,485,483,815,000 |
This one is a bit weird.
We have a closed network of about five (5) Red Hat Workstation 7 assets in one of our development laboratories. One of the REHL 7 machines is hosting a USB connected DroboPro via NFS to the other machines - the other machines are mounting this share on boot via /etc/fstab. Everything works great and all users and access the share - unless the machine hosting the NFS share goes down. When that machine is shut down or brought offline, the share is inaccessible (obviously), but the other machines also experience a side effect we can't explain.
If the machine hosting the share is off, and we lock the screen or reboot any of the other four (4) RHEL 7 machines, they lockup/freeze and are inaccessible until the machine hosting the NFS share is brought back online.
We've narrowed the source down to the NFS share by unmounting it on the other four (4) RHEL 7 assets and bringing down the share, which resulted in no locking/freezing.
/etc/exports > /dir/path/ 192.168.100.0/24(rw)
Any insight or recommendation for further troubleshooting would be appreciated.
Thanks.
|
give this a try: add the following flags to your nfs mount point in /etc/fstab:
bg,intr,soft,timeo=3,retrans=3,actimeo=3,retry=3
adjust timeout rates accordingly but i found this combination works the best. Ensure "default" is not set in nfs mount point line and read the man pages for nfs to see exactly how this would effect your mount point.
| NFS Share Locking Workstations in Closed Network |
1,485,483,815,000 |
My problem
If I transfer file with rsync using tapes,or disk(usb,e-sata,firewire)
linux hang,no way to resume if not using powerbutton(brutal shutdown!)
sysrq-trigger don't work,ssh don't answer,keyboard and screen no input.
I have a M5A97 R2.0 Asus board,with 16G ram Crucial.
I 've ordered a couple of other ram by kingston
In your opinion can be a hw problem,or ram problem?
Using the program ramtest no error given.
I have tried also this solution..but hang anyway.
Your opinion?
I forgot,hang happen on every transfer especially with big files(over 10G)
I tried different kernel versions..same problem.
|
Change ram and..works fine.
Transfer of over 2TB completed
without panic.
So problem was my old ram.
| linux hang on transfer with rsync,can be a ram error? |
1,485,483,815,000 |
When I open too many (more than ~8/9) tabs in Chrome the whole GUI freezes and the mouse pointer doesn't move and the system responds incredibly slowly to keyboard input (~20s delay). I'm assuming it's all down to lack of RAM on my laptop but I haven't been able to check this when it actually happens due to the nature of the problem.
What I want to be able to do is press a special key combination which instantly kills Chrome.
I'm running: Arch Linux/ Cinnamon on a Lenovo X200 if that helps at all.
|
Alt-Sysrq-F should help you if you're already in the trouble and system is very slow due to search for any free memory bits. But it's better to add more RAM especially with modern browser applications, which become more and more bigger due to support of many new web standards. As an alternative, you can increase your swap space.
| Too many tabs in Chrome causes whole computer to freeze |
1,485,483,815,000 |
Yesterday I successfully managed to make a kiosk from Ubuntu Server. I'm going to use it to rub some web application that will run non-stop.
However, in some cases, duo to lot of js animation I'm afraid that it may freeze/won't respond anymore and I won't be there to do anything.
Is there a way to run some commands once the browser freezes? Currently, when the OS launches it will trigger the kiosk in its own but if I want I can start and stop it manually with:
bash
sudo start kiosk
sudo stop kiosk
So I will need to run
bash
sudo stop kiosk
To close the current freezed browser instance (hopefully it will kill it since the server has no graphics but when I start the kiosk it's loading openbox and xset in order to see the browser, when I'm stopping the kiosk it stops those services as-well).
Then, I will need to run:
bash
sudo start kiosk
To relaunch everything.
So is it possible doing that once I somehow detect if the browser has frozen or not responding?
Edit:
My kiosk files are as follows:
/opt/kiosk.sh:
#!/bin/bash
xset -dpms
xset s off
openbox-session &
while true; do
rm -rf ~/.{config,cache}/google- chrome/
google-chrome --kiosk --no-first-run 'http://thepcspy.com'
done
/etc/init/kiosk.conf:
start on (filesystem and stopped udevtrigger)
stop on runlevel [06]
console output
emits starting-x
respawn
exec sudo -u user startx /etc/X11/Xsession /opt/kiosk.sh --
|
Browsers freeze typically when they hog memory. Since you are running in kiosk mode you can find out the ideal memory usage by the browser , and also the memory it is taking when it actually gets hung while you are observing it.
Lets say it gets hung when you are working - just find out the memory it is taking by using
ps -eo vsize,pid | grep <pid of the browser>
Now you know the limit that should not be crossed.
Just write a forever loop that keeps monitoring the vsize and if it exceeds just restart it. (this example keeps that limit at 12345)
while true; do
browser &
p=$!
echo "browser restarted with pid $p"
while true; do
sleep 1
x=`ps -eo vsize,pid | grep $p | head -1 | awk '{print $1}' `
echo "memory is $x"
if [ "$x" -gt "12345" ]
then
kill -9 $p
break
fi
done
done
| Relaunch an app if it freezes |
1,485,483,815,000 |
My Linux Mint system (17 Cinnamon, lenovo g565) hangs up frequently during work (say, 2-4 times a day).
It may look different
white screen
black screen
screen freeze
Maybe some of these symtoms look familiar and you know possible reasons to check?
If not, what updates/logs/diagnostic tools can you advice to make the most systematic and direct search of the reason?
|
Start from the very beginning. Go to /var/log and have a look at the syslog file.
Almost every error and problem will show up there. Any error entry is a potential problem, it is either the result of another error or the primary cause of your issues.
A healthy system should have VERY few error entries in syslog.
Once you get a line on the problems you see, bring them back to the forum. Someone here will probably know what is happening.
If you have no syslog file or it does not appear to be current, start the syslog daemon.
Have a look here if this is something you do not understand.
http://computernetworkingnotes.com/network-administrations/syslog-server.html
| frequent linux mint hangs |
1,712,611,232,000 |
I moved from Windows to Linux. I have been using Linux for a few weeks. I am having some problems, such as freezing, errors. I am a programmer on the rider program. When I run this program, Linux freezes and I cannot do anything with it.
When I use Bluetooth headphones, there is a delay in the sound and interruption, these things do not happen to me when I was using Windows.
Is there a solution? I am using debian 12.
These are the laptop specifications
|
In general, and specifically to possibly address your Bluetooth audio issues, I would suggest a distro other than Debian stable. Debian stable is, while very stable, quite old in terms of included packages.
I would suggest, as a beginner, you might find Pop!OS, Ubuntu, or Mint to work better for you. These are kept much more up to date and are still regarded as quite stable.
As far as freezing issues, the most common issue is hardware. Some piece of hardware, possibly memory, isn't playing well and may be the root cause of freezing.
| Why does linux freeze and not work correctly |
1,712,611,232,000 |
So, I've installed Linux many times in the past, generally from a liveUSB, as I'm using now. It's a 32 GB SamData SD101, on USB 2.0. (Probably excessive for an installer, but it's what I had on hand and it was empty.)
I am currently running Linux Mint 20.4, and it's past time for an upgrade, so in this island between projects, I'm attempting to try KUbuntu on it. I download the iso for 22.04.3 and burn it to said drive with Mint's USB Image Writer app, plug it into a USB 2.0 port, and restart; then, I hit F11 for my boot device selector and choose the USB.
A moment later, I'm greeted with the basic installer options, specifically Try/Install KDE, etc., and I choose Try/Install. After that, the weirdness happens.
I get the power-on boot splash, as if it's stuck in POST. This is hard data on the motherboard, and after I select from the boot menu. There's a little LED blinking on the USB drive, but I've seen it go on like that, with the POST splash, for more than ten minutes. (Figured I would get some household chores done and come back to it, in case it's just taking a little while; but the mobo splash was still there.)
As far as I can tell, it's just stuck. On concluding this, I remove the drive from the USB 2.0 slot, and depress the power button to manually power-off my machine; then I wait at least twenty seconds (old habit to protect my HDD) and turn it on. Mint 20.3 boots normally. Current OS acts like nothing happened.
Aside from that initial GRUB-like menu, I never get the option to try or install KUbuntu. (Clearly I installed Mint on this machine some time ago, and do not know if I've dealt with this before... it's been a busy few years.) Just a hang on the splash screen, and a potentially irrelevant red light on the thumb drive, seemingly indefinitely.
I've got some ideas, but I do not know what I'm doing wrong, and need some advice.
Additional data: The motherboard is an MSI MPG x570 Tomahawk Wifi. None of the debug LEDs are informing me of an error with power, RAM, CPU, or detection of a disk; they're behaving normally, so I'm assuming it isn't the mobo. I very recently installed a 4 TB Crucial NVMe M.2 drive, which runs fine on my current OS and doesn't seem to be defective at all; it's been formatted and auto-mounts, and I've had no difficulty storing on it or reading from it (in fact it's KUbuntu's target disk, if it can ever get around to that part). My USB is plugged into an otherwise well-behaved USB 2.0 slot on the front of my machine, which I regularly use for writing to storage, though it is attached through the case and is not directly on the motherboard. Lastly, my graphics card installed is currently an RTX 3050, but that shouldn't matter to a LiveUSB, should it?
I recently installed the last LTS of KUbuntu onto an Ideapad without issue, so this is a little weird.
Thanks for any assist.
|
So, I got it on there. Here's what was happening.
To begin with, now that I've got some time for it, I cleared a USB port at the back of my machine and plugged the thumb drive in there. (It's not easy to get to, but doable; I usually just use that space for consistent peripherals and the front-panel or a hub for everything else.) This was part of the problem, but not all of it.
Turns out that the 32 GB thumb drive I'm using had two partitions burned onto it as part of the KUbuntu image, for some reason. Booting to one would get me the GRUB screen, then complain (for a flicker) about a lack of boot directories and then dump me at the boot splash. Interesting. I only recall one drive partition showing up when it was plugged into the front, but can't explain why this is different. Note that this was not the behavior where the KUbuntu logo shows up beneath the power-on splash, but just the power-on splash.
Booting to the other partition was where I hit my second weird issue. My CPU is a Ryzen without embedded graphics, and all attempts to boot were going through an RTX 3050 plugged in. Apparently the LiveUSB had a little trouble with that, and was dumping me on a blinking cursor screen for a very long time, possibly indefinitely. To be sure, I left, made lunch, ate it, and came back the better part of an hour later, and it was still there; apparently this is a known issue with Nvidia cards.
Powering off, and rebooting again, took me to the option of "safe graphics" mode, which couldn't hurt. This took a moment but brought me to Try/Install KUbuntu in very low resolution. After verifying that everything was functional, I installed onto my M.2.
Rebooting to it, everything is flawless. Since I opted to download proprietary material too, the Nvidia driver is already installed. System powers on and off in a practical blink of an eye. I still need to customize it to my liking, but all is well.
So, in summary, plug the USB drive in the back, be prepared for issues with an Nvidia card (minus a driver for it) and use "safe graphics" to get around them, and install proprietary material too if you've got a big media setup so the reboot will take full advantage. After that, all has been well.
| Strange boot issue installing KUbuntu |
1,712,611,232,000 |
My Linux crashes after it wakes up from sleep mode,
namely, it stops responding to any commands,
at the moment I have Manjaro Linux, but there was a similar problem on Ubuntu.
My laptop: Huawei Mate Book D16 RLEF-X with processor: Intel i5-12450H.
I tried to change the value of some parameter in the root/etc/default/grub file, but it didn't help me, Everything ends in the logs when entering sleep mode.
I have heard that a similar problem manifests itself on many (if not all) laptops of this model and the Huawei brand in particular. But maybe there is some solution to this problem?
сен 24 04:00:38 artyom-rlefxx systemd-logind[418]: The system will suspend now!
сен 24 04:00:38 artyom-rlefxx NetworkManager[419]: <info> [1695517238.9251] manager: sleep: sleep requested (sleeping: no enabled: yes)
сен 24 04:00:38 artyom-rlefxx ModemManager[443]: <info> [sleep-monitor-systemd] system is about to suspend
сен 24 04:00:38 artyom-rlefxx NetworkManager[419]: <info> [1695517238.9253] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
сен 24 04:00:38 artyom-rlefxx NetworkManager[419]: <info> [1695517238.9257] manager: NetworkManager state is now ASLEEP
сен 24 04:00:38 artyom-rlefxx NetworkManager[419]: <info> [1695517238.9258] device (wlp0s20f3): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
сен 24 04:00:38 artyom-rlefxx dbus-daemon[416]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.2' (uid=0 pid=419 comm="/usr/bin/NetworkManager --no-daemon")
сен 24 04:00:38 artyom-rlefxx kded5[741]: org.kde.plasma.nm.kded: Unhandled active connection state change: 3
сен 24 04:00:38 artyom-rlefxx systemd[1]: Starting Network Manager Script Dispatcher Service...
сен 24 04:00:38 artyom-rlefxx dbus-daemon[416]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
сен 24 04:00:38 artyom-rlefxx systemd[1]: Started Network Manager Script Dispatcher Service.
сен 24 04:00:38 artyom-rlefxx kernel: wlp0s20f3: deauthenticating from e2:c7:58:19:a6:a9 by local choice (Reason: 3=DEAUTH_LEAVING)
сен 24 04:00:39 artyom-rlefxx kscreenlocker_greet[4371]: Qt: Session management error: networkIdsList argument is NULL
сен 24 04:00:39 artyom-rlefxx wpa_supplicant[499]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=e2:c7:58:19:a6:a9 reason=3 locally_generated=1
сен 24 04:00:39 artyom-rlefxx wpa_supplicant[499]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
сен 24 04:00:39 artyom-rlefxx NetworkManager[419]: <info> [1695517239.1169] device (wlp0s20f3): supplicant interface state: completed -> disconnected
сен 24 04:00:39 artyom-rlefxx NetworkManager[419]: <info> [1695517239.1170] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
сен 24 04:00:39 artyom-rlefxx NetworkManager[419]: <info> [1695517239.1172] dhcp4 (wlp0s20f3): canceled DHCP transaction
сен 24 04:00:39 artyom-rlefxx NetworkManager[419]: <info> [1695517239.1172] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
сен 24 04:00:39 artyom-rlefxx NetworkManager[419]: <info> [1695517239.1172] dhcp4 (wlp0s20f3): state changed no lease
сен 24 04:00:39 artyom-rlefxx NetworkManager[419]: <info> [1695517239.1517] device (wlp0s20f3): set-hw-addr: set MAC address to 26:D7:AB:DA:5A:BF (scanning)
сен 24 04:00:39 artyom-rlefxx NetworkManager[419]: <info> [1695517239.1803] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
сен 24 04:00:39 artyom-rlefxx NetworkManager[419]: <info> [1695517239.2016] device (wlp0s20f3): set-hw-addr: reset MAC address to 30:05:05:98:BC:E6 (unmanage)
сен 24 04:00:39 artyom-rlefxx wpa_supplicant[499]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
сен 24 04:00:39 artyom-rlefxx wpa_supplicant[499]: p2p-dev-wlp0s20: CTRL-EVENT-DSCP-POLICY clear_all
сен 24 04:00:39 artyom-rlefxx wpa_supplicant[499]: nl80211: deinit ifname=p2p-dev-wlp0s20 disabled_11b_rates=0
сен 24 04:00:39 artyom-rlefxx wpa_supplicant[499]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
сен 24 04:00:39 artyom-rlefxx kscreenlocker_greet[4371]: kf.kirigami: Failed to find a Kirigami platform plugin
сен 24 04:00:39 artyom-rlefxx wpa_supplicant[499]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
сен 24 04:00:39 artyom-rlefxx wpa_supplicant[499]: nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0
сен 24 04:00:39 artyom-rlefxx systemd[1]: Reached target Sleep.
сен 24 04:00:39 artyom-rlefxx kscreenlocker_greet[4371]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_US" . Search paths ("/usr/share/qt/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts")
сен 24 04:00:39 artyom-rlefxx systemd[1]: Starting System Suspend...
сен 24 04:00:39 artyom-rlefxx systemd-sleep[4409]: Entering sleep state 'suspend'...
сен 24 04:00:39 artyom-rlefxx kernel: PM: suspend entry (s2idle)
|
A solution has been found. After many days of trying and suffering, I finally decided to install POP OS! and check its operation on this problematic unit. After coming out of sleep mode in the new system, lo and behold, the system was still working. But it was too early to rejoice, she switched to reading mode. It was impossible to perform any action with memory. Then I realized the problem is in the SSD NVMe drive, which is from the factory in the laptop. He was the reason for the incorrect operation of any Linux distribution. This drive simply did not "wake up" after coming out of sleep mode. Various methods have been tried to correct this error, but to no avail. Only the replacement of the regular strange SSD with a normal new one helped . I really hope that anyone who bought this laptop and encountered a similar error will find this post and will finally be able to install this wonderful system on their laptop :)
| Linux crashes after resume from suspend |
1,712,611,232,000 |
On my Linux Mint 21.1 Cinnamon running an nvidia-driver-530...
VirtualBox 7.0 guest freezes whenever the guest is switched into full-screen mode. The exact version follows:
$ apt-cache policy virtualbox-7.0
virtualbox-7.0:
Installed: 7.0.8-156879~Ubuntu~jammy
Candidate: 7.0.8-156879~Ubuntu~jammy
Version table:
*** 7.0.8-156879~Ubuntu~jammy 500
500 https://download.virtualbox.org/virtualbox/debian jammy/contrib amd64 Packages
100 /var/lib/dpkg/status
... has only one guest machine = Win10 Pro version 22H2 (not a clean install, but virtualized physical machine according to this one of my answer.
Guest additions were updated to the latest version both in VirtualBox itself, and inside the Win10 VM.
I tried connecting remotely for an hour or more using different tools (RDP clients). I believed this is the way around the issue. Fail was what I accepted as a result in the end.
At this point I am unsure what causes the issue, and how exactly to solve it?
|
For some reason, disabling 3D acceleration helped and fixed the issue:
| VirtualBox 7.0 guest freezes whenever the guest is switched into full-screen mode, fix? |
1,606,652,776,000 |
I'm currently running Debian Buster with the 4.19.0-9-amd64 kernel. I find that intermittently after booting my system, selecting this kernel, entering my boot disk encryption key, and waiting for systemd to launch its services, my screen will clear, but will not proceed to launch my WM from that point. (as a note, 4.19.0-10-amd64 appears to cause this behavior 100% of the time)
Normally, I expect my primary monitor to turn off between systemd's services starting and my WM login screen appearing, but that does not happen in these cases–instead, my system will hang on an apparently empty terminal screen (which does not animate or respond to input) until it is hard rebooted. To my knowledge, this has always occurred, even on a fresh Debian install with little-to-no other software installed.
The only other thing I could find which seems odd is that every time I boot, before prompting me for my encrypted disk key, I see the following lines:
volume group "debian-vg" not found
Cannot process volume group debian-vg
volume group "debian-vg" not found
Cannot process volume group debian-vg
I suspect they are not related, but this is the only oddity I can pinpoint in my boot.log.
My graphics drivers are nvidia's proprietary drivers, with my machine running two SLI'd GTX 770 cards. My desktop environment is KDE Plasma.
The output of sudo dmesg is too long to add to this post, and is posted to Debian's pastezone.
|
Since the posting of this questing, I've upgraded my system to Debian 11 (Bullseye), and with that upgrade I'm no longer seeing this hang. I presume some DE package was at fault and was upgraded in the process. I still encounter the "debian-vg" lines at startup, but the don't seem to impact it in any way.
| Intermittent hang after systemd startup on Debian Buster |
1,606,652,776,000 |
My PC freezes a third time and I have to shut it down forcibly. Why doesn't journalctl save the boot logs before forced shutdown? When I do journalctl --list-boots I only get the boot after crash.
I'm not sorting well or misconfiguration?
System: ArchLinux (5.4.8-arch1-1)
|
It depends on the freeze, and it's not clear to me what do you mean by "shut it down forcibly". If this means a power off, definitely, there is no way for your PC to sync data in a proper way. The recommended way to force reboot, is by using the magic SysRq key and the REISUBsequence. More details are at
https://wiki.archlinux.org/index.php/Sysctl
https://en.wikipedia.org/wiki/Magic_SysRq_key
Also, check that /var/log/journal exists, writable, persistent and you have enough free space
| Why journalctl don't save my logs of the boot before forced shutdown? |
1,606,652,776,000 |
I'm running Gnome on Ubuntu 17.04. I had gnome-terminal in fullscreen, neovim in a tmux session, a background process compiling code, and Chromium running as well, when my system froze up on me. I could move the mouse cursor, barely, with extreme lag, but that's all I could do. I waited several minutes, then tried Ctrl-C, Ctrl-Alt-Delete, Alt-F2, but nothing responded.
Finally, I gave up and held down the power button until the machine shut down.
What I'm wondering is, how can I troubleshoot this? Is there something else I could have tried before forcing a shutdown? Are there logs I can inspect to see what happened? I tried journalctrl after rebooting, but it only shows logs from the current boot. I also see some log files in ~/.local/share/xorg/, but I'm not sure if they're relevant, or what to search for.
|
The following logs can help you debug your system from the last boot:
journalctl --boot=-1 | less
tail /var/log/syslog.1
tail /var/log/kern.log.1
tail /var/log/debug.1
tail /var/log/Xorg.0.log.old
| How to troubleshoot a (near total) freeze? |
1,327,810,934,000 |
In this question I asked how to prevent a media failure from halting the system boot process. However, I got two suggestions for /etc/fstab options
nobootwait
nofail
What is the difference between the two?
|
Firstly nofail allows the boot sequence to continue even if the drive fails to mount.
This is what fstab(5) says about nobootwait
The mountall(8) program that mounts filesystem during boot also recognises additional options that the ordinary mount(8) tool does not. These are:
bootwait which can be applied to remote filesystems
mounted outside of /usr or /var, without which mountall(8) would not hold up the boot for these;
nobootwait which can be applied to
non-remote filesystems to explicitly instruct mountall(8) not to hold up the boot for them;
optional which causes the entry to be ignored if the filesystem type is not known at boot time; and
showthrough
which permits a mountpoint to be mounted before its parent mountpoint (this latter should be used carefully, as it can cause boot hangs).
fstab(5) has this to say about nofail
nofail do not report errors for this device if it does not
exist.
| What is the difference between 'nobootwait' and 'nofail' in fstab? |
1,327,810,934,000 |
What is the difference between sync and async mount options from the end-user point of view? Is file system mounted with one of these options works faster than if mounted with another one? Which option is the default one, if none of them is set?
man mount says that sync option may reduce lifetime of flash memory, but it may by obsolete conventional wisdom. Anyway this concerns me a bit, because my primary hard drive, where partitions / and /home are placed, is SSD drive.
Ubuntu installer (14.04) have not specified sync nor async option for / partition, but have set async for /home by the option defaults. Here is my /etc/fstab, I added some additional lines (see comment), but not changed anything in lines made by installer:
# / was on /dev/sda2 during installation
UUID=7e4f7654-3143-4fe7-8ced-445b0dc5b742 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=d29541fc-adfa-4637-936e-b5b9dbb0ba67 /home ext4 defaults 0 2
# swap was on /dev/sda4 during installation
UUID=f9b53b49-94bc-4d8c-918d-809c9cefe79f none swap sw 0 0
# here goes part written by me:
# /mnt/storage
UUID=4e04381d-8d01-4282-a56f-358ea299326e /mnt/storage ext4 defaults 0 2
# Windows C: /dev/sda1
UUID=2EF64975F6493DF9 /mnt/win_c ntfs auto,umask=0222,ro 0 0
# Windows D: /dev/sdb1
UUID=50C40C08C40BEED2 /mnt/win_d ntfs auto,umask=0222,ro 0 0
So if my /dev/sda is SSD, should I - for the sake of reducing wear - add async option for / and /home file systems? Should I set sync or async option for additional partitions that I defined in my /etc/fstab? What is recommended approach for SSD and HDD drives?
|
async is the opposite of sync, which is rarely used. async is the default, you don't need to specify that explicitly in releases of nfs-utils up to and including 1.0.0. In all releases after 1.0.0, sync is the default, and async must be explicitly requested if needed.
The option sync means that all changes to the according filesystem are immediately flushed to disk; the respective write operations are being waited for. For mechanical drives that means a huge slow down since the system has to move the disk heads to the right position; with sync the userland process has to wait for the operation to complete. In contrast, with async the system buffers the write operation and optimizes the actual writes; meanwhile, instead of being blocked the process in userland continues to run. (If something goes wrong, then close() returns -1 with errno = EIO.)
SSD: I don't know how fast the SSD memory is compared to RAM memory, but certainly it is not faster, so sync is likely to give a performance penalty, although not as bad as with mechanical disk drives. As of the lifetime, the wisdom is still valid, since writing to a SSD a lot "wears" it off. The worst scenario would be a process that makes a lot of changes to the same place; with sync each of them hits the SSD, while with async (the default) the SSD won't see most of them due to the kernel buffering.
In the end of the day, don't bother with sync, it's most likely that you're fine with async.
| Difference between 'sync' and 'async' mount options |
1,327,810,934,000 |
One of my servers is set up to automatically mount a Windows directory using fstab. However, after my last reboot it stopped working. The line in fstab is:
//myserver/myfolder /mnt/backup cifs credentials=home/myfolder/.Smbcredentials
The .Smbcredentials file is:
username=myaccount
password=mypassword
domain=mydomain
I do a mount -a and I receive mount error 13 = Permission denied. If I do this enough it will lock out my Windows account, so I know it's trying. I've checked that my password is correct.
What am i doing wrong?
|
Thanks, but some more googling turned up the solution. It was using the wrong security type by default; this command worked:
$ sudo mount -t cifs //172.16.1.5/myshare/ /mnt/myshare \
-osec=ntlmv2,domain=MYDOMAIN,username=myusername,password=mypassword
| mount error 13 = Permission denied |
1,327,810,934,000 |
I'd like to know what is the exact mechanism (implementation) used to defer mounting until after network interface is up when one uses _netdev option in /etc/fstab?
Does systemd alter this behavior?
Also, what does delay_connect option to sshfs provide what _netdev does not?
From mount man page:
_netdev
The filesystem resides on a device that requires network
access (used to prevent the system from attempting to mount
these filesystems until the network has been enabled on the
system).
From sshfs man page:
-o delay_connect
delay connection to server
|
From man systemd.mount for version 231 of systemd:
Mount units referring to local and network file systems are
distinguished by their file
system type specification. In some cases this is not sufficient (for example network block device based mounts, such as
iSCSI), in which case _netdev may be added to the mount option string of the unit, which forces systemd to consider the mount
unit a network mount.
| How does _netdev mount option in /etc/fstab work? |
1,327,810,934,000 |
I know how to use /etc/fstab to automatically mount devices on boot or when doing sudo mount -a, which works perfectly fine. For example, here is my current line for my device
UUID=B864-497A /media/usbstick vfat defaults,users,noatime,nodiratime,umask=000 0 0
How do I achieve automatic mounting when this USB device with known UUID is plugged in while the system is already running, so that I don't have to run sudo mount -a after it is plugged in?
Additional info: I'm working on an up-to-date console-only Debian wheezy linux.
|
I use the usbmount package to automount USB drives on my Ubuntu server install. I have confirmed that the package exists for Wheezy too. Recently also added for Jessie.
sudo apt-get install usbmount
usbmount will automount hfsplus, vfat, and ext (2, 3, and 4) file systems. You can configure it to mount more/different file systems in /etc/usbmount/usbmount.conf. By default it mounts these file systems with the sync,noexec,nodev,noatime,nodiratime options, however this can also be changed in the aforementioned configuration file.
usbmount also supports custom mount options for different file system types and custom mountpoints.
| How to automatically mount an USB device on plugin-time on an already running system? |
1,327,810,934,000 |
It seems that I have added incorrect record to /etc/fstab:
//servername/share /mnt/share cifs defaults,username=myuser 0 0
When I did mount -a, it asked user password to mount network share. It seems that it cannot proceed without password on boot, so it is just hung.
How can I fix fstab to prevent boot failure?
|
It seems that I’ve found a solution:
At the GRUB prompt, hit A to append options.
Add init=/bin/bash to the end of the kernel command line and press Enter.
The system will boot to a prompt like bash-3.2# enter the following commands at the prompt
mount -o remount,rw /
Then edit the fstab:
vim /etc/fstab
Edit the fstab file commenting the errors by adding a # at the begining of each problematic line, save the file and reboot by pressing Ctrl+Alt+Del.
| How to fix boot failure due to incorrect fstab? |
1,327,810,934,000 |
mount -a works fine as a one-time action. But auto-mount of removable media reverts to settings that were in fstab at the last reboot.
How to make the OS reload /etc/fstab so auto-mounts use the new settings when media is connected?
The specific example seen with Raspbian (Debian) Stretch:
FAT-formatted SD card; configured fstab to auto-mount; rebooted; volume auto-mounts, but read-only.
Changed umask options in /etc/fstab; mount -a while media is connected, and volume is now read-write.
Unmount and re-insert the media; auto-mount works, but using the options in /etc/fstab from the last reboot, so volume is read-only.
Reboot; OS loads updated /etc/fstab; auto-mount works when media is connected, and volume is read-write. How to get this effect without a reboot?
FWIW, the (updated) /etc/fstab syntax was:
/dev/sdb1 /Volumes/boot vfat rw,user,exec,nofail,umask=0000 0 0
|
I suspect this is caused by systemd’s conversion of /etc/fstab; traditional mount doesn’t remember the contents of /etc/fstab.
To refresh systemd’s view of the world, including changes to /etc/fstab, run
systemctl daemon-reload
| How to force OS reload of fstab? |
1,327,810,934,000 |
The Arch Wiki on fstab specifies the options of / to be defaults,noatime, but on my installation the default fstab is created with the options of rw,relatime. The Arch Wiki covers the atime issues. What I am curious about is the defaults option. The man page for mount says:
defaults
Use the default options: rw, suid, dev, exec, auto, nouser, and async.
Note that the real set of all default mount options depends on kernel and filesystem type. See the beginning of this section for more details.
Are the default options used only if the defaults option is provided or are they used in all cases? Do I need defaults in my fstab?
|
You only need defaults if the field would otherwise be empty.
You can leave out the options field altogether if it's empty, unless the 5th or 6th fields are present. Field 5 is the dump frequency, rarely used nowadays. Field 6 fsck order, should be 1 for /, 2 for other filesystems mounted on boot and 0 otherwise. Fields 5 and 6 can be omitted if their value is 0, except that field 5 needs to be present if field 6 is.
Thus defaults is necessary in
/dev/foo /foo somefs defaults 0 1
(though you can use some other option like rw or ro instead)
But it can be omitted when you specify another option.
eg: The mounts below have the same effect.
/dev/foo /foo somefs ro 0 1
/dev/foo /foo somefs defaults,ro 0 1
But these also have the same effect.
/dev/foo /foo somefs defaults 0 0
/dev/foo /foo somefs
| Do you need to specify the "defaults" option in fstab? |
1,327,810,934,000 |
In the blkid output, some lines contain UUID and PARTUUID pairs and others only PTUUID. What do they mean?
In particular, why are two IDs required for a partition and why are some partitions identified by UUID/PARTUUID and some by PTUUID?
|
UUID is a filesystem-level UUID, which is retrieved from the filesystem metadata inside the partition. It can only be read if the filesystem type is known and readable.
PARTUUID is a partition-table-level UUID for the partition, a standard feature for all partitions on GPT-partitioned disks. Since it is retrieved from the partition table, it is accessible without making any assumptions at all about the actual contents of the partition. If the partition is encrypted using some unknown encryption method, this might be the only accessible unique identifier for that particular partition.
PTUUID is the UUID of the partition table itself, a unique identifier for the entire disk assigned at the time the disk was partitioned. It is the equivalent of the disk signature on MBR-partitioned disks but with more bits and a standardized procedure for its generation.
On MBR-partitioned disks, there are no UUIDs in the partition table. The 32-bit disk signature is used in place of a PTUUID, and PARTUUIDs are created by adding a dash and a two-digit partition number to the end of the disk signature.
| What is UUID, PARTUUID and PTUUID? |
1,327,810,934,000 |
I was making some changes to /etc/fstab, when this chicken and egg question occurred to me - if /etc/fstab contains the instructions for mounting the file systems, including the root partition, then how does the OS read that file in the first place?
|
When the boot loader calls the kernel it passes it a parameter called root. So once the kernel finished initializing it will continue by mounting the given root partition to / and then calling /sbin/init (unless this has been overriden by other parameters).
Then the init process starts the rest of the system by loading all services that are defined to be started in your default runlevel.
Depending on your configuration and on the init system that you use, there can be multiple other steps between the ones that I mentioned. Currently the most popular init systems on Linux are SysVInit (the traditional one), Upstart and Systemd. You can find more details about the boot process in this wikipedia article.
Here is a simplified example of my Grub config. The important part to answer your question is on the second to last line, there is a root=/dev/sda3:
menuentry 'Gentoo GNU/Linux' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-40864544-2d0f-471a-ab67-edd7e4754dae' {
set root='hd0,msdos1'
echo 'Loading Linux 3.12.6-gentoo-c2 ...'
linux /kernel-3.12.6-gentoo-c2 root=/dev/sda3 ro
}
In many configurations the kernel mounts / in read-only mode and all the rest of the options are set to the defaults. In /etc/fstab you might specify file system parameters which would then be applied once init remounts it.
| How is /etc/fstab accessed before root is mounted? |
1,327,810,934,000 |
For example, this is the first line of my /etc/fstab:
UUID=050e1e34-39e6-4072-a03e-ae0bf90ba13a / ext4 errors=remount-ro 0 1
And here's the output of df -h command (reporting free disk space):
honey@bunny:~$ df -T
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/vda ext4 30832636 4884200 24359188 17% /
none tmpfs 4 0 4 0% /sys/fs/cgroup
udev devtmpfs 498172 12 498160 1% /dev
tmpfs tmpfs 101796 320 101476 1% /run
none tmpfs 5120 0 5120 0% /run/lock
none tmpfs 508972 0 508972 0% /run/shm
none tmpfs 102400 0 102400 0% /run/user
From the two is it okay to deduce that UUID=050e1e34-39e6-4072-a03e-ae0bf90ba13a represents /dev/vda given that the first column in fstab is <file system>?
So, would it be okay if I modified /etc/fstab to this?
/dev/vda / ext4 errors=remount-ro 0 1
EDIT: If yes (to above question), why does the sudo blkid command show a different UUID for /dev/vda?
$ sudo blkid
/dev/vda: LABEL="DOROOT" UUID="6f469437-4935-44c5-8ac6-53eb54a9af26" TYPE="ext4"
What am I missing here?
Answer: I'd conclude (3) to be a bug in the cloud of my host. So yes, the UUID reported by blkid (or ls -l /dev/disk/by-uuid) should be the same as the one used in /etc/fstab.
|
The advantage of using the UUID is that it is independent from the actual device number the operating system gives your hard disk.
Imagine you add another hard disk to the system, and for some reason the OS decides that your old disk is now sdb instead of sda.
Your boot process would be screwed up if fstab points to the device name. But in case of the UUIDs, it is fine.
More detailed information about UUIDs can also be found on the blog post "UUIDs and Linux: Everything you ever need to know"
| Why does fstab use UUID instead of the actual file system name? |
1,327,810,934,000 |
I'm on an Arch Linux system, which means systemd.
In systemd there are native unit files for mountpoints, with the extension .mount. I've always just used /etc/fstab, which never gave me problems because systemd just picks up information from that. But now that I've actually read the documentation, I'm wondering if I should change to native systemd unit files.
The Arch Wiki suggests that there's no benefit, because it says to populate your fstab in the beginner's guide.
|
From man systemd.mount itself:
fstab
Mount units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details). Mounts listed in /etc/fstab will be converted into native units dynamically at boot and when the configuration of the system manager is reloaded. In general, configuring mount points through /etc/fstab is the preferred approach to manage mounts for humans. For tooling, writing mount units should be preferred over editing /etc/fstab. See systemd-fstab-generator(8) for details about the conversion from /etc/fstab to mount units.
Note that certain features are only implemented for fstab. For example when systemd in the initrd is used to mount the /usr filesystem as well as the / filesystem. systemd in the initrd reads etc/fstab on / and looks for an entry for /usr.
It also lets you use mount /mountpoint manually. systemd is generally happy for you to do this, e.g. it will update the status of the mount unit when you unmount or mount the filesystem.
| Is there any reason to move away from fstab on a systemd system? |
1,327,810,934,000 |
I am learning about linux security and struggling to understand why a USB stick with a character device on it is potentially dangerous.
If I have a USB stick with a bash executable that has setuid root on it, the danger is obvious: Anybody with such a USB stick can gain root privileges on my computer if I have an entry like
/dev/sdb1 /media/usbstick auto defaults 0 0
in my /etc/fstab because defaults includes suid.
But what about character devices? How can I use a character device to gain root privileges or break stuff if a USB stick with a character device on it gets mounted with dev or defaults?
|
Because access to the underlying device is controlled only by file permissions by default, so if your USB stick contains a POSIX filesystem with a world-writable device node corresponding to a real device in the system, you can use that device node to access the corresponding device as a "plain" user. Imagine a device corresponding to one of the audio devices, your webcam, /dev/sda (which is a block device rather than a character device, but the argument is the same)...
Here's an example to make things clearer. Say you want to access /dev/sda (then you can pretty much do anything you want with the contents of the disk, including planting a program which would allow you to become root; this is a block device but the problem is the same with character devices). On your target system, ls -l /dev/sda shows
brw-rw---- 1 root disk 8, 0 Sep 8 11:25 sda
This means /dev/sda is a block device (the b at the beginning of the line), with major number 8 and minor number 0 (the 8, 0 in the middle of the line). The device is only accessible to root (read/write) and members of the disk group (also read/write).
Now imagine on this system you can't become root but for some reason you can mount USB sticks as a user without nodev. On another system, where you are root, you can create a corresponding special file on your USB key:
mknod -m 666 usersda b 8 0
This will create a special file called usersda, readable and writable by everyone.
Mount the key on your target system and hey presto, you can use the usersda device in the same way as /dev/sda, but with no access restriction...
(This will work even with encrypted file systems, as long as you are able to access the decrypted mapper device: create device which matches the appropriate /dev/mapper entry.)
| Why is "nodev" in /etc/fstab so important? How can character devices be used for hacking? |
1,327,810,934,000 |
I'm on Ubuntu 14.04.
I pasted something incorrect (from a tutorial) into my /etc/fstab file. As a result, the root file system will not mount when the machine boots up.
I know what needs to be fixed in /etc/fstab, but I cannot save the file (or any file) because the system boots as read only.
As root, I tried:
mount -o remount,rw /
to no avail. The error message cited the section of bad options that I pasted into /etc/fstab.
I read some stuff about booting into single user mode by adding 'single' to the end of the kernel parameter. I can't seem to find the kernel parameter. On the grub menu, I highlight Ubuntu and press 'e' which brings up a file with some sort of configuration, but there is no 'kernel' parameter to be found.
I'm relatively new to linux. Can anyone help me figure out a way to fix my /etc/fstab file so that Ubuntu will boot normally?
|
To get things back to where they should be, I:
Highlighted 'Ubuntu' at the boot menu
hit 'e' to edit the configuration
in the line starting with linux=, I switched the 'ro' to 'rw' and added the word 'single' at the very end of the line
hit f10 to boot
once it booted, as root, I did:
mount -o remount,rw /
as root, I edited /etc/fstab to get it where it needed to be
rebooted normally and everything seems to be fixed
| How to edit /etc/fstab when system boots to read only file system? |
1,327,810,934,000 |
I currently have an extra HDD which I am using as my workspace. I am trying to get it to mount automatically on reboots using the following line added to /etc/fstab
/dev/sdb1 /media/workspace auto defaults 0 1
This works to auto mount it, however I would like to restrict read/write access to users belonging to a specific group. How would I go about doing this in /etc/fstab? Can I simply just use chown or chmod to control the access?
|
If the filesystem type is one that doesn't have permissions, such as FAT, you can add umask, gid and uid to the fstab options. For example:
/dev/sdb1 /media/workspace auto defaults,uid=1000,gid=1000,umask=022 0 1
uid=1000 is the user id.
gid=1000 is the group id.
umask=022 this will set permissions so that the owner has read, write, execute. Group and Others will have read and execute.
To see your changes you do not need to reboot. Just umount and mount again without arguments. For example:
umount /media/workspace
mount /media/workspace
But make sure to do not have any process (even your shell) using that directory.
| Automatically mount a drive using /etc/fstab, and limiting access to all users of a specific group |
1,327,810,934,000 |
Using Fedora 24, I had configured in /etc/fstab an external usb drive:
UUID=6826692e-79f4-4423-8467-cef4d5e840c5 /backup/external ext4 defaults 0 0
When I unplugged the usb disk and reboot, it does not boot
That is the error message:
[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-6826692e\x2d79f4\x2d4423\x2d8467\x2dcef4d5e840c5.device.
[DEPEND] Dependency failed for /backup/external.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Relabel all filesystems, if necessary.
[DEPEND] Dependency failed for Mark the need to relabel after reboot.
Why does not boot? is it a bug? a feature? of systemd?
I know that was a mistake of me, I had to set options to "noauto", but anyway Why booting process stops because a non-critical directory of FHS is missing?
|
Using the nofail mount option will ignore missing drives during boot. See man pages fstab(5) and mount(8).
nofail Do not report errors for this device if it does not exist.
So your fstab line should instead look like:
UUID=6826692e-79f4-4423-8467-cef4d5e840c5 /backup/external ext4 defaults,nofail 0 0
| Cannot boot because missing external disk |
1,327,810,934,000 |
..and what are the consequences of the different methods?
I have been trying some things with the mounting of an sda2 partition.
Mounting in fstab, not mounting in fstab but from the file manager.
So far, if I am right, I learned that by mounting in fstab, a partition is mounted automatically at startup.
But this mounted partition is not shown under 'devices' in the file manager, whereas the root partition and cdrom for example are shown.
When you want to have it under devices in the sidebar, a partition should not be mounted in fstab but by clicking it in the file manager. Is that correct?
But which way to go if you want both? Automatically mounted at startup AND being shown in the sidebar of file manager?
|
This is documented (at least for gnome-shell/nautilus) in gvfs-udisks2-volume-monitor:
The gvfs-udisks2-volume-monitor process is responsible for the disks,
media, mounts and fstab entries shown in the desktop user interface.
..........................................
A device is either mounted (in which case its directory is known) or
it's not. If the device is not mounted, then its directory is known
only if it's referenced in the /etc/fstab file.
Further down comes the explanation:
If the directory for a device is known and outside /media, $HOME
(typically /home/foo) or /run/media/$USER then the device is not shown
in the user interface. Additionally, if any of component directories
in its directory starts with a dot ("."), the device is not shown
either. This policy may be overriden by use of the options x-gvfs-show
and x-gvfs-hide.
To sum up:
Partitions listed in /etc/fstab would (by default) only show up if they're mounted under /media, $HOME or /run/media/$USER. If you want a partition to be automatically mounted at system startup and also listed in the file manager sidebar, the easiest way is to mount it via /etc/fstab under one of those three locations.
If you want the partition to be mounted under a different directory (e.g. /mnt) and still be shown in the sidebar, you can override the default behaviour by adding x-gvfs-show to your mount options in fstab:
UUID=5a1615ca-cffd3124917a /mnt/storage ext4 rw,noatime,discard,x-gvfs-show 0 2
Partitions not listed in /etc/fstab are handled by udisks2 and will be mounted under /run/media/$USER/VolumeName or /media/VolumeName depending on the value of UDISKS_FILESYSTEM_SHARED1 hence they will be shown under Devices in the sidebar. However, they are not automatically mounted. A user could automatically mount them at session startup with udisksctl, e.g. adding:
udisksctl mount -b /dev/sdb2 -t ext4
to the session startup scripts.
1
man udisks:
UDISKS_FILESYSTEM_SHARED
If set to 1, the filesystem on the device will be mounted in a shared directory e.g. /media/VolumeName)
instead of a private directory (e.g. /run/media/$USER/VolumeName) when the Filesystem.Mount() method is handled.
| What is the difference between mounting in fstab and by mounting in file manager |
1,327,810,934,000 |
The way I understand it, initramfs is responsible for loading the "real" root filesystem.
Now, there are two places where we define that root. First we put an entry in /etc/fstab. Second, we put the device on the kernel boot commands e.g. root=/dev/sda1.
Which one does initramfs use to determine where is the root filesystem? If it uses the root kernel parameter, why do we have an entry in /etc/fstab? The second option, (it reads /etc/fstab), is quite illogical because the /etc/fstab file is on the very root device that initramfs is trying to mount in the first place.
Very confusing stuff.
|
As you stated, the purpose of initramfs is to get the "real" root filesystem mounted (it can do other things too, but this is the common task).
Without an initramfs, the kernel will normally mount a partition up as read-only and then pass control over to /sbin/init. An initramfs just takes over this task from the kernel, usually when the root filesystem isn't a normal partition (mdraid, lvm, encrypted, etc).
Now, aside from the background on initramfs, your /etc/fstab resides on your root filesystem. As such, when initramfs is launched, that root filesystem isn't there, and so it can't get to the fstab (chicken and egg problem).
Instead we have to pass a parameter into the kernel boot arguments for the initramfs to use. Normally this is something like root=/dev/sdX. However it might also do something to automatically figure out where your root device is, and so there's no parameter at all. Since it's just software (generally a script), it can really do anything it wants for mounting the root device.
Now, as stated earlier, the kernel will mount the real root as read-only. The initramfs should do exactly this. Once the initramfs is done, the system proceeds booting exactly as if there were no initramfs at all, and /sbin/init starts up. This init then starts all your normal boot scripts, and it's the job of one of these scripts to read /etc/fstab, switch root to read-write, and mount all your other filesystems.
| Does initramfs use /etc/fstab? |
1,327,810,934,000 |
From my understanding of /etc/systemd options, noauto means that the device will not be mounted at boot time (or with mount -a).
Is there any situation where adding nofail changes the behaviour if noauto is already given, or is it totally redundant?
man systemd.mount(5) says:
With noauto, this mount will not be added as a dependency for local-fs.target or remote-fs.target. This means that it will not be mounted automatically during boot, unless it is pulled in by some other unit.
With nofail, this mount will be only wanted, not required, by local-fs.target or remote-fs.target. This means that the boot will continue even if this mount point is not mounted successfully.
What about automount situations?
|
Just for the record:
For an external USB disk which is usually not connected at startup, I have an fstab entry
/dev/disk/by-label/data /data xfs noauto,user,noatime 0 0
When booting there is no error as noautokeeps the system from trying to mount. When I try to mount manually without the drive connected, I immediately get the error
~$ mount /data
mount: special device /dev/disk/by-label/data does not exist
~$
If I change the line in fstab to
/dev/disk/by-label/data /data xfs noauto,nofail,user,noatime 0 0
there is no error reported, even when the drive is not available:
~$ mount /data
~$
System: Ubuntu 16.04 with systemd.
| /etc/fstab: meaning of "nofail" if "noauto" is already specified |
1,327,810,934,000 |
I'm learning how to set up a tmpfs in fstab for my www-data user and I was wondering if I can use the actual user/group name instead if the numeric ids (personal preference)?
I'm on Debian with ext4, formatted with "msdos" during setup.
It seems to be working, but I'm wondering if this is a Debian-specific feature or will it work across platforms (I like portability)?
Here's what I've got:
$ vim /etc/fstab
# PHP temporary files.
tmpfs /tmpfs/php-session tmpfs defaults,size=512M,mode=1700,uid=www-data,gid=www-data,noexec,nodev,nosuid 0 0
tmpfs /tmpfs/php-upload tmpfs defaults,size=256M,mode=1700,uid=www-data,gid=www-data,noexec,nodev,nosuid 0 0
|
The Linux mount program interprets non-numeric parameters to uid and gid options as user and group names respectively. This applies to all filesystem types. It works both if the options come from the command line and if they come from /etc/fstab.
Source: source (old (parse_opt), new (mnt_optstr_fix_gid, mnt_optstr_fix_uid)).
| Can fstab options uid and gid be the user-group name or must they be numeric? |
1,327,810,934,000 |
I have done many obscure system optimizations in the past, but I got rid of most of them after powertop told me I should set my USB ports to autosuspend, which forced them to an eternal sleep, and also after I realized the benefits of a higher swappiness.
But today, while looking at /etc/fstab, I noticed I had set the option commit=60 for / and /home. I remember that this was an optimization for laptops, to reduce the amount of writes to the disk, thus saving battery. But then I became concerned that this might cause data loss (sometimes my battery gets disconnected, and then on boot fsck tells me about a couple of orphan inodes).
While searching for an explanation for this option, I came to the following explanations (the second seems to contradict my previous understanding):
$ man mount | awk '/commit=/,/^$/'
commit=nrsec
Sync all data and metadata every nrsec seconds. The default value is 5 seconds.
Zero means default.
https://forums.gentoo.org/viewtopic-p-4088752.html
commit=60 stops the "immediate" (default of 5 seconds) prioritization of writes of over reads, caching the writes for a few more seconds later. This is good in the situation of heavy reads and writes mixed together, where the user wants the reads to take priority, so that the processor can be kept busy rather than pause while waiting for the writes to finish before it can continue reading.
A real-world example I have seen is waiting several seconds for the Gnome pull-down menu to appear, for seemingly no reason. The reason was that the disk was busy writing, so the CPU had to wait for the writing to finish before it could get all the data from the disk to be able to show the menu.
What does commit really do? Are there really advantages of increasing it (like responsiveness and power savings)? May it actually cause data loss?
|
What does commit really do?
I think one of the best explanations was given here by allquixotic.
Are there really advantages of increasing it (like responsiveness and
power savings)? May it actually cause data loss?
As per the ext4 official documentation:
Ext4 can be told to sync all its data and metadata every 'nrsec' seconds. The default value is 5 seconds. This means that if you lose
your power, you will lose as much as the latest 5 seconds of work
(your filesystem will not be damaged though, thanks to the
journaling). This default value (or any low value) will hurt
performance, but it's good for data-safety. Setting it to 0 will have
the same effect as leaving it at the default (5 seconds). Setting it
to very large values will improve performance.
Increasing commit value means you might lose as much as the latest N seconds of work (where N = commit interval) though most of the time this won't happen as software can still call fsync() and get its data written to disk, overriding the commit setting. You could look at it as "write everything to disk at least this often".1
On the other hand, it means less writes (which makes it quite popular among ssd users) and better performance (multiple writes are combined into one single larger write, updates to previous writes within the commit time frame are cancelled out).
As to the power savings, according to this page, it turns out that nowadays increasing commit value does not save power.
| Advantages/disadvantages of increasing "commit" in fstab |
1,327,810,934,000 |
In my /etc/fstab file I have an entry for my swap as follows:
/root/swap swap swap sw 0 0
I have other machines and also I've seen online that sometimes they put default or xfs or other options. Then, I'm a little confused on what 'sw' means and what's for, and also which one would be the best option to put there and why.
|
From the fstab manual on my system:
The fourth field, fs_mntops, describes the mount options associated with the filesystem. It is formatted as a comma separated list of options. It contains at least the type of mount (see fs_type below) plus any additional options appropriate to the filesystem type. [...]
If fs_type is “rw”, “rq”, or “ro”
then the filesystem whose name is given in the fs_file field is normally
mounted read-write or read-only on the specified special file. If
fs_type is “sw” then the special file is made available as a piece of
swap space by the swapon(8) command at the end of the system reboot
procedure.
So basically, sw is used to tell swapon (or swapctl on my system) that this is a valid candidate for use as swap space that will be added as part of the system start-up routine.
From the manual describing swapctl -A:
This option causes swapctl to read the /etc/fstab file for devices and files with an “sw” type, and adds all these entries as swap devices. If no swap devices are configured, swapctl will exit with an error code.
That's on OpenBSD. On the Ubuntu Linux system that I have access to, neither manual mentions sw as a mount option for swap for some reason.
| What 'sw' means in the fstab swap entry for 'mount options' column |
1,327,810,934,000 |
I get that I can use mount to set up / directories and that I can use the /etc/fstab to remount them on reboot.
Testing the fstab file is also fun with mount -faV.
When I'm looking at the fstab file, the number of space is disconcerting. I would have expected one space (like a separator between command parameters) or four spaces (like a tab). I'm seeing seven spaces at a time, almost as convention.
My question is: What are all the spaces in the /etc/fstab for?
(Perhaps also - Will it matter if I get the wrong number?)
|
The number of spaces is a way to cosmetically separate the columns/fields. It has no meaning other than that. I.e. no the amount of white space between columns does not matter.
The space between columns is comprised of white space (including tabs), and the columns themselves, e.g. comma-separated options, mustn't contain unquoted white space.
From the fstab(5) man page:
[...] fields on each line are separated by tabs or spaces.
and
If the name of the mount point contains spaces these can be escaped as `\040'.
Example
With the following lines alignment using solely a single tab becomes hard to achieve. In the end the fstab without white space looks messier than what you consider disconcerting now.
/dev/md3 /data/vm btrfs defaults 0 0
/var/spool/cron/crontabs /etc/crontabs bind defaults,bind
//bkpsrv/backup /mnt/backup-server cifs iocharset=utf8,rw,credentials=/etc/credentials.txt,file_mode=0660,dir_mode=0770,_netdev
Can you still see the "columns"?
| What are all the spaces in the /etc/fstab for? |
1,327,810,934,000 |
I am using OpenStack Cloud and using LVM on RHEL 7 to manage volumes. As per my use case, I should be able to detach and attach these volumes to different instances.
While updating fstab, I have used defaults,nofail for now but I am not sure what exactly I should be using. I am aware of these options:
rw, nofail, noatime, discard, defaults
But I don't how to use them. What should be the ideal configuration for my use case ?
|
As said by @ilkkachu, if you take a look at the mount(8) manpage, all your doubts should go away. Quoting the manpages:
-w, --rw, --read-write
Mount the filesystem read/write. This is the default. A synonym is -o rw.
Means: Not needed at all, since rw is the default, and it is part of the defaults option
nofail Do not report errors for this device if it does not exist.
Means: If the device is not enable after you boot and mount it using fstab, no errors will be reported. You will need to know if a disk can be ignored if not mounted. Pretty useful on usb drivers, but i see no point on using this on a server...
noatime
Do not update inode access times on this filesystem (e.g., for faster access on the
news spool to speed up news servers).
Means: No read operation is a "pure" read operation on filesystems. Even if you only cat file for example, a little write operation will update the last time the inode of this file was accessed. It's pretty useful on some situations(like caching servers), but it can be dangerous if used on sync technologies like Dropbox. I'm no one to judge here what is best for you, if noatime set or ignored...
discard/nodiscard
Controls whether ext4 should issue discard/TRIM commands to the underlying block device
when blocks are freed.This is useful for SSD devices and sparse/thinly
-provisioned LUNs, but it is off by default until sufficient testing has been done.
Means: TRIM feature from ssds. Take your time to read on this guy, and probe if your ssd support this feature(pretty much all modern ssds suport it). hdparm -I /dev/sdx | grep "TRIM supported" will tell you if trim is supported on your ssd.
As for today, you could achieve better performance and data health by Periodic trimming instead of a continuous trimming on your fstab. There is even a in-kernel device blacklist for continuous trimming since it can cause data corruption due to non-queued operations.
defaults
Use default options: rw, suid, dev, exec, auto, nouser, and async.
tl;dr: on your question, rw can be removed(defaults already imply rw), nofail is up to you, noatime is up to you, the same way discard is just up to your hardware features.
| When and where to use rw,nofail,noatime,discard,defaults? |
1,327,810,934,000 |
Question: What does /dev/disk/by-pathdescribe? And where is this documented?
Going through the meaning of what is displayed in the folders /dev/disk/by- I've got that far, and I wonder is this correct?
by-id → based upon the serial number of the hardware devices
by-label → Whatever name was set manually for this disk
by-path → ?!
by-uuid → Universal Unique Identifier: a uniquely created string to identify the disk [done so through the system]
[Note: I work on GNU/Linux Debian 7, Crunchbang, if this matters…]
|
Mountpoint /dev is devtmpfs filesystem and managed by udev completely.
So for details we have to go to udev configuration.
2 udev rules are handling this typically
$ grep -ri '/dev/disk' /usr/lib/udev/rules.d/
/usr/lib/udev/rules.d/60-persistent-storage.rules:# persistent storage links: /dev/disk/{by-id,by-uuid,by-label,by-path}
/usr/lib/udev/rules.d/13-dm-disk.rules:# These rules create symlinks in /dev/disk directory.
60-persistent-storage.rules mentions
# by-path (parent device path)
ENV{DEVTYPE}=="disk", DEVPATH!="*/virtual/*", IMPORT{builtin}="path_id"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", SYMLINK+="disk/by-path/$env{ID_PATH}"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="?*", SYMLINK+="disk/by-path/$env{ID_PATH}-part%n"
Finally ID_PATH is a unique identificator for a device based on it's physical HW location / connection (eg. something like ID_PATH=pci-0000:02:04.0-scsi-0:0:0:0).
ID_PATH comes from builtin udev program called path_id (eg. for /sys/block/sdc)
$ udevadm test-builtin path_id /sys/block/sdc
calling: test-builtin
=== trie on-disk ===
tool version: 204
file size: 5632867 bytes
header size 80 bytes
strings 1260755 bytes
nodes 4372032 bytes
load module index
ID_PATH=pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0
ID_PATH_TAG=pci-0000_00_14_0-usb-0_1_1_0-scsi-0_0_0_0
We can relate it to
drwxr-xr-x 6 root root 0 Aug 15 02:30 /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/
Ultimately, if anybody is interested in details consult the source code
http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-path_id.c
| understanding /dev/disk/by- folders |
1,327,810,934,000 |
I am running Oracle Linux 7 (CentOS / RedHat based distro) in a VirtualBox VM on a Mac with OS X 10.10. I have a Synology Diskstation serving as an iscsi target.
I have successfully connected to the Synology, partitioned the disk and created a filesystem. It is refernced as /dev/sdb and the partition is /dev/sdb1. Now, what I would like to do is create a mount point so I can easily access it:
mount /dev/sdb1 /mnt/www
That command works. But obviously, it isn't persistent across a reboot. No worries...into /etc/fstab we go.
First, I got the UUID of the partition to ensure I am always using the correct device:
blkid /dev/sdb1
Result:
/dev/sdb1: UUID="723eb295-8fe0-409f-a75f-a26eede8904f" TYPE="ext3"
Now, I inserted the following line into my /etc/fstab
UUID=723eb295-8fe0-409f-a75f-a26eede8904f /mnt/www ext3 defaults 0 0
Upon reboot, the system crashes and goes into maintenance mode. If I remove the line I inserted, all works again. However, I am following the instructions verbatim from Oracle-Base
I know I am missing something..can anyone point me in the right direction?
|
Just change the parameter "defaults" by "_netdev", like this:
UUID=723eb295-8fe0-409f-a75f-a26eede8904f /mnt/www ext3 _netdev 0 0
This way the mount point will be mounted only after the network start correctly.
| Mount iscsi drive at boot - system halts |
1,327,810,934,000 |
What is the difference between using auto.master and having autofs automount your NFS mountpoints versus just putting the info in fstab? Linux Red-Hat 5/6
|
With fstab, the advantage is the remote filesystem will be mounted on system (when the noauto mount option is not used).
Additionally, it depends how the mount point is defined. There are two options which determines the recovery behaviour when the NFS client can't reach the server. With the hard option (default one), the boot process will pause if there is a problem mounting the nfs share and repeated tries are made to mount the share indefinitely. If the soft option is used, then the mount fails after retrans retransmissions have been sent.
On the other hand, autofs only mounts nfs shares when they are needed and accessed.
| Linux: difference between using autofs with NFS and just using fstab |
1,327,810,934,000 |
Can I include another file in my fstab file?
I.e. can I have fstab execute lines from another file at an arbitrary point, and then return to the main file when completed?
|
Generally not, but with newer versions of mount/swapon/fsck... on Linux (from util-linux 2.19) at least, you can have more files (with .fstab extension) in /etc/fstab.d. So you can have a /etc/fstab.d/00_header.fstab, /etc/fstab.d/50_middle.fstab, /etc/fstab.d/99_end.fstab.
Another approach if all you want is mount -a to run some command is have an entry with your own filesystem type and create a /sbin/mount.own that does the work for you.
Note that recent versions of Ubuntu have that mountall that might get in the way.
Also note that some distributions process mounts in several stages using -t fstypes, which you may need to take into account as well.
| Can I include another file in fstab |
1,327,810,934,000 |
I have an ext4 mounted with the flags rw,suid,dev,exec,auto,user,async in /etc/fstab but running mount after mounting gives rw,nosuid,nodev,noexec,relatime,user.
How do I get it to mount exactly as written in /etc/fstab and (optionally) why is there such a difference?
I'm using Arch Linux.
|
You must put the exec, suid and dev options after the user option, because user implies noexec, nosuid and nodev.
See mount man page for details:
user
Allow an ordinary user to mount the filesystem. The name of the mounting user is written to the mtab file (or to the private libmount file in /run/mount on systems without a regular mtab)
so that this same user can unmount the filesystem again.
This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line user,exec,dev,suid)
| Drive mounted with flags different from /etc/fstab - not respecting suid, dev, or exec |
1,327,810,934,000 |
What is the difference between nointegrity, noatime and relatime? And what is the best option for a SSD? I am using ext4 as my filesystem. And why disabling journaling on my system, data loss can occur? Can I use for example nointergrity & noatime together in fstab, or only one option is accepted?
Thank you!
|
The nointegrity option has no direct relation with atime, noatime, relatime or nodirtime. You could choose only one of the time options for files. Using noatime imply nodirtime. So, noatime will make all files and directories noatime.
In my system I can not find the option nointegrity for ext4. Please check the man mount in the section for ext4 to find available options for it. The only options ext4 allows for journaling are journal, ordered and writeback. If you don't want possible filesystem corruption on a crash, do not use writeback.
So, for an SSD, make sure the discard option is enabled (it is by default). It will probably be safer to use relatime. The noatime may be infinitesimally faster but there is some risk of some programs failing to work correctly.
In ext4 there is no nointegrity option, but, in any case, do not use it if you care about having reliable data (you have been warned!).
| Difference between nointegrity, noatime & relatime |
1,327,810,934,000 |
The server is listening on port '8765' and requires a SSH key for authentication.
I can mount the remote directory using this command:
sshfs -o idmap=user,port=8765 stephen@server:/export/usb2T /mnt/usb2T
The server recognizes my SSH public key.
I have seen that as an fstab entry for the standard SSH port this will be :
stephen@server:/export/inbox /mnt/inbox fuse.sshfs defaults,_netdev 0 0
But I will need to add the server's listening port and the client user's SSH public key.
How do I do that?
|
I want this sshfs mount to:
happen only after network connection is achieved;
for the files on the mount to be executable.
Pulling together the info provided in somethingSomething's excellent post along with the options required we have this:
stephen@server:/export/inbox /mnt/inbox fuse.sshfs x-systemd.automount,x-systemd.requires=network-online.target,_netdev,user,idmap=user,transform_symlinks,port=2314,identityfile=/home/stephen/.ssh/id_rsa,allow_other,default_permissions,uid=1000,gid=1000,exec 0 0
The additional options are :
x-systemd.automount creates an automount unit for systemd
x-systemd.requires=network-online.target attempts mount only after network connection is achieved
exec make files on the mounted drive executable.
| How to make an fstab entry for sshfs on non-standard SSH port and using ssh key |
1,327,810,934,000 |
I'm running a modified WD MyCloud (Gen 1) NAS with Debian 8 (Jessie) installed on it.
Due to the nuances of the device, I can't resize the root partition, and am struggling with space on it.
To remedy this, I've rsynced the /var and /usr directories on to the main data partition.
I've then added the following lines to the /etc/fstab:
/data/rootfs/var /var none defaults,bind 0 0
/data/rootfs/usr /usr none defaults,bind 0 0
Upon rebooting, I find that the /var directory has successfully been mounted, but that the /usr directory has not.
If I then run mount -a, I get no errors, and the /usr directory is correctly mounted.
What's going wrong?
|
If you are using systemd, mounts are done in parallel (by dynamically converting the fstab entries into mount units), line ordering is not preserved as would be expected from pre-systemd experience.
You have an untold dependency that's not automatically guessed: mounting /data/ before mounting /usr. WIthout it you get a race condition.
You have to manually add the dependency as a pseudo mount option, using x-systemd.requires=. So if the previous mountpoint that should be mounted is /data, this should make it work:
/data/rootfs/var /var none x-systemd.requires=/data,bind 0 0
/data/rootfs/usr /usr none x-systemd.requires=/data,bind 0 0
In case somebody else finds this question, but the use case is for /data being a remote network filesystem like NFS, the pseudo mount option _netdev (pre-systemd option also recognized by systemd) must also be added on the /data/rootfs/usr entry to get everything working fine, because none can't hint this automatically and not having it might then confuse the x-systemd.requires= resolution.
| /etc/fstab fails to bind mount on boot, but running mount -a works correctly |
1,327,810,934,000 |
I recently upgraded my kernel from 3.16.4 (Debian jessie) to 4.9.0 (Debian stretch).
Everything was fine, until I tried to "Hibernate" (suspend to disk).
When I use Hibernate option in LXDE, it appears to hibernate. I can hear the disk spindle ticking and writing data. But the problems appears when resuming from hibernation. The kernel successfully restores the image from swap, but then freezes and reboots, with all that work lost. I could not find answer anywhere on internet. The people are just solving some mistakes around not setting /etc/initramfs-tools/conf.d/resume or have set kernel paramters, or have wrong entry in /etc/fstab. I have these correct. Correct UUID in /etc/initramfs-tools/conf.d/resume, correct fstab and not set resume kernel paramter.
I moved the swap partition outside of the extended partition to primary. The UUID was saved and applied to the new swap.
The system reaches "Restoring image 100%" and then "Suspending consoles", and then it powers off and boots normally, with all work lost.
Tried clean install, but without luck.
Happens only on i386 (32-bit x86), amd64 (64-bit x86) does not suffer.
Disk partition table layout:
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ext4 HDD <ROOT-UUID> /
└─sda2 swap HDD-SWAP <SW-UUID> [SWAP]
sr0
The sda2 was logical(resides-inside-extended) before the upgrade.
Fstab:
UUID=<ROOT-UUID> / ext4 errors=remount-ro 0 1
UUID=<SW-UUID> none swap sw 0 0
/etc/initramfs-tools/conf.d/resume
RESUME=UUID=<SW-UUID>
Kernel cmdline
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-686-pae root=UUID=<ROOT-UUID> ro quiet
System information:
Computer: Compaq CQ60-120ec
Swap Size: 3.5GiB
Processor: AMD Athlon X2 64 QL-66
GPU: Nvidia Geforce 8200M G
Memory: 2G DDR2 667MHz
Desktop Environment: LXDE
Debian Version: 9 (stretch)
Kernel version: 4.9.0-3
Graphics Driver: nvidia legacy 304xxx
(I know the processor is 64bit but it came with 32bit os originally, so I thought it was 32bit until I examined /proc/cpuinfo)
|
The issue is due to a conflict between hibernate and kASLR on x86-32. This can be solved by disabling kASLR with the nokaslr kernel boot option. x86-64 is not affected.
For Grub this can be done by editing /etc/default/grub and adding nokaslr to the boot options, e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nokaslr"
Then run update-grub to update the configuration and reboot to give it a try.
I had exactly the same issue and it seems that only the PAE kernel is affected by that issue. The same kernel without PAE works without issues.
The workaround for me was to install linux-image-686 and uninstall linux-image-686-pae and linux-image-4.9.0-4-686-pae. The exact kernel version may change over time due to upgrades, but basically the currently running PAE kernel need to be replaced with a kernel without PAE.
It has actually nothing to do with PAE support of the CPU, as my CPU supports PAE according to /proc/cpuinfo. But PAE is anyway not of much use on old notebooks.
It has also nothing to do with kernel 4.9 PAE as the same issue happens with kernel 4.13 PAE from Debian backports.
| Hibernation resume fail on linux kernel 4.9.0, Debian 9 |
1,327,810,934,000 |
I have a 1TB HDD (/dev/sda1, mount point /run/media/<name>/4733A97E4133EADF) that I'm trying to mount as read-write, but I can only get it to mount as read-only.
System:
$ uname -a
Linux <hostname> 4.10.6-1-ARCH #1 SMP PREEMPT Mon Mar 27 08:28:22 CEST 2017 x86_64 GNU/Linux
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
└─sda1 ntfs 4733A97E4133EADF /run/media/<name>/4733A97E4133EADF
sdb
├─sdb1 swap d9cea12d-5273-49ef-8950-3cd662fe63c7 [SWAP]
└─sdb2 ext4 e09a8578-53e9-4c26-9a97-a47b6350a1ab /
...
What I've tried
Adding a fstab entry to automount the drive on boot:
$ cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb2
UUID=e09a8578-53e9-4c26-9a97-a47b6350a1ab / ext4 rw,relatime,data=ordered 0 1
# /dev/sdb1
UUID=d9cea12d-5273-49ef-8950-3cd662fe63c7 none swap defaults 0 0
# /dev/sda1
UUID=4733A97E4133EADF /run/media/<name>/4733A97E4133EADF ntfs defaults,users,user 0 0
I've tried with defaults, defaults,users, and defaults,users,user. Rebooted after each change, but the drive is still mounted as read-only:
$ ls -l /run/media/<name>
...
dr-x------ 1 root root 4096 Mar 28 17:35 4733A97E4133EADF
...
Manually remounting:
$ sudo mount -o remount,rw /dev/sda1 /run/media/<name>/4733A97E4133EADF
mount: cannot remount /dev/sda1 read-write, is write-protected
$ sudo umount /run/media/<name>/4733A97E4133EADF
$ sudo mount -o rw /dev/sda1 /run/media/<name>/4733A97E4133EADF
At this point, the command just hanged for a few minutes, so I terminated it.
$ sudo umount /run/media/<name>/4733A97E4133EADF
$ sudo mount /dev/sda1 /run/media/<name>/4733A97E4133EADF
No change.
As of yet, I have not been able to write to the drive at all (from this system, at least), even as root.
chown, chmod have no effect because the filesystem is read-only.
What must I do to (auto)mount this drive as read-write, with normal (non-root) user access?
Have tried solutions from the following:
How do I remount a filesystem as read/write? | Ask Ubuntu
Ubuntu remount a root mount that's changed to ro as rw without rebooting | Server Fault
|
Although @ingopingo answered the question in one of the comments, i am going to write an answer with further information now.
By default the Linux kernel only supports reading from the NTFS file system. For read/write access you will need a read-write NTFS driver like the ntfs-3g package from extra repository.
After installation with sudo pacman -S ntfs-3g you are able to mount your NTFS partitions the usual way with sudo mount /path/to/ntfs /mount/point. This is possible due to a symlink of /usr/bin/mount.ntfs to /usr/bin/ntfs-3g.
Note: You need to have root privilegs to mount the filesystem.
Requirements for an exception are listed in the ntfs-3g-FAQ.
Using the default settings the NTFS-partition will be mounted at boot. Put the following in your /etc/fstab:
/path/to/ntfs /mount/point ntfs-3g defaults 0 0
To be able to read-write with a non-root user, you have to set some additional options (username has to be changed to your username):
/path/to/ntfs /mount/point ntfs-3g uid=username,gid=users,umask=0022 0 0
| Unable to mount drive as read-write |
1,327,810,934,000 |
I can mount a drive using 9p on to my libvirt guest using the following command...
mount -t 9p trans=virtio,version=9p2000.L,rw share /machine/host
...but can't work out what to add to /etc/fstab to do it on startup.
I have tried...
share /machine/host 9p trans=virtio,version=9p2000.L,rw 0 0
...but the guest fails to boot (and I get taken to Emergency mode).
|
This did it for me.
https://superuser.com/q/502205/524816
All credit to @roiama for the answer (in question comments).
| How to mount 9p drive using /etc/fstab? |
1,346,289,248,000 |
I have a home partition which is shared by mulitple distros on the same box. I'm using bind mounts from fstab. Each Linux install has something like this:
UUID=[...] /mnt/data ext4 nodev,nosuid 0 2
/mnt/data/arch /home none defaults,bind 0 0
/mnt/data/files /files none defaults,bind 0 0
The disadvantage is, of course, that /mnt/data/arch and /mnt/data/files are now mounted twice. On a hunch, I tried umount /mnt/data, which seems to work as I had hoped: according to mount, the device is now only mounted to /home and /files.
My questions are:
Is this safe, or am I overlooking something?
Is it possible to get the same effect as umount /mnt/data using only fstab? Or could I do it in rc.local?
|
It's safe to unmount one of the bind-mounted copies. After you run mount --bind /foo /bar, the kernel doesn't keep track of which of /foo or /bar came first, they're two mount points for the same filesystem (or part of a filesystem).
Note that if /foo is a mount point but /foo/wibble isn't, mount --bind /foo/wibble /bar makes /bar point to a part of the filesystem that's mounted on /foo. It's still ok to unmount /foo.
So if you mount /mnt/data, then bind parts of it to /home and /files, and unmount /mnt/data, you end up with no access to the parts of /mnt/data outside arch and files. If that doesn't bother you, go for it.
You can't achieve that through fstab: it only supports mounting filesystems. Bind mounts get in through a hack (the bind mount option is turned into a --bind option to the mount command internally). mount --move and unmounting can't be specified in fstab. You can use /etc/rc.local to call umount.
| Umount device after bind mounting directories: is it safe? |
1,346,289,248,000 |
I am experimenting mounting options for a program I am writing. I am running Linux Mageia 2.
I added the following line to /etc/fstab
/dev/sr0 /mem auto user,noauto, 0 0
and I removed all other entries regarding /dev/sr0 which is the device for my DVD drive.
Then, acting as normal user, I can successfully
$ mount /dev/sr0
but I then get an error message ("Only root can ...") for
$ umount /dev/sr0
Of course, the device is not busy : I do nothing between mount and umount.
Added after solving : If you are interested only in solving that problem, you can skip the rest of the question, and go directly to the accepted answer.
The rest of the question is about my work to find a solution or better document the problem. However, there is a post-mortem section at the very end of the question that complements the answer with my own remarks.
Ownership of files :
$ ls -ld /mem /dev/sr0
brw-rw----+ 1 root cdrom 11, 0 mai 14 01:01 /dev/sr0
drwxr-xr-x 12 root root 4096 janv. 21 22:34 /mem/
And I am a member of the group "cdrom"
I have the very same problem when mounting a file system image with a loop device.
However, everything works fine when I replace "user" with the option "users", which seems to indicate that the system is confused when remembering who mounted the file system.
The first reply by Rahul Patil does not bring further insight since it is essentially equivalent to what I used, if my understanding of the umounting procedure is correct. However it lead me to think further about this process (hence one upvote) and to get more details. This was even more supported by the comment of Hauke Laging. As I understand it, summarily, the umount command takes its argument (a device or a mount point) and tries to identify applicable entries in /etc/mtab and then checks with /etc/fstab whether it can execute the request.
According to the man page for mount(8),the name of the mounting user [should be] written to mtab so that he can unmount the filesystem again.
When I check /etc/mtab after mounting, there is no such information written that I can find. I do not know how it is supposed to be stored and what it should look like.
Hence the probleme is really with mount rather than with umount.
To be absolutely sure that the problem is not that another /etc/fstab entry is used for mounting (which would explain ignorance of the "user"option),
I deleted all other entries in /etc/fstab, keeping only the single line at the beginning of my question. Then I repeated the mount-umount sequence, unfortunately with the same result.
$ grep sr0 /etc/mtab
/dev/sr0 /mem udf ro,nosuid,nodev,noexec,relatime,utf8 0 0
$ mount | grep sr0
/dev/sr0 on /mem type udf (ro,nosuid,nodev,noexec,relatime,utf8)
Hauke Laging asked for ls -l /etc/mtab, which I thought was an error and that he was really asking for cat /etc/mtab. But I did it anyway ...
$ ls -l /etc/mtab
lrwxrwxrwx 1 root root 12 juin 25 2012 /etc/mtab -> /proc/mounts
$ ls -l /proc/mounts
lrwxrwxrwx 1 root root 11 mai 19 13:21 /proc/mounts -> self/mounts
$ ls -l /proc/self/mounts
-r--r--r-- 1 myself mygroup 0 mai 19 13:22 /proc/self/mounts
This last information surprised me. Though I am essentially the only user on that computer, I see no reason why this file should belong to me, or to any other user than root itself. Many thanks Hauke, but why did you ask that question ?
Actually the file does not belong to me. I guess it must be a virtual file. I repeated the request as user "friend", and then as "root":
$ ls -l /proc/self/mounts
-r--r--r-- 1 friend users 0 mai 19 14:10 /proc/self/mounts
# ls -l /proc/self/mounts
-r--r--r-- 1 root root 0 mai 19 14:10 /proc/self/mounts
I would welcome any suggestion as to what the problem might be, or for experiments to attempt.
Thanks
Post-mortem: here are some final remarks after the problem was solved by Hauke Laging.
I followed on the web the lead of Hauke's explanation.
Apparently this is an old issue. It is explained in an old document from october 2000, mentionning some problems with other options, but not user.
Hopefully some of the kernel reliability issues are now corrected.
The issue is briefly mentionned in the bug section of the mount man page
but not in enough detail, especially regarding alternative setups and effect on options.
However, lost in that very long man page is the following information:
When the proc filesystem is mounted (say at /proc), the files
/etc/mtab and /proc/mounts have very similar contents. **The
former has somewhat more information, such as the mount options
used**, but is not necessarily up-to-date (cf. the -n option
below). It is possible to replace /etc/mtab by a symbolic link to
/proc/mounts, and especially when you have very large numbers of
mounts things will be much faster with that symlink, but **some
information is lost that way, and in particular using the "user"
option will fail**.
It would certainly have been useful to have a hint about this where the option user is described, which is the first place I looked.
|
The problem is that your /etc/mtab is not a file but a symlink to /proc/mounts. This has advantages but also the disadvantage that user does not work. You already guessed right the reason for that: "the system is confused when remembering who mounted the file system". This information is written to mtab, cannot be written there in your case though. The kernel doesn't care (doesn't even know) about user mounts (this is a userspace feature). Thus this info is not contained in /proc/mounts.
Do this:
cd /etc
cp mtab mtab.file
rm mtab
mv mtab.file mtab
umount as user should work after you have mounted the volume again.
| Option "user" work for mount, not for umount |
1,346,289,248,000 |
I'm using sshfs in my fstab to mount a filesystem in Ubuntu 18.04.04 LTS:
sshfs#[email protected]:/remote-dir /mnt/local-mnt fuse rw,exec,user,allow_other,noauto,reconnect,ServerAliveInterval=15,ServerAliveCountMax=3 0 0
It mounts fine, but if I try to execute anything in the path I get:
./some-executable: Permission denied.
The file has execute permissions (and works fine if I am actually ssh'd into the system).
If I use the fstab but include the -oexec option again:
mount /mnt/local-mnt -oexec
Then it works. Why is the fstab 'exec' being ignored?
|
The exec option is not being ignored - it's being overwritten by an implicit noexec associated with the subsequent user option. This behavior is alluded to in man mount:
user Allow an ordinary user to mount the filesystem. The name of the
mounting user is written to the mtab file (or to the private
libmount file in /run/mount on systems without a regular mtab)
so that this same user can unmount the filesystem again. This
option implies the options noexec, nosuid, and nodev (unless
overridden by subsequent options, as in the option line
user,exec,dev,suid).
You can get the desired behavior by specifying the exec option after the user option.
See also
Partition mounted noexec even though not specified in /etc/fstab
| 'exec' option ignored in fstab for sshfs, need to specify to 'mount' on command-line? |
1,346,289,248,000 |
While following this guide to installing Arch Linux the reader is instructed to execute the following command:
genfstab -U -p /mnt >> /mnt/etc/fstab
It is stated the the -U option uses UUID's over labels, but what does the -p option do? I have Googled it and can only find a page on fstab itself, not its generator. Arch includes no manpage on the subject... if anyone knows where docs on genfstab are, can they please provide a link? If not, can someone tell me what the options are or what the options do (primarily the -p switch)?
|
As stated in the "usage" section, -p will skip pseudo-FS mounts (tmpfs, AutoFS and others):
usage: genfstab [options] root
Options:
-L Use labels for source identifiers (shortcut for -t LABEL)
-p Avoid printing pseudofs mounts (default behavior)
-t TAG Use TAG for source identifiers
-U Use UUIDs for source identifiers (shortcut for -t UUID)
-h Print this help message
genfstab generates output suitable for addition to an fstab file based
on the devices mounted under the mountpoint specified by the given
root.
You can check the details in its source code: genfstab.in - arch-install-scripts.git | Official arch-install-scripts repository
| What does genfstab's -p option do? |
1,346,289,248,000 |
I got a new drive and I can copy files fine with simple cp on the drive. However for some weird reason I get Permission denied with ffmpeg.
Permissions seem fine unless I'm missing something
> ll /media/manos/6TB/
drwxrwxrwx 13 manos 4096 Apr 16 00:56 ./
drwxr-x---+ 6 manos 4096 Apr 16 00:49 ..
-rwxrwxrwx 1 manos 250900209 Apr 15 17:28 test.mp4*
..
But ffmpeg keeps complaing
> ffmpeg -i test.mp4 test.mov
ffmpeg version n4.1.4 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
configuration: --prefix= --prefix=/usr --disable-debug --disable-doc --disable-static --enable-avisynth --enable-cuda --enable-cuvid --enable-libdrm --enable-ffplay --enable-gnutls --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfontconfig --enable-libfreetype --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopus --enable-libpulse --enable-sdl2 --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libv4l2 --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxvid --enable-nonfree --enable-nvenc --enable-omx --enable-openal --enable-opencl --enable-runtime-cpudetect --enable-shared --enable-vaapi --enable-vdpau --enable-version3 --enable-xlib
libavutil 56. 22.100 / 56. 22.100
libavcodec 58. 35.100 / 58. 35.100
libavformat 58. 20.100 / 58. 20.100
libavdevice 58. 5.100 / 58. 5.100
libavfilter 7. 40.101 / 7. 40.101
libswscale 5. 3.100 / 5. 3.100
libswresample 3. 3.100 / 3. 3.100
libpostproc 55. 3.100 / 55. 3.100
test.mp4: Permission denied
Simply copying like below works fine..
> cp test.mp4 test.mp4.bak
'test.mp4' -> 'test.mp4.bak'
Any ideas on what is going on? This is pretty annoying. Note ffmpeg is installed at /snap/bin/ffmpeg
|
So after a lot of digging I figured the issue is with snap package manager. Apparently by default, snap can't access the media directory so we need to manually fix this.
Check if ffmpeg has access to removable-media like below
> snap connections | grep ffmpeg
desktop ffmpeg:desktop :desktop -
home ffmpeg:home :home -
network ffmpeg:network :network -
network-bind ffmpeg:network-bind :network-bind -
opengl ffmpeg:opengl :opengl -
optical-drive ffmpeg:optical-drive :optical-drive -
pulseaudio ffmpeg:pulseaudio :pulseaudio -
wayland ffmpeg:wayland :wayland -
x11 ffmpeg:x11 :x11 -
Add that permission if it's missing
sudo snap connect ffmpeg:removable-media
| "Permission denied" with ffmpeg (via snap) on external drive |
1,346,289,248,000 |
When I installed my SSD I just mounted with discard and didn't sweat it. However today I was reading about the pros and cons of using fstrim instead and decided to run the program to get an idea of how long it would actually take (still with my partitions mounted with discard). The command took several minutes on both my root and home partitions. For my home partition I used -v and got this:
$ sudo fstrim -v /home
/home: 137494052864 bytes were trimmed
This is more than the amount of free space on the partition!
$ df -h /home
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 206G 78G 118G 40% /home
Subsequent runs finish in less than a second, eg:
$ sudo fstrim -v /home
/home: 0 bytes were trimmed
Surely if I have always had the partition mounted with discard, fstrim should not trim a large amount of data like that? The discard option is definitely enabled, here are the relevant fstab lines:
UUID=xxxxxxxx... / ext4 noatime,discard,errors=remount-ro 0 1
UUID=xxxxxxxx... /home ext4 noatime,discard,errors=remount-ro 0 2
And mount output lines:
/dev/disk/by-uuid/xxxxxxxx... on / type ext4 (rw,noatime,discard,errors=remount-ro,stripe=128,data=ordered)
/dev/sda2 on /home type ext4 (rw,noatime,discard,errors=remount-ro,stripe=128,data=ordered)
The SSD is a TOSHIBA THNSNS256GMCP. Why does this happen?
|
Two things here:
fstrim trims all the data that is unallocated in the filesystem (well, not really all the data, only the data blocks that are not allocated, I don't think the unused parts of the inode table or the parts of not-completely used blocks are trimmed), regardless of whether discard is in used or not. fstrim cannot know which of those unallocated blocks have been "trimmed" or not already in the past, but it (actually the kernel, all the fstrim work is done in the FITRIM ioctl) does however keep track of which block group have been trimmed and will not trim them again if there hasn't been any unallocation in that block group since then, unless you're requesting a FITRIM with a smaller minimum extent length (from checking the ext4 code, it may be different for other file systems) which explains why you get 0 on the next run.
Note that it doesn't harm to trim a block that has already been trimmed. That's just telling the SSD again that it can do whatever it wants with it (like erase it so it can be ready to use again for something else).
In df output, the "available" value doesn't take into account the space that is "reserved" for root, you'll notice that 206 - 76 is 130G, not 118G. 12G (about 5%) are reserved. See tunefs -m to change how much is reserved.
| fstrim trims more than half of partition size even though partition mounted with discard |
1,346,289,248,000 |
I have a remote sshfs drive that I use on a daily basis. I previously executed the following command every time I booted up my computer.
sshfs -o Ciphers=arcfour -o Compression=no -o reconnect remote:dev ~/dev
Obviously, it's not super convenient to do that by hand every time, so I thought I'd just add the remote to my file systems table. I am unfamiliar with how fstab is formatted, but after a bit of reading on a few technical "how-to" blogs, I settled on including the following line in my /etc/fstab file.
sshfs#wbarlow@remote:/home/wbarlow/dev /home/wbarlow/dev fuse defaults,users,idmap=user 0 0
Unfortunately, if there is a blip in the network, the drive sometimes goes down. This happens maybe once per day -- and when I try to manually reconnect (by clicking on the drive in nautilus), I'm given a message that says "Transport endpoint is not connected.".
My primary question is this: how can I bring the -o reconnect option that I used in the terminal command into my fstab file? I believe that would prevent the drive disconnect due to blips.
Also, I chose that cipher because it's the quickest one my remote server supports (I think), and removed compression because the wired gigabit network is faster than the time taken by the CPU to compress stuff. It would be great if I could pull those options into my fstab as well, but I can live without them.
Here is my Kernel/OS/architecture info:
[wbarlow ~]$ uname -r
4.1.3-200.fc22.x86_64
|
To include the options you want, you should modify your fstab entry as shown below. Be careful, as adding an option that doesn't actually exist will cause your system not to boot.
sshfs#wbarlow@remote:/home/wbarlow/dev /home/wbarlow/dev fuse defaults,users,noauto,idmap=user,Ciphers=arcfour,Compression=no,reconnect 0 0
I tested it by
Inspecting the output of ps|grep ssh
Running kill ssh didn't kill the mount.
I took the liberty of adding the noauto option. This requests that the mount won't happen automatically, so that any failure will not stop the boot process (particularly when using systemd). It relies on you having a convenient way of running mount. Hopefully your filemanager will provide this, otherwise it defeats the point...
Another possibility is the nofail option. This option requests a successful boot even if this filesystem fails to mount "this device if it does not exist". Unfortunately we found sshfs/fuse has not implemented this option. Ironically, using the nofail option here will guarantee failure.
The docs (man fstab) describe the fourth field of an fstab entry:
The fourth field (fs_mntops)
This field describes the mount options associated with the filesystem.
It is formatted as a comma-separated list of options. It contains at least the type of mount (ro or rw), plus any additional options appropriate to the filesystem type (including performance-tuning options). For details, see mount(8) or swapon(8).
Basic filesystem-independent options are:
defaults use default options: rw, suid, dev, exec, auto, nouser, and async.
noauto do not mount when "mount -a" is given (e.g., at boot time).
user allow a user to mount.
owner allow device owner to mount.
comment or x-<name> for use by fstab-maintaining programs.
nofail do not report errors for this device if it does not exist.
Options which are completely filesystem-independent are handled by fstab. Other options are passed to the filesystem-specific command (in this case, sshfs).
| Force reconnect on sshfs drive mounted via fstab |
1,346,289,248,000 |
I have a mount command which with the use of -t cifs mounts a remote folder (for example \\remote_ip_address\folder) to a local folder (for example /srv/mount_destination).
So the whole command looks like this:
mount -t cifs -o ro,username=UN,password=PWD '\\remote_ip_address\folder' /srv/mount_destination
However I receive the following error:
mount: only root can use "--options" option
My problem is that this command has to be run by user, however user does not have and can not have sudo priveledges, so using the command with sudo is out of the question. Another road block is that the remote folder has to be mounted under a folder in /srv, thus using other folders like /media is not an option either.
I've tried to add the following line to /etc/fstab, restarted the system but without any positive effect:
//remote_ip_address/folder /srv/mount_destination cifs noauto,user 0 0
Is there something I did wrong or is there anything I'm still missing?
|
Given the line you’ve added to /etc/fstab, the following should work:
USER=UN mount /srv/mount_destination
(replacing UN with the appropriate value). This will use the file system, target and options specified in /etc/fstab, the username stored in the USER environment variable, and prompt for a password. If you want the ro option, you should add that to /etc/fstab too (noauto,user,ro).
The -o limitation (only root can specify it) is in place to protect the system: the administrator can set up whatever options are necessary, either directly using -o or using /etc/fstab; users can only cause user-controllable file systems to be mounted or unmounted, without specifying options, because file system options allow a number of hostile scenarios. As a result, some file systems support other ways of setting certain options, such as the USER environment variable used above with CIFS.
mount.cifs (which is used by mount -t cifs) supports a number of other settings which may be relevant. The multiuser option in particular can be very useful.
| Use "mount -o" with a non-root user |
1,346,289,248,000 |
I had swap from a swapfile working for quite some time, but for some reason it stopped working.
sudo fallocate -l 4G /home/.swap/swapfile
sudo chmod 600 /home/.swap/swapfile
sudo mkswap /home/.swap/swapfile
# /etc/fstab
/home/.swap/swapfile swap swap defaults 0 0
sudo swapon -a
swapon: /home/.swap/swapfile: swapon failed: Invalid argument
I'm running the newest version of Fedora, so is it maybe possible something has changed with an update or what could be the reason?
|
Please try replacing
fallocate -l 4G /home/.swap/swapfile
with
dd if=/dev/zero of=/home/.swap/swapfile bs=1M count=4096
| Swapfile Swapon invalid argument |
1,346,289,248,000 |
In mount man page errors=remount-ro is an option for mounting fat but this option doesn't appear in ext4 options catalog.
I know what this option means: In case of mistake remounting the partition like readonly but I don't know if it's a correct option or only a bug.
|
It is perfectly valid for ext4, and is defined in the ext4 manpage:
errors={continue|remount-ro|panic}
Define the behavior when an error is encountered. (Either
ignore errors and just mark the filesystem erroneous and
continue, or remount the filesystem read-only, or panic and
halt the system.) The default is set in the filesystem
superblock, and can be changed using tune2fs(8).
Some versions of the mount manpage do list this option for ext4; others refer to the manpage linked above:
Mount options for ext2, ext3 and ext4
See the options section of the ext2(5), ext3(5) or ext4(5) man page
(the e2fsprogs package must be installed).
| Why do I have "errors=remount-ro" option in my ext4 partition in my Linux? |
1,346,289,248,000 |
It's a simple question: but I am in much pain over this situation, so here is the question:
How can I "mount" a share so that a) the share is run on boot b) that I can control things like chown/chmod from the client.
# mount -t cifs -o username=root,password=******** //192.168.0.110/backup/ /var/backup/
# chown -R wwwroot:www /var/backup/
this second line will fail as a million "Permission Denied", is there anyway I can place the system settings such that a) this self same command in /etc/fstab/ auto-mounts and b) set things up so I can manage the share as if it were to behave exactly like a local volume
|
If you add the share to fstab you should be ok, but remember you need to have a network connection before you actually mount the drive. There "network" option is for that.
Now as to making it look "exactly" like a native partition, you can't. There are certain things that are not supported over a network drive. There are even more things that "may" be support, but depends on the hosts configuration.
You can get pretty close though.
Never mount things as root (across the network)
Change your configuration so that
mount -t cifs -o username=someuser,password=somepass //192.168.0.110/backup /var/backup
Then in /etc/fstab add
//192.168.0.110/backup /var/backup cifs username=someuser,password=somepass,network,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm
The dir_mode and file_mode force the local files to work like they have those permissions. You can also set other masking options and user options to allow others to access the folders. Keep in mind this removes a layer of security. If your trying to run backups you might want to try backups over SSH or NFS if possible. (NFS is like CIFS but much nicer for Linux to Linux shares, and SSH is supported by almost every backup tool out there).
| how do I mount a CIFS share so I can fully control the mounted volume on the client |
1,346,289,248,000 |
In Eric Hammond's article Running MySQL on Amazon EC2 with EBS he shows how to add a second drive (/vol/) and then progresses to move mysql's config and data there.
/sdh gets mounted as /vol by editing fstab and adding:
/dev/sdh /vol xfs noatime 0 0
And next some paths are added like this:
/vol/etc/mysql /etc/mysql none bind
I don't have a problem with doing this way but I don't quite understand what is going on.
I can most closely compare this to using a symlink, something like:
ln -s /etc/mysql /vol/etc/mysql
I've taken a look at man fstab without seeing much information about the bind syntax and can't find it in the fstab section in the Linux Administrator's Handbook either. Can someone shed some light on fstab's bind syntax, how it works, what it does, and where I should be able to find more information on it?
|
bind mirrors a filesystem (among other situatons, it's useful when setting a chroot inside which you need to have a "complete" system (like when unpacking/installing Gentoo).
Just simply like that, it mirrors a tree from A into B. I don't know for sure if it has any option, but I doubt it, it does not do more than, well, mirroring.
Unlike a symlink, which is a file in a filesystem pointing to another filesystem, requiring you to set it up, and is still a "special file", bind really mirrors the whole subtree. Depending on the tool, both strategies may work, but it is possible to detect the symlink and some tools may resolve it to the original path. The bind approach is more transparent, acting like two different filesystems.
| What is the difference between a symlink and binding with fstab? |
1,346,289,248,000 |
Inside the /etc/fstab file, in the sixth column, there is a number that corresponds to whether a filesystem should be scanned for errors. Possible values are:
0 - skip
1 - high priority
2 - low priority
Why was fsck 'priority' introduced in /etc/fstab?
|
The field exists so you can define the order in which filesystems are checked. Different partitions on the same drive should not be checked at the same time since the IO going to each filesystem will compete with one another, and slow the whole process down. Filesystems on different physical disks could be set to check in the same pass to speed up the whole process since the IO to separate disks would not be competing.
| Why was fsck priority introduced in /etc/fstab? |
1,346,289,248,000 |
I want to be able to mount our file server's file share (on a Mac OS X server, shared via AFP and Windows File Sharing) on my Ubuntu 10.10 linux laptop. I want to be able to mount it as my normal user, and be prompted for the password each time. What do I add to /etc/fstab to make this happen? I know I did it before, but I forgot how now.
EDIT: The share in question is called "G4 320", and I am trying the following line in fstab:
//server_ip/G4\040320 /media/G4/ cifs user,username=something 0 0
But I'm getting the following via dmesg:
CIFS VFS: cifs_mount failed w/return code = -6
EDIT2:
As requested, more debug info. Output of dmesg with my fstab line:
[151994.740138] CIFS VFS: cifs_mount failed w/return code = -6
[152007.760136] CIFS VFS: cifs_mount failed w/return code = -6
[152132.770147] CIFS VFS: cifs_mount failed w/return code = -6
[152221.700152] CIFS VFS: cifs_mount failed w/return code = -6
[152245.340132] CIFS VFS: cifs_mount failed w/return code = -6
Output of dmesg with the credentials line from Michael:
[153117.088656] CIFS VFS: No username specified
[153117.088668] CIFS VFS: cifs_mount failed w/return code = -22
[153164.358300] CIFS VFS: No username specified
[153164.358312] CIFS VFS: cifs_mount failed w/return code = -22
/var/log/messages seems to have no useful information.
EDIT3: OK. Thanks again to Michael I almost have it! If I put the following in /etc/fstab then it works:
//10.1.0.15/G4\040320H /media/G4 cifs user=AzureDiamond,password=hunter2 0 0
However:
I do not want my password in there...
I now need to use sudo to mount the share.
How can I resolve those two issues?
|
The line in /etc/fstab I eventually used was:
//10.1.0.15/G4\040320H /media/G4 cifs username=master,user 0 0
What solved the issue of not being prompted for the password as well as credentials= not working was installing mount.cifs via:
sudo apt-get install cifs-utils
Just like Michael Mrozek I assumed I had mount.cifs installed or else I wouldn't be able to mount CIFS shares, but apparently the kernel will use it's own internal code to mount unless it finds mount.cifs
| How do I add an entry in /etc/fstab for a windows share? |
1,346,289,248,000 |
In BuildRoot 2015.08.1 /etc/fstab contains the following line.
/dev/root / ext2 rw,noauto 0 1
On my encrypted Ubuntu laptop /etc/fstab contains the following line.
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
Question: What is the purpose of listing the rootfs in /etc/fstab?
Not the answer:
The kernel mounts the rootfs read-only from the root= parameter or in initramfs. So /etc/fstab does not help mounting the rootfs read-only.
The init process remounts the rootfs read-write. This is done in /etc/inittab in BuildRoot, and /etc/rcS.d/S06checkroot.sh in Ubuntu. So /etc/fstab does not help remounting the rootfs read-write.
Background: I am building an embedded system with a fancy initramfs. It looks for different rootfs candidates on the network and locally until it finds a suitable one. It takes care of checking the filesystem and remounting it read-write before calling switch_root.
Bonus question: What would be the impact of not listing the rootfs in /etc/fstab?
It would be awesome if there was none. I don't want to maintain a different /etc/fstab for each rootfs. But then why would BuildRoot and Ubuntu keep it?
Spoiler: I tried and it seems to work, but I am wary of hidden consequences.
|
The options in fstab are supposed to be used to remount it, applying the options specified ( which may NOT include rw access ). A boot script that is hard coded to remount the root fs with rw without consulting fstab is broken. Thus, the only result of leaving it out of fstab is that it won't be remounted, and will remain ro with no other options applied.
| What is the purpose of listing the rootfs in /etc/fstab? |
1,346,289,248,000 |
I have 2 XFS partitions I want to mount via /etc/fstab:
/dev/sdb1 /media/data xfs defaults 0 2
/dev/sdc1 /media/backup xfs defaults 0 2
Both are mounted at boot but when I try to access it as a non-root user, I get
$ cd /media/data
-bash: cd: /media/data: Permission denied
$ ls /media/data
ls: cannot access /media/data/audio: Permission denied
ls: cannot access /media/data/documents: Permission denied
ls: cannot access /media/data/downloads: Permission denied
ls: cannot access /media/data/images: Permission denied
ls: cannot access /media/data/video: Permission denied
audio documents downloads images video
Note that from the ls command there is a Permission denied error but the last line shows the directory names although they are in red font. I have tried doing sudo chmod 766 /media/data and sudo chmod 766 /media/backup but I still get permission errors when trying to access said mount points as a non-root user.
I am using Fedora 20 and I am not sure if this has something to do with SELinux but in my previous setup with a partition of NTFS, I don't get these errors and the partition was accessible by non-root users.
|
I have currently resolved this by:
Creating a new group and add my user to the new group
chgrp the mounts /media/data and /media/backup to created group
chmod 775 to both mounts
I can now access said mount points as my user and any user added to the new group I've created.
| How do I mount an XFS partition via /etc/fstab and non-root users can r/w to it? |
1,346,289,248,000 |
How this is possible?
ACL is not enabled in /etc/fstab, and I can verify it via manually opening fstab or running sudo mount | grep -i acl.
But getfacl & setfacl Commands would work without any complains!
The problem is, first I need to understand why this is working, and second I need to check other systems to see if ACL support is available on them or not, so how can I do that?
ACL commands were tested on both / & /mydrive(see below for mount output).
OS Info:
uname -a:
Linux localhost 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u1 x86_64 GNU/Linux
lsb_release -a:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.5 (wheezy)
Release: 7.5
Codename: wheezy
mount:
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=384309,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=308664k,mode=755)
/dev/disk/by-uuid/3180f94a-e765-44e9-93f7-33aa1c6422c0 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1188500k)
/dev/sda5 on /mydrive type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
|
ext3/4 file systems have a default mount options attribute in their headers. You can see it with:
$ LC_ALL=C tune2fs -l /dev/device | grep 'Default mount options:'
Default mount options: user_xattr acl
You can change it with tune2fs -o and mounting with -o noacl would override it.
When creating a new file system, mke2fs will set that based on what you specify in /etc/mke2fs.conf. For instance, mine has:
[defaults]
[...]
default_mntopts = acl,user_xattr
[...]
However, as noted by Gilles, since 2.6.39, acl and user_xattr are on by default (provided support has been enabled in the kernel at compile time which would generally be the default). So even without the acl default mount option, acls would be enabled by default on newer kernel, and the only way to disable it would be to use mount -o noacl.
To check whether ACLs are supported, best would be to try and query them:
$ chacl -l /the/mountpoint
chacl: cannot get access ACL on '/the/mountpoint': Operation not supported
| ACL is NOT enabled but it's working [duplicate] |
1,346,289,248,000 |
I mounted a FAT32 drive onto my Linux computer using the following terminal command:
> sudo mount /dev/sdb1 /media/exampleFolderName -o dmask=000, fmask=111
I did this so I could share / edit the files over a network connection. Unfortunately Linux doesn't support per file permissions in FAT32 format, so this sets the entire drive in the right permissions whilst it's connected.
If I understand mount correctly, I'll have to do this every time I plug the drive in, which I don't want to do. I've heard about:
/etc/fstab
So my question - how do I turn the above mount command into an fstab entry? If anyone could also explain what dmask and fmask mean, that would be appreciated.
|
You probably want to add a line like
/dev/sdb1 /media/drive1 vfat dmask=000,fmask=0111,user 0 0
to /etc/fstab. The additional ,user in the options field allows any user to mount this filesystem, not just root.
| Linux, fat32 and etc/fstab |
1,346,289,248,000 |
For /tmp in /etc/fstab, I have mode=1777, but after a reboot, the permissions on /tmp are 0755. Another directory /var/tmp is configured in exactly the same way but does not have this problem (see below). This is a Raspberry Pi running Ubuntu 18.04 Server. The root filesystem is a microSD card mounted read-only.
What is the proper way to make the 1777 permissions permanent?
Here are some additional details (after a fresh boot):
$ touch /tmp/test
touch: cannot touch '/tmp/test': Permission denied
$ whoami
ubuntu
$ ls -ld /tmp /var/tmp
drwxr-xr-x 9 root root 180 Dec 26 13:54 /tmp
drwxrwxrwt 4 root root 80 Dec 26 13:54 /var/tmp
$ mount |grep /tmp
tmpfs on /var/tmp type tmpfs (rw,nosuid,nodev,noexec,noatime,size=65536k)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,noatime,size=131072k)
$ grep /tmp /etc/fstab
tmpfs /var/tmp tmpfs defaults,noatime,nosuid,nodev,noexec,mode=1777,size=64M 0 0
tmpfs /tmp tmpfs defaults,noatime,nosuid,nodev,noexec,mode=1777,size=128M 0 0
$ sudo systemctl status tmp.mount
● tmp.mount - /tmp
Loaded: loaded (/etc/fstab; generated)
Active: active (mounted) since Sun 2018-01-28 15:58:18 UTC; 10 months 27 days ago
Where: /tmp
What: tmpfs
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 642 ExecMount=/bin/mount tmpfs /tmp -t tmpfs -o defaults,noatime,nosuid,nodev,noexec,mode=1777,size=128M (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 2146)
CGroup: /system.slice/tmp.mount
Jan 28 15:58:18 testsystem systemd[1]: Mounting /tmp...
Jan 28 15:58:18 testsystem systemd[1]: Mounted /tmp.
$ grep -R '/tmp' /etc/tmpfiles.d /usr/lib/tmpfiles.d
/usr/lib/tmpfiles.d/x11.conf:D! /tmp/.X11-unix 1777 root root 10d
/usr/lib/tmpfiles.d/x11.conf:D! /tmp/.ICE-unix 1777 root root 10d
/usr/lib/tmpfiles.d/x11.conf:D! /tmp/.XIM-unix 1777 root root 10d
/usr/lib/tmpfiles.d/x11.conf:D! /tmp/.font-unix 1777 root root 10d
/usr/lib/tmpfiles.d/x11.conf:D! /tmp/.Test-unix 1777 root root 10d
/usr/lib/tmpfiles.d/x11.conf:r! /tmp/.X[0-9]*-lock
/usr/lib/tmpfiles.d/tmp.conf:D /tmp 1777 root root -
/usr/lib/tmpfiles.d/tmp.conf:#q /var/tmp 1777 root root 30d
/usr/lib/tmpfiles.d/tmp.conf:x /tmp/systemd-private-%b-*
/usr/lib/tmpfiles.d/tmp.conf:X /tmp/systemd-private-%b-*/tmp
/usr/lib/tmpfiles.d/tmp.conf:x /var/tmp/systemd-private-%b-*
/usr/lib/tmpfiles.d/tmp.conf:X /var/tmp/systemd-private-%b-*/tmp
/usr/lib/tmpfiles.d/tmp.conf:R! /tmp/systemd-private-*
/usr/lib/tmpfiles.d/tmp.conf:R! /var/tmp/systemd-private-*
$ sudo chmod 1777 /tmp
$ ls -ld /tmp /var/tmp
drwxrwxrwt 9 root root 180 Dec 26 13:55 /tmp
drwxrwxrwt 4 root root 80 Dec 26 13:55 /var/tmp
$ cat /etc/rc.local
#!/bin/bash
service ntp start
exit 0
$ uname -a
Linux testsystem 4.15.0-1030-raspi2 #32-Ubuntu SMP PREEMPT Fri Dec 7 09:15:28 UTC 2018 armv7l armv7l armv7l GNU/Linux
Related, unanswered questions:
/tmp tmpfs permissions problem
How can I mount a tmpfs to /tmp via fstab, writable to anyone?
|
This was part of my initial configuration (because / is mounted read-only):
sudo rm -rf /var/spool && sudo ln -s /tmp /var/spool
Apparently at boot, the system does chmod 755 /var/spool, which changed /tmp in my case.
The fix was to replace the symlink with a normal directory and add a third tmpfs mount:
sudo rm -rf /var/spool && sudo mkdir /var/spool && sudo chmod 755 /var/spool
echo 'tmpfs /var/spool tmpfs defaults,noatime,nosuid,nodev,noexec,mode=0755,size=64M 0 0' |sudo tee -a /etc/fstab
Thanks to everyone for the comments which directed me in the correct direction, especially Filipe Brandenburger's "Do you have any other scripts or units messing with /tmp on startup?"
| Why is /tmp mounted with permissions 0755 when fstab has 1777? |
1,346,289,248,000 |
I have a partition, /dev/sdb1, that gets mounted at /data. In /etc/fstab I have:
/dev/sdb1 /data ext4 defaults 1 2
After that partition gets mounted, I then have the following bind mounts:
/data/backups/f17/opt /opt none rw,bind 0 0
/data/backups/f17/home /home none rw,bind 0 0
/data/var/www/html /var/www/html/ none rw,bind 0 0
All the mounting is done just fine.
The problem is that when I run df, the only entry I get relating to sdb1 points to "/opt", not "/data".
e.g.:
/dev/sdb1 240233144 196081648 31925236 86% /opt
I expect/want df to show the original mount point, that is /data, instead of /opt. Or at the very least, show all the mount points related to sdb1. If I umount the /opt bind mount point, then df happily shows /data (even though the other two bind mounts are still mounted, strangely).
There is no difference in behavior if I do the mounting commands in the terminal (vs letting the system do it via mount -a, which uses /etc/fstab).
I know I can use something like findmnt --df to get a better picture of all mounted filesystems, but I want to use df (and I don't want to alias df to anything else).
Fedora 21
kernel 3.19.3-200.fc21.x86_64
df (GNU coreutils) 8.22
mount from util-linux 2.25.2
thanks.
UPDATE
(adding more information)
The file /proc/mounts shows all four mount points:
/dev/sdb1 /data ext4 rw,relatime,data=ordered 0 0
/dev/sdb1 /var/www/html ext4 rw,relatime,data=ordered 0 0
/dev/sdb1 /home ext4 rw,relatime,data=ordered 0 0
/dev/sdb1 /opt ext4 rw,relatime,data=ordered 0 0
|
A bind mount is equivalent to the original. There isn't one that's marked as the original and one that's marked as a copy. Bind mounts are like hard links in this respect, not like symbolic links.
Since GNU coreutils 8.21 (if I read the changelog correctly), df strives to report each filesystem only once. Older versions included one entry per non-ignored mount point, so a bind mount would result in multiple entries. df shows the latest mount point for each filesystem, as far as it can determine. In your case, df reports /opt, not /data, because /opt was added last.
Pass the option -a to get even recent coreutils to report all entries for each filesystem. This also causes filesystems that would normally be ignored to be listed, if you don't pass a path argument. If you do pass a path argument, I think df never reports anything but the latest mount point.
If you don't want to alias df to something else, you'll either have to replace df by a custom implementation or have to live with df reporting something different from what you'd like. If you need the earliest mount point rather than the latest one, a sane solution would be to call df -a and retain only the first match for the device that you're interested in.
| bind mounting and df output |
1,346,289,248,000 |
I need to mount a ntfs partition and be able to use it with unix file system permissions. The problem is that, when I mount the partition using the following fstab entry, I cannot run chown and chmod successfully. It executes without error, but the file access rights are not changed.
PARTUUID=c3e3b171-d451-44e6-9f17-ffbe9e220dc7 /mnt/mounted_drive ntfs-3g defaults,umask=0022,uid=1000,gid=1000,errors=remount-ro,permissions 0 2
When I mount the partition without setting umask, uid, and gid I can use previously mentioned commands successfully.
PARTUUID=c3e3b171-d451-44e6-9f17-ffbe9e220dc7 /mnt/mounted_drive ntfs-3g defaults,errors=remount-ro,permissions 0 2
What shall I do to mount the partition properly?
|
With NTFS-3G, setting the owning user and group seems only to be possible when a UserMapping file containing a mapping for the targeted user/group is present. This is not really clear from the documentation, but I'm testing it just now and that is what is happening.
If compatibility with an existing Windows installation is not needed, create an empty file .NTFS-3G/UserMapping on the mounted partition and fill it via:
getRUI4() { od -An -N4 -tu4 /dev/random | tr -d ' '; }
USERMAPPING=/media/NTFS_PARTITION/.NTFS-3G/UserMapping
echo ":users:S-1-5-21-$(getRUI4)-$(getRUI4)-$(getRUI4)-513" | sudo tee -a $USERMAPPING >/dev/null
echo "$(id -un):$(id -gn):S-1-5-21-$(getRUI4)-$(getRUI4)-$(getRUI4)-1001" | sudo tee -a $USERMAPPING >/dev/null
If you want to use existing Windows SIDs, you can instead use the program ntfsusermap on an unmounted (!) partition, which will interactively ask you to specify user- and group-names (do not need to be numeric, regardless of the message) for given paths where it first finds an as of yet unmapped ID. This is quick to do.
User and group root is mapped by default, as is other. The above lines will create a mapping for users group, and the current user. Repeat as necessary.
Also, in my case, I mount the drive with the options
no_def_opts,allow_other,acl,nodev,nosuid,big_writes,hide_dot_files
However, in your case you should not need any of them, although I find that these options improve upon the default, as otherwise for instance chown/chmod fail silently in case of errors.
| Cannot chown, chmod on mounted ntfs partition |
1,346,289,248,000 |
We have a Redhat 7 machine. And the filesystem for device /dev/sdc is ext4.
When we perform:
mount -o rw,remount /grop/sdc
We get write protected error like:
/dev/sdc read-write, is write-protected
in spite the /etc/fstab allow read and write and all sub folder under /grop/sdc have full write/read permissions:
/dev/sdc /grop/sdc ext4 defaults,noatime 0 0
Then we do
umount -l /grop/sdc
and from df -h, we see that the disk is currently not mounted.
Then we perform
mount /grop/sdc
but we get busy. :-(
So we do not have a choice and we perform a reboot.
And from history we do not see that someone limited the disk for read only by mount.
This is very strange, how the disk device became write protected?
In order to solve this we perform a full reboot, and now the disk is write/read as it should be.
What happens here, after reboot we check the dmesg and we see the following:
EXT4-fs warning (device sdc): ext4_clear_journal_err:4698: Marking fs in need of filesystem check.
EXT4-fs (sdc): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (sdc): recovery complete
can we say that during boot - e2fsck was performed ?
dmesg | grep sdc
[sdc] Disabling DIF Type 2 protection
[sdc] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[sdc] 4096-byte physical blocks
[sdc] Write Protect is off
[sdc] Mode Sense: d7 00 10 08
[sdc] Write cache: disabled, read cache: enabled, supports DPO and FUA
sdc: unknown partition table
[sdc] Attached SCSI disk
EXT4-fs warning (device sdc): ext4_clear_journal_err:4697: Filesystem error
recorded from previous mount: IO failure
EXT4-fs warning (device sdc): ext4_clear_journal_err:4698: Marking fs in
need of filesystem check.
EXT4-fs (sdc): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (sdc): recovery complete
EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sdc): error count since last fsck: 5
EXT4-fs (sdc): initial error at time 1510277668: ext4_journal_check_start:56
EXT4-fs (sdc): last error at time 1510496990: ext4_put_super:791
|
It appears your filesystem has become corrupt somehow. Most filesystems switch to read-only mode once they encounter an error. Please perform the following commands in a terminal:
umount /dev/sdc
e2fsck /dev/sdc
mount /dev/sdc
If /dev/sdc is the harddisk which has your operating system on it, use a startup DVD or usb stick to boot from.
| How an ext4 disk became suddenly write protected in spite configuration is read/write? |
1,346,289,248,000 |
I'm messing around with having both /home and /var on a separate partition which will be mounted in /myhdd.
Next, I use mount --bind to mount /var on /myhdd/var and /home on /myhdd/home. With this configuration I am able to successfully install Arch Linux, but as soon as I boot to the installed system /var and /home are not mount although /myhdd is.
Due to this issue, I can't get pacman and more important stuff working. I do get a working system if I manually mount all directories, so it looks like an fstab problem, so here it is:
# /dev/sda1
UUID=f192b003-abf9-4e1a-87ee-d187d64423ce / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2
UUID=b4c5571f-ddb7-440e-b591-759e888b268d /myhdd ext4 rw,relatime,data=ordered 0 2
# /mnt/myhdd/home
/mnt/myhdd/home /home none bind 0 0
# /mnt/myhdd/var
/mnt/myhdd/var /var none bind 0 0
Any ideas why fstab doesn't mount my /var and /home directories?
|
Your problem:
/myhdd ... /mnt/myhdd/... /mnt/myhdd/...
It should read either:
/mnt/myhddd ... /mnt/myhdd/... /mnt/myhdd/...
or...
/myhdd ... /myhdd/... /myhdd/...
| bind mount /var with fstab |
1,346,289,248,000 |
I've been trying to set up my Raspberry Pi B+ as a HTPC that also shares a USB HDD over Samba and AFP. The latter is working just fine, and the Samba share seemed to be working too for a moment. However, whenever I try to connect to the Pi now (no modifications AFAIK) it shows me the folders with small stop icons. The following links unfortunately didn't offer me any help.
Mount exFAT file system as user without specifying /dev/sdX1 in /etc/fstab
Cannot mount exFAT even though I installed exfat-fuse
initialization
sudo mkdir /mnt/Data
sudo chown osmc:osmc /mnt/Data
sudo chmod -R 777 /mnt/Data
sudo apt-get install exfat-fuse exfat-utils
mount
/dev/sdb2 on /mnt/Backups type hfsplus (rw,nosuid,nodev,noexec,relatime,umask=22,uid=1000,gid=0,nls=utf8)
/dev/sdb1 on /media/EFI type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0111,dmask=0000,allow_utime=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,errors=remount-ro,uhelper=udisks)
/dev/sdb3 on /mnt/Data type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
cat /proc/filesystems | grep fuse
fuseblk
nodev fuse
nodev fusectl
blkid
/dev/sdb3: LABEL="Data" UUID="5563-32E4" TYPE="exfat" PARTLABEL="Data" PARTUUID="91a3c291-cfcf-4b17-ba57-538c29c3f951"
fdisk -l
Disk /dev/sdb: 2,7 TiB, 3000592977920 bytes, 732566645 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: C5BDA252-07EB-4C54-B1EF-35AC14D16381
Device Start End Sectors Size Type
/dev/sdb1 6 76805 76800 300M EFI System
/dev/sdb2 76806 244217437 244140632 931,3G Apple HFS/HFS+
/dev/sdb3 244250368 732566527 488316160 1,8T Microsoft basic data
cat /etc/fstab
/dev/mmcblk0p1 /boot vfat defaults,noatime 0 0
/dev/mmcblk0p2 / ext4 defaults,noatime 0 0
UUID=eae6464d-bd99-39f5-91a9-7d41b61356d4 /mnt/Backups hfsplus rw,force,exec,auto,users 0 3
UUID=5563-32E4 /mnt/Data exfat rw,force,exec,auto,user,umask=0 0 0
I've tried the following:
changing "exfat" in /etc/fstab to "fuse-exfat", "exfat-fuse", "fuseblk". All without luck.
manually mounting using:
sudo mount /dev/sdb3 /mnt/Data
sudo mount -t exfat /dev/sdb3 /mnt/Data
sudo mount -t exfat-fuse /dev/sdb3 /mnt/Data
sudo mount.exfat /dev/sdb3 /mnt/Data
sudo mount.exfat-fuse /dev/sdb3 /mnt/Data
/etc/samba/smb.conf
[global]
workgroup = HOME
server string = %h server
dns proxy = no
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
security = user
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
pam password change = yes
map to guest = bad user
usershare allow guests = no
[homes]
comment = OSMC
# browseable = no
path = /home/osmc/
valid users = @users, root, osmc ###this seemed necessary according to a guide
force group = users
create mask = 0777
directory mask = 0777
read only = no
The funny thing is, on every single one of these commands. The /mnt/Data privileges change to (drwxr-xr-x, root:root) and go back to normal when I unmount the volume. I'm guessing OS X won't let me browse into any directory as it is owned by root and I'm connecting as osmc. What seems to be going wrong here?
Regards,
Rowan Kaag
|
I noticed that by default, OSMC also shares external HDD's over Samba. On connecting to the Raspberry via Samba, I get the following options:
osmc
homes (not relevant in this case)
Data (ExFat partition on HDD)
When connecting to osmc, from my understanding, it serves me /home/osmc which has symlinked folders that I put there, e.g.: /home/osmc/Movies -> /mnt/Data/Movies
This results in the behaviour I mentioned before, giving me red warning circles on the folders. However when connecting directly to 'Data', everything works fine. I figured this would suit me and couldn't be bothered waiting for an answer here as I'm really impatient.
| Mounting ExFAT on Linux |
1,346,289,248,000 |
I want to use aufs to combine a few disks.I am able to mount the aufs file system using the mount command from the command line.
However, when trying to mount the same through an fstab entry, it fails. Google tells me that fstab does not mount file systems in the specified order, creating this problem. I also found recommendations to add the mount command in rc.local so the aufs is mounted after fstab.
I am using archlinux which uses systemd, so how can I run the mount command at boot in systemd?
|
Systemd has native support for mounts (man systemd.mount). In fact systemd reads /etc/fstab, uses it to generate mount units, and mount the filesystems itself.
Rather than relying on fstab, it's also possible to create mount units by hand. This is how system mounts like /dev, /sys, /proc, etc are handled (/usr/lib/systemd/system/*.mount). This method allows you to use systemd dependencies to ensure things get mounted in the right order.
systemd mount unit files must be named after the mount point they control (man systemd.unit). As an example, I created a unit file to mount my USB backup drive to /mnt/backup. Following the naming convention, I've created /etc/systemd/system/mnt-backup.mount, with the following contents:
[Unit]
Description = USB backup disk
[Mount]
What = LABEL=david-usb-backup
Where = /mnt/backup
Type = ext4
[Install]
WantedBy = multi-user.target
I then run systemctl daemon-reload for systemd to load the unit. I can run systemctl start mnt-backup.mount to mount the disk, and/or systemctl enable mnt-backup.mount to have it started at boot.
For dependencies add Requires = some-other-mnt-point.mount under the [Unit] section. Optionally, you may use BindTo rather than Requires; this will cause it to get unmounted if one of the dependencies disappears. However Requires does not affect the order in which the disks are mounted. So to make sure that the disks are mounted before aufs, use After.
Edit: To expand on the use of Requires and After, the unit section might look like:
[Unit]
Description = USB backup disk
Requires = mnt-data01.mount
Requires = mnt-data02.mount
Requires = mnt-data03.mount
After = mnt-data01.mount
After = mnt-data02.mount
After = mnt-data03.mount
| How to mount aufs file system on boot in archlinux? |
1,346,289,248,000 |
As I was checking the /etc/fstab I noticed that the swap space has attr pass=0, which means its filesystem is not checked at boot time.
Can anyone please tell me why is this behavior for?
|
At boot time, swap doesn’t contain any data which would need to be recovered, so there’s no point in writing a tool to repair swap. If a swap partition or file is corrupted in such a way that swapon can’t make use of it, the fix is to mkswap it again — there’s no need for a separate fsck.swap tool, so there isn’t one and /etc/fstab isn’t set up to use one.
It might then seem nice for swapon to automatically mkswap if necessary, but that would mean that any mistake in the arguments to swapon would be instantly fatal to the data stored in the given volume or file.
| Why swap space doesn't get filesystem check at boot time? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.