First attempt at install returned errors related to HDD. I wiped the drive using DBAN planning to replace the HDD. When attempting Ubuntu install after HDD wipe I received the following errors:  [ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata: plesae update microcode to version: 0x20 (or later) [ 0.32000] [mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae00000040110a [ 0.32000] [mce: [Hardware Error]: TSC 0 ABBR ffb07640 MISC 38a0000006 [ 0.32000] [mce: [Hardware Error]: PROCESSOR 0:40651 TIME 1537996692 SOCKET 0 APIC 0 microcode 17 0   Need to know if I have more than HDD issues here before replacing HDD
15710
I saw several bugs and error messages when I was looking by chance into the tool called "logs".  Being a newbie in Ubuntu I have no idea how to deal with these bugs, where to report them or how to fix them.  Any help to guide me here?  The bug I have (which is listed under important) reads:  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later)
69238
I’ve had a laptop fail (CPU failure according to the blinking LED) and was wondering what steps I could take to transfer its hard drive to a new machine and have it boot. It currently has Windows 10 installed (upgraded from Windows 8.1, Windows 8 before that, and originally Windows 7).  I’ll probably start by taking a backup image of the disk. The replacement laptop hasn’t arrived as yet, it’s of a similar vintage. The old machine was a HP ProBook (don't recall the model off the top of my head), and the replacement a Dell Latitude 6420.  I of course want to avoid having to reinstall and reconfigure all the applications on the drive.
93912
So I had been literally trying to fix my windows not being able to boot at all for more than 24 hours straight till now. I almost read every single article and troubleshooting step on the web to find a solution but nothing seems to work. I will keep it short as much as I can.  I did all of the following and it was:  "Reset this PC" gave an error "The required drive partition is missing"  "Refresh this PC" gave an error "The drive where windows is installed is locked. Please unlock and try again"  "System restore" gave an error something I don't actually remember but its like "Choose your OS and then try again"  "Automatic Repair" just failed to fix it and reverted me back to advanced options.   After all of that, I did  bootrec /fixboot bootrec /fixmbr bootrec /scanos bootrec /rebuildbcd bcdboot d:\windows (D is where I have the windows installed and C is for system reserved) bcdboot d:\windows /s c: /f ALL   All of these command prompt lines failed giving multiple errors like:  For REBUILDBCD, it said "Identified total windows installations: 1" then clicked "Y" to add it to the list and then it said "The requested system device cannot be found"  For bcdboot d:\windows it said Failure when attempting to copy boot files"   I wiped the disk multiple times using diskpart and installed fresh copies of windows on it 3 times but each time the installation will finish stage 1 (at a very slow pace) then when it restarts to continue installation, it simply won't boot (Windows logo and a spinning dot circle below forever)  I gave up and tried a totally new HDD and installed windows to it, it booted so normal and fast actually so I made sure it was not an issue with the windows.  Now I am booted from the new HDD and reformatted the old HDD and working on data recovery using easeus and it is finding my stuff luckily. It is also noticeable that the old HDD is making some noise while it is reading now as I scan for lost files.  My ultimate question is, will this HDD ever be able to used again? Even as a storage drive not as a drive I boot from? Because it is being seen through the bios boot menu and I see it in the disk management with healthy status. Can this HDD be fixed or I'm better off stop using it?  Here is a screenshot of the health status through SMART using HD Tune Pro:
8651
I have a desktop computer with Ubuntu Desktop 14.04.4 LTS 64-bit with an attached HDD USB 3.0 4TB Intenso 1 partition ext4 data drive only (no OS or Apps). After a sudden power failure, I am unable to mount the drive (checked different host Linux machines with no result).  error message:  sudo mount /dev/sdd1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdd1,        missing codepage or helper program, or other error        In some cases useful info is found in syslog - try        dmesg | tail  or so   Tried with fsck, e2fsck with no result. The error message says "Get a newer version of e2fsck".  Tried with all available superblocks backups with no result.  Tried offline file/drive Linux checkers on the offline and UNmounted volume with no result.  Finally, I received the following error message for which I couldn't find any help online:   "has unsupported feature(s): metadata_csum". e2fsck 1.42.9 (4-Feb-2014) /dev/sdd1 has unsupported feature(s): metadata_csum e2fsck: Get a newer version of e2fsck!   Can anyone help me take my data back?
29467
I'm new to Ubuntu, it looks like it is better than Windows. Last day I tried to install Kget (the download manager) but during the process my computer suddenly stopped working. So I had to switch it off. After I logged into Ubuntu again I can't install any program. The Ubuntu Software Center says:  Items cannot be installed or removed until package catalog is repaired. Do you want to repair it now?   After I clicked repair it says (after few seconds):  Package operation fails - The installation or removal of a software package failed   I've tried several times, but the same problem occurred. Can anyone tell me a solution for this problem?
34741
I have a HP Compaq nx6310 notebook wth 4gb memory &amp; a new 250gb hdd. After installing Ubuntu 12.04, i got an "out of disk" error &amp; was unable to boot. I rebooted in live, instaled &amp; ran Boot Repair then rebooted. Grub menu loaded fine, followed by "out of disk.....press any key to continue". I pressed a key &amp; Ubuntu booted, a bit slow but still booted. So here are my questions: 1- Since Ubuntu DOES boot, should I just leave it alone? 2- If I need to fix this, HOW do I do it? 3- What causes this error?  $wolf@lpc-1:~$ df -h Filesystem      Size  Used Avail Use% Mounted on /dev/sda1       230G  9.1G  209G   5% / udev            1.6G   12K  1.6G   1% /dev tmpfs           655M  868K  654M   1% /run none            5.0M     0  5.0M   0% /run/lock none            1.6G  260K  1.6G   1% /run/shm wolf@lpc-1:~$
79993
kernel: EDAC MC0: UE page 0x0, offset 0x0, grain 0, row 7, labels ":": i3200 UE  All of a sudden today, our CentOS release 6.4 (Final) system started throwing EDAC errors. I rebooted, and the errors stopped.  I have been searching for answers, but they fall into two camps, memory or a chipset. I would like some advice on where to search further to narrow this down to chipset or memory.
33825
I have DELL Precision, with 512GB SSD. I did shrink the only Drive C,  and made 125 GB of unallocated space to install Ubuntu on it.  restarting the system choosing boot, install Ubuntu, the installation process does not recognize any hard disk except the Flash memory that contains ubuntu bootable.  the information from Windows 10 side:  Dell Precision 3520 windows 10 pro Intel Core i7-7820HQ BIOS mode UEFI from the device manager; Storage Controllers:         Intel chipset SATA/PCIe RST premium controller         microsoft spaces storage controller         microsoft VHD loopback controller Disk 0: (Basic)        SSDPEKK NVMe INTEL 512GB               Partition Style GPT Rapid Storage Technology:        Controller 1, Port 0        Port Location Internal        Type PCIe solid-state drive        System Disk: yes        Controller Type: NVMe BIOS options on power up:         System Configuration/SATA Operation = RAID on (Intel RST)   I've read that the Ubuntu kernel is compatible with RST and should recognize the SSD, Also the Disk 0 is shown as basic which I think means hardware RAID.  What should do in this case to have a dual boot installation of Ubuntu
9112
I have just set up my new system by creating three partitions on a whole hard disk (/boot, /home, swap and /). I saw  article and now I am getting those errors and the system provide me with some options: (I to ignore, S to skip mounting or M for manual recovery).   I am forced to choose skip mounting because I don't know what manual recovery is. Despite the error I get I think that the system boots okay because I can use the system but this error is very annoying.
51400
I was trying to setup a Microserver with two 1TB harddrives as a software RAID. Somehow it didnt work and now ubuntu 14.04 is not starting. My problem is that I dont see the drives anymore when I go through the installation process again!  On boot I can see, that there are two working drives inserted, but I cant see them while being in the "partitioning menu" during the Ubuntu server installation.   There is no data on those drives, so I am looking for some way to erase them completely, so they show up again. From the installation I could switch to an Almequist (ash) shell.  How can I get my drives back?  Thanks!
74265
This is what happened:  I was running 12.04.1 and wanted to install 12.10. upgrade, but a fresh install.  When setting up my computer I anticipated for this by dividing my 640GB HD in following partitions: 1. 60 GB for Ubuntu, boot 2. 576 GB for data, mountpoint /home 3. swap, 4GB  The idea was to manually select the correct partition in the installer but I got distracted for a moment and selected the wrong option.  Result: The installer started repartitioning the entire HD.  When I noticed this I interrupted the installer, but upon reboot it was clear that I was too late, no OS to boot to.  I booted from a Gparted Live CD to see if I could recover the data on my previous /home-partition, but it's gone.  Is there any way to recover the lost data? I searched around and read alot about Testdisk, but in all the tutorials I've seen, the set-up has been much easier than what I'm facing.  I've not only lost my partition table, it's been replaced.  Thanks in advance for any ideas that might help!  If extra info is needed, please specify and I will do my best to provide.
2113
So, let's say your server had 6 healthy hard drives.  A drive fails (will not mount/detect, drops out of raid with errors) or is failing (SMART getting worse, etc).  You need to swap out the bad drive.  When you open the case you see.. six identical hard drives.  How can you tell which one is no longer healthy/mounting/functioning?  System would be linux, most likely ubuntu server, using at most simple software RAID.  The hard drives would be SATA and connected directly to the motherboard. (no raid controller)   I don't want to randomly disconnect drives until I pick the correct one.  The drives all appear identical to me; I imagine there is some common way to identify which drive is which that I am unaware of.  Does anyone have any pointers/tips/best practices?  Thanks!  EDIT: I had wanted this to be 'generalized' in a hand-wavy sort of way, but it just came off as 'incomplete' and 'horrible'.  My bad!
34562
Last night I was updating my Ubuntu 10.04 to either 11.04 or 12.04 (I'm not entirely sure which one it was, but I think it was 11.04) and I left it overnight to finish. When I came down in the morning, I noticed that the computer hadn't barely begun installing the updates! The update thing said that my computer was on the installation step, but it was still preparing the libc bin (or whatever its called) . It's like the first part of the step installing the upgrades. So, I stupidly restarted the computer, and when it rebooted, I got five options on a purple screen:  Ubuntu, with Linux 3.0.0-28-generic Ubuntu, with Linux 3.0.0-28-generic (recovery mode) Previous Linux versions Memory test (memtest86+) Memory test (memtest86+, serial console 115200)   Long story short, not matter which way I enter Ubuntu to try and reinstall the updates using the root thing (it's like terminal) after I enter sudo apt-get update it basically said it failed to fetch every url link, and it then says:  W: Some index files have failed to download. They have been ignored, or old ones used instead. W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.   So, I entered sudo dpkg --configure -a, and it says:  dpkg: error: unable to access dpkg status area: Read-only file system"   I'm left like wtf, and I really just some guidance here. I just got this laptop, and I can not afford a new one if I broke this one.
87604
I used a live USB to install Ubuntu 14.04 and completely erase windows 8.1, the installation went fine but when I restarted the computer Ubuntu wouldn't boot from my HDD, instead it came up with try Ubuntu or install Ubuntu so I restarted without the live usb plugged in and I got an error message Reboot and select a proper boot device or insert boot media in selected boot device and press any key.  I read a lot of posts about people that had similar problems but so far none of the solutions that worked for them have worked for me.  I also ran boot-repair but that didn't fix the problem either.   Here is the link from boot-repair   Please any help would be appreciated.  My laptop is a Toshiba Satellite U50D-A notebook with AMD A6-5200 processor
91304
What steps should be taken before/during/after installation of Ubuntu on a Solid State Drive to optimize performance and ensure maximum durability of the drive?
2519
I get this error message   NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [plymouthd:305]    on the startup of my system (even with live-cd).  My PC is a dell inspiron 7559 with intel graphic and nvidia.  UPDATE - this issue also happens when attempting to install ubuntu 18.10 using LiveUSB
2874
I received a new HDD from my uncle, RAW file system. Tried CHKDSK, but it didn't work because of the RAW file system.      Update  I ran SpinRite 6 overnight and it got nowhere. Stayed at 0% for the whole 10 hours. SpinRite also gave me a notification that this drive is most probably toast. I think I am going to throw this drive away.