 |
and possible remedies/causes.
Here is a list of known error messages (numbers) and their meaning. This list is by no means absolute, and if additional causes and/or remedies are found, please e-mail the webmaster.
| Error Code | Meaning | Cause and remedy |
| 21 | Error running script. | (This should NEVER happen) |
| 150 | The folder "/dev" does not exist. | There are a couple of instances when this could happen. One instance involve trying to mount a drive or device that isn't fully supported in Linspire. Sometimes this error is followed by a lockup. Turn the computer off, remove the offending device and restart. |
| 151 | devfsd is not running. | |
| 152 | Could not initialize partition. |
This usually happens during installation but could happen when adding a new storage device. If it happens during installation, there are 3 common causes - not the least of which are a bad hard drive or too small a hard drive. Usually, however, the cause is simply the inability to overwrite the existing partition. A low-level format utility from the hard drive manufacturer will solve this problem. |
| 153 | Could not initialize partition. | This usually happens during installation but could happen when adding a new storage device. If it happens during installation, there are 3 common causes - not the least of which are a bad hard drive or too small a hard drive. Usually, however, the cause is simply the inability to overwrite the existing partition. A low-level format utility from the hard drive manufacturer will solve this problem. |
| 154 | Could not create partition. | This usually happens during installation but could happen when adding a new storage device. If it happens during installation, there are 5 common causes - not the least of which are a bad hard drive or too small a hard drive. Usually, however, the cause is simply the inability to overwrite the existing partition. A low-level format utility from the hard drive manufacturer will solve this problem. The 4th cause could actually be a bad memory stick or even another malfunctioning drive causing what can only be described as "interference". |
| 155 | Could not mount partition. | Almost always a bad drive but could also be a bad memory stick. |
| 156 | Could not unmount partition. | When this happens, you are trying to remove an external device but it is still busy. Close the programs using the device (including Konqueror) and try unmounting the device. |
| 157 | Could not format partition. | In most cases, a bad drive. |
| 158 | Could not format swap device. | In most cases, a bad drive. |
| 159 | Could not create swap file. | In most cases, a bad drive. |
| 160 | Could not mount swap device. | In most cases, a bad drive. |
| 161 | Could not unmount swap device. | In most cases, a bad drive. |
| 162 | Could not create directory. | On a drive, check to see if write protection is enabled. Over a network, be sure you have write permission for the location you are writing to. Failing those, restart and try again. |
| 163 | Could not find a swap partition. | In most cases, a bad drive. |
| 164 | Error running "etcdev". | |
| 165 | Directory does not exist / is not a directory and could not be created. | SEE ALSO 162. Press F5 to refresh the list. Otherwise, the directory is temporary and really does not exist. |
| 166 | Could not install master boot record. | In most cases, a bad drive or filesystem. Low-level format and try again. |
| 167 | Could not read hostname from Linspire partition. | In most cases, corrupt data or a bad drive. Try a low-level format utility. |
| 200 | rsync failed. | This is the most puzzling installation error but is almost always a hardware failure. The causes could be as follows: bad installation CD, bad CD-ROM, bad memory, bad hard drive, bad capacitors on mainboard, or hot processor. Troubleshoot the problems in this order and you will quickly isolate the problem. |
| 201 | rm failed. | Not the same error as #200 but troubleshoots the same. |
| 202 | Error purging debs. | |
| 203 | Error copying. | During installation this is almost always a memory, harddrive, CD-ROM, or installation CD problem. |
| 204 | Error while untaring. See the log for more information. | Usually memory, media, or file error. |
| 205 | Detector reset command failed. | |
| 206 | Detector install failed. | |
| 207 | Could name make initial ramdisk. | In most cases, a bad memory stick. |
| 208 | Error running fooze. | |
| 209 | Could not create XFree86 config. | In most cases, a bad drive. |
| 210 | Could not convert to shadow passwords | |
| 211 | Could not move file. | SEE ALSO 162. |
| 212 | Could not fix pam file. | |
| 213 | Could not run system-setup. | Bad image or bad CD. |
| 214 | Could not clear password. | Could be a problem with the user account, or, more likely, you don't have permissions to alter user passwords. |
| 215 | Could not change directory. | In most cases, a bad drive. SEE ALSO 162. |
| 216 | Could not mount. | Cannot see the drive/partition. Sometimes a bad drive or corrupt partition. |
| 217 | Could not unmount. | SEE ALSO 156. When this happens, you are trying to remove an external device but it is still busy. Close the programs using the device (including Konqueror) and try unmounting the device. |
| 218 | Could not write file. | In most cases, a bad drive. |
| 219 | Error running jiffyboot. | |
| 220 | Error running boot record configurator. | Bad image or bad CD. |
| 221 | Could not set password. |
Could be a problem with the user account, or, more likely, you don't have permissions to alter user passwords. |
| 222 | Could not create dir | SEE ALSO 162. On a drive, check to see if write protection is enabled. Over a network, be sure you have write permission for the location you are writing to. Failing those, restart and try again. |
| 223 | Could not find /iso, malformed installer CD. | Bad image or bad CD. |
| 224 | Error while streaming disk image. | Bad image, bad CD, bad CD drive, blown capacitors, bad hard drive, magnetic echoes (that is: old drive data that doesn't get fully erased coming back and corrupting new data laid over top of it.) |
| 225 | Could not create loopback device. | |
| 500 | Could not allocate memory. | Out of memory or bad memory. |
| 501 | Could not load configuration. | Bad image or bad CD. After install, if a similar error occurs, it is usually a bad drive or corrupt drive data. |
| 502 | Some settings are missing or incorrect. | When running a program in Linspire, this message could appear if depenancy files are missing or corrupt. |
| 503 | Could not run disk setup script. | Bad image or bad CD. |
| 504 | Could not run install script. | Bad image or bad CD. |
| 505 | Could not configure system. | Bad image, bad CD, bad CD drive, blown capacitors, bad hard drive, magnetic echoes (that is: old drive data that doesn't get fully erased coming back and corrupting new data laid over top of it.) |
| 506 | Installer timeout | Try install again and check for hardware damage. |