Ran into this one today, on a debian squeeze box:
/usr/sbin/grub-probe: error: no such disk.
It actually was telling the truth, the disks listed in /boot/grub/device.map were wrong. Replaced /dev/disk/by-id/serial-of-drive with /dev/sda. Worked.
Whilst researching this problem, I did run into a similar debian bug, but it wasn’t relevant. In case you’re interested, it’s about LVM drives, and it’s here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673573
Hi all, I was having trouble installing Mythubuntu 12.04 on an old PC I had lying around.
Mythubuntu is based on Ubuntu 12.04 so if you’re struggling with the ATI Radeon 9200 on there these steps should help.
(Since I have a Hauppuage Nova-T 500 dual freeview pci card from old projects, and a 2tb drive from new ones, I wanted to see about recording some films!)
Basically, when booting it would come up with a garbled, black or blank screen.
If this happens during the livecd boot, preventing you from installing, when you see the logo:
Logo that appears when first booting ubuntu from livecd.
Hit enter, and F6 for other options, select nomodeset, hit enter to enable then Escape and enter to boot.
If operating from a laptop, you might want to try noapic too.
In the latest grub setup – grub 2 – the boot menu is hidden, making it near impossible to access.
Might make it look pretty but is major frustrating for troubleshooting!
The script /boot/grub/grub.cfg it uses is supposed to boot in textmode if it has failed to boot, but this does not work.
The fix:
Note: you can login, type
sudo su
and then skip typing sudo with every command below (it gets quite annoying I know!)
sudo nmcli -p con up id “Wired connection 1”
If that doesn’t work check your wireless connections names with and edit the above command appropriately
nmcli con
sudo apt-get install xserver-xorg-video-ati
(don’t freak out when you see ‘Removing Mythubuntu-desktop’ it seems to come right in the end.
sudo ln /usr/bin/Xorg /usr/bin/X
sudo nano /etc/default/grub.cfg
Change this line near the top:
GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”
to
GRUB_CMDLINE_LINUX_DEFAULT=”nomodeset”
#”quiet splash”
The # tells it to ignore this bit, it’s a backup so that we can make it quiet again later. You’ll notice text streaming by as the system boots instead of the cute (Myth) Ubuntu …. logo
Ctrl-X to exit, type s and Return to save
sudo update-grub
sudo reboot
I actually ran this command to to start the windows manager, (and I haven’t tried rebooting yet, shhh)
sudo start lightdm
If you have any extra trouble, comment below, check the ubuntu forums and google.
I managed to work this out on my own as I couldn’t find the answer!
I also created a script to set the resolution of lightdm at boot, following the guide here:
LightDM Resolution
This did not work as when I started lightdm, the resolution was set higher than I’d set in lightdm, so I don’t think this was part of the fix.
Thankfully it was within my monitors capabilities. I think I set the output name wrong.
I need to figure out the display outputs are available but couldn’t query it from the command line without x running, which seems kinda silly.
Hope this has been helpful!
To make du not traverse partitons, just run it with the -x flag, or –one-file-system. Shiny.
(For the google meister, next time I search; du don’t follow partiton)
..
My friend Nick has also reminded me you can use the -x flag on cp as well, which is handy 🙂
As another aid to my memory, you can run mysql commands on the command line like this:
mysql -u user -p[password] database -e "SELECT * FROM orders;".
You can also send the mysql client commands on stdin:
echo "SELECT * FROM orders" | mysql -u user -p[password] database
Or read them in with a file redirection
mysql -u user -p[password] database < /home/kirrus/orders.sql
That last one is really handy for reading MySQL dumps back into MySQL.
I keep forgetting. To limit find’s recursion, use:
find . -maxdepth X
Where X is the recursion number. Maxdepth must be before any search selection stuff (type, name, mtime, perm etc).
This is the second half of that magento issue. Mainly, after having got a directory with millions of files in it, you can do one of two things.
mv sessions sessions_full && mkdir sessions && chown www-data:www-data sessions
rm -rfv sessions_full
Or
find /loc/of/sessions -ctime +1 -type f -exec rm -v {} \;
After an upgrade, I’ve noticed a few times that bind has refused to restart or reload, saying:
Stopping domain name service: namedrndc: connect failed: connection refused
This seems to be a permissions bug in debian, quite a long lasting one. In order to cheat-fix it quickly, I do the following:
chown bind:root /etc/bind/rndc.key
chmod 660
/etc/init.d/bind9 restart
That seems to fix it well enough. I think it’s a problem in that bind starts as one user, but runs as another. It may be that 440 are all the perms that are necessary. The debian bug report is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=169577
Magento (the popular open-source online shop system) likes to store its PHP session files in ~/public_html/var/session/
Most debian servers don’t have that in their cron job that deletes old session files.
So, you probably want to set it to store it’s session files in the default location (/var/lib/php5) or alter your cron job (/etc/cron.d/php5)
Fun!
So, ran into this one. Firefox is throwing this error, along with ‘SSL_ERROR_RX_RECORD_TOO_LONG’. Turns out, apache was serving plain HTTP on port 443, as it hadn’t been given a default SSL config.
Other causes may be: Corrupted SSL cert (rare). Mis-configured proxy. Not adding “SSLEngine On” after configuring an SSL cert. But mostly, you’re trying to talk HTTPS to an HTTP serving webserver.
`a2ensite default-ssl` (on debian) fixed it. Well, fixed in in that the default server now has a snake-oil self-signed cert, but, you know, fixed it. 🙂
If you get these errors:
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
or
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
Do this as root (or using sudo):
# apt-get install firmware-realtek
Win!
If you have other firmware issues, n1md4 suggested installing: firmware-linux and firmware-linux-nonfree in the comments (thanks!)