2,187
edits
Difference between revisions of "Troubleshooting (Ubuntu)"
Jump to navigation
Jump to search
Added "Unable to Mount CD-ROM"
(Initial creation - content from Ubuntu page) |
(Added "Unable to Mount CD-ROM") |
||
| Line 1: | Line 1: | ||
= Network = | == Network == | ||
== No NIC == | === No NIC === | ||
Especially after hardware changes, its possible the networking config no longer refers to the right interface. | Especially after hardware changes, its possible the networking config no longer refers to the right interface. | ||
| Line 7: | Line 7: | ||
# Assuming it states that say <code>eth0</code> has been changed to <code>eth1</code> then just update the <code>/etc/network/interfaces</code> file | # Assuming it states that say <code>eth0</code> has been changed to <code>eth1</code> then just update the <code>/etc/network/interfaces</code> file | ||
= | == File System == | ||
== Replacing a RAID 1 Disk == | === Unable to Mount CD-ROM === | ||
Mounting drive with following command fails | |||
* <code> mount /dev/cdrom /media/cdrom/ </code> | |||
If <code>/media/cdrom/</code> doesn't exist | |||
# Create the file with <code>mkdir /media/cdrom</code> | |||
If <code>/dev/cdrom</code> special device doesn't exist | |||
# Check for existing mappings and devices | |||
#* <code>ls -l /dev/ | grep cdrom</code> | |||
# If an existing mapping exists but for a different drive number (eg <code>cdrom2 -> sr0</code>) | |||
#* Then try mounting with that number | |||
#* EG <code> mount /dev/cdrom2 /media/cdrom/ </code> | |||
# If no existing mapping exists | |||
#* Then try creating one for one of the listed devices | |||
#* EG <code> ln -sf /dev/sg0 /dev/cdrom </code> | |||
=== Replacing a Software RAID 1 Disk === | |||
This procedure was written from the following starting point... | This procedure was written from the following starting point... | ||
* A machine originally with two disks in RAID1 has failed, one disk has been replaced, and machine started again | * A machine originally with two disks in RAID1 has failed, one disk has been replaced, and machine started again | ||
| Line 26: | Line 42: | ||
#* <code> more /proc/mdstat </code> | #* <code> more /proc/mdstat </code> | ||
= SSH = | == SSH == | ||
== Server Hostname Change == | === Server Hostname Change === | ||
If the hostname (or IP) of the server you are SSH'ing to changes, the old entry needs to be removed from your SSH key known hosts file | If the hostname (or IP) of the server you are SSH'ing to changes, the old entry needs to be removed from your SSH key known hosts file | ||
* <code> ssh-keygen -R <name or IP> </code> | * <code> ssh-keygen -R <name or IP> </code> | ||
= Packages = | == Packages == | ||
Errors etc received from <code>apt-get</code> | Errors etc received from <code>apt-get</code> | ||
* '''Error 400 Bad Request''' | * '''Error 400 Bad Request''' | ||
| Line 38: | Line 54: | ||
** Package manager can hold back updates because they will cause conflicts, or sometimes because they're major kernel updates. Running <code>aptitude safe-upgrade</code> normally seems to force kernel updates through. | ** Package manager can hold back updates because they will cause conflicts, or sometimes because they're major kernel updates. Running <code>aptitude safe-upgrade</code> normally seems to force kernel updates through. | ||
= Reboot Required? = | == Reboot Required? == | ||
If a package update/installation requires a reboot to complete the following file will exist... | If a package update/installation requires a reboot to complete the following file will exist... | ||
/var/run/reboot-required | /var/run/reboot-required | ||