[Solved] Can't boot, root device not found

I recently performed an update of udev and my kernel and after this I am unable to boot the normal kernel or the fallback. When I try I get this error:
ERROR: Unable to find root device '/dev/disk/by-uid/03619a2f-908f-4724-ba4b-1fb3985e382b' You are being dropped to a recovery shell Type 'exit' to try and continue booting sh: can't access tty; job control turned off
Typing exit results in me dropping to another shell and if done repeatedly a kernel panic. I attempted to boot via the grub console using the sda device block but I came up with the same error. When I look in /dev through the recovery console that comes up the sda* blocks aren't present.
I need to know if there is a way to do this without entirely reformatting my system, I also don't have easy access to another computer but I have an android phone. Any assistance is greatly appreciated.
Last edited by Surry (2012-03-20 00:06:12)

This has been solved.
For anybody's reference:
From the recovery shell I had to load the modules ahci and sd_mod and that got the sda* to appear in /dev. After that I had to mount /dev/sda3 (my root partition) under /root and /new_root and then enter 'exit' to continue booting.
Pretty much:
modprobe ahci
modprobe sd_mod
mount /dev/sda3 /root
mount /dev/sda3 /new_root
exit

Similar Messages

[SOLVED] Can't boot computer (device not found)

On boot (both Normal and Fallback) I get:
Waiting 10 seconds for device /dev/disk/by-uuid/d3c4f22d-65c6-4e06-bcc1-752db552061
ERROR: device '/dev/disk/by-uuid/d3c4f22d-65c6-4e06-bcc1-752db552061' not found
Skipping fsck
And then it drops to a shell, and I need to use "exit" to run, but it requires me to choose a boot partition (I tried exit /dev/sda1 and others but it says invalid number).
I know there are many posts on that, but since I believe this is a specific issue (I updated kernel last night with -Syyu'd), I decided to make my own.
Any ideas? Thank you in advance.
Last edited by ephan (2012-06-01 18:46:28)

edit: I'm way too slow
ephan wrote:
# mkdir /mnt/arch
# mount /dev/sdaX /mnt/arch (your root partition)
# cd /mnt/arch
# mount -t proc proc proc/
# mount -t sysfs sys sys/
# mount -o bind /dev dev/
# mount /dev/sdaX boot/ (your /boot partition) #This step is not needed if you do not have a separate boot partition
# chroot .
# pacman -Syu udev mkinitcpio
# mkinitcpio -p linux
About that, I have some questions...
1. How long can it take?
2. How dangerous is it?
3. Is it really what I need?
4. Can I lose files? Since I can't boot, is there a way to save them?
5. In order to find out what my root partition is, can I use Gparted?
5.1. Can I not use an Arch Live CD and use Ubuntu for example? It's much easier to do it.
6. How do I know if I have a separate boot partition? I have all /dev/sda's, and one of them is boot I think. Don't we all have?
Sorry and thank you!
Also, and I want to make this clear, I did *not* use force on pacman, I never do.
So, what caused?
I just updated it normally, like I always do, was it some arch error everybody else experienced?
1) The time to boot the live cd, type the commands and like 30 seconds for mkinitcpio.
2) lol, not dangerous
3) Since it's in the Q&A: most probably.
4) You can always lose files. Just boot a live cd, mount the partitions you want to save and the partition you want to save it to and copy (or rsync).
5) I don't think so, unless you gave your partitions a descriptive label. Just mount partitions until you find the root.
5.1) I don't think so.
6) If you find your root partition: if /boot is empty, you have a separate boot partition. You can check your fstab to see which one.
What caused? dunno
Was it something everybody experienced: no
Good luck! Just follow the instructions, it's not that hard.
Last edited by Terminator (2012-05-29 21:47:43)

[Solved] - Root device not found - Unable to boot!

Before posting links to other threads or to the pacman/mkinitcpio wiki page please go through the following.
I know that many others are facing a similar problem, but I am posting this after spending 8+ hours (in 2 days) trying to get my system to boot.
And worst of all I don't have a working CDROM so I have to boot via an iso on a pendrive which is very frustating.
The exact message I get after the GRUB menu is:
ERROR: resume: hibernation device '/dev/sda3' not found
ERROR: Unable to find root device '/dev/disk/by-uuid/...'
You are being dropped to a recovery shell.
Type exit to try and continue booting
Now I have already tried the following, by chrooting into my system:
1. As per the pacman wiki page, boot via live arch, chroot and run full upgrade. Then reinstall udev followed by mkinitcpio and then remake the image.
2. Downgrading to linux-3.3.4-2, udev-182-2x86-64 and mkinitcpio-0.8.8-1
3. Rearranging hooks in mkinitcpio.conf (usbinput before udev), and adding ext4 to MODULES array. Done this in both downgraded version and new kernel version (3.3.8-1)
After trying various permutations and combinations, I have failed and haven't been able to get past the first 8 lines after the grub menu.
An important point to note:
I had used the --force switch for 1 more package other than filesystem while updating which I don't remember now. I had to use it because some packages had gotten corrupted while downloading and I had to upgrade in parts. Also at no point during any of these trials did I get an error while rebuilding the initrd image.
If I remove the resume hook in /etc/mkinitcpio.conf then the first line "ERROR: ... " changes saying that "no hibernation device specified".
Please suggest anything if you can!
Last edited by theta (2012-06-15 15:44:15)

ewaller wrote:
Do you know the partition that is supposed to be your root partition?
Grub cannot find it by its UUID. Reboot, at the grub menu, highlight the kernel you want to boot, and press 'e'. You are dropped into a simple editor which will allow you to change the boot command. Replace references to /dev/disk/by-uuid/... with /dev/sdan, when n is the root partition number.
One other possibility. Does your system have multiple drives? Any chance the BIOS could be swapping them ? (On second thought, that would not break UUID, But... it is something to be aware of using the technique I proposed)
If you do not know the partition arrangement, use that limited recover shell you mentioned to go look around and determine it.
Hmm, Thanks for this advice but I can't help saying that I'm not a noob .
Somehow the problem resolved itself with the new kernel update which came about half an hour ago (3.4.2-2). Suppose it will remain a mystery now!

[Solved] kernel 2.6.27 - Root device not found (2.6.28 too)

since the last kernel update, my ArchLinux won't boot anymore, as it seems to be unable to find the root partition "/dev/sda5". The exact output is:
:: Loading root filesystem module...
Attempting to create root device '/dev/sda5'
ERROR: Failed to parse block device name for '/dev/sda5'
unknown
ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
Waiting for devices to settle...done.
Root device '/dev/sda5' doesn't exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/sda5'
ERROR: Unable to create/detect root device '/dev/sda5'
Dropping to a recovery shell... type 'exit' to reboot
NOTE: klibc contains no 'ls' binary, use 'echo *' instead
If the device '/dev/sda5' gets created while you are here,
try adding 'rootdelay=8' or higher to the kernel command-line
ramfs$
What I have tried:
1.- I have booted with an old Ubuntu LiveCD, and /dev/sda5 seems to be working and healthy, as it mounted flawlessly while in Ubuntu.
2.- I have also found that not even /dev/sda is created from the fallback recovery shell so, obviously, there is no root device to create.
3.- None of the suggested kernel command-line parameters worked: 'rootfstype=ext3' and/or 'rootdelay=8'(I mean, using them separately or both in the same kernel GRUB line) didn't give any positive result, or any behavior change.
And now, two questions:
1.- How can I fix this?
2.- If it's not possible, how can I downgrade the kernel from a LiveCD? I suppose this is possible by booting an ArchLinux LiveCD, chrooting my '/dev/sda5' finding a 2.26.X kernel pacman package and installing, but I'm almost iliterate in kernel issues, and some help would be nice.
Thank you all in advance!
EDIT: Oh, I have also waited for some time to see if the hard disk gets ready after the failed booting proccess but it seems it doesn't, so 'rootdelay=8' wouldn't help anyway, just to give some more details about the problem.
Last edited by 4s|m3tr|ko0 (2009-01-21 10:14:32)

4s|m3tr|ko0 wrote:
ballon wrote:It seems like my problems can be the same, however I haven't managed to solve it myself so if you can be more detailed that would be nice.
Of course I can, it's quite easy.
First of all, you have to boot from an Archlinux install CD, to have an usable environment. Once you have booted, I will assume a couple of things to make the examples, which are:
"/dev/sda2" is the root partition where the system is currently installed but not booting.
"/dev/sda1" is the boot partition (not needed if you don't have a separated boot partition, obviously).
"/mnt/myarch" is the directory where sda1 will be mounted on the live session.
The kernel version on sda2 is "2.6.27-ARCH", you can find which kernel versions are installed on sda2 by checking the directory names under "/lib/modules/"
Next you have to mount your root partition on any directory and mount the "boot" partition if you have one too:
mkdir /mnt/myarch #Creates the mount directory on the live session, you can use /mnt/ so this command is not neccesary
mount -t auto /dev/sda2 /mnt/myarch #Mount the root partition on the live session
mount -t auto /dev/sda1 /mnt/myarch/boot #Mount the boot partition, if you have to
Now, you'll have to bind three system directories to their true locations on the root partition:
mount -t proc proc /mnt/myarch/proc
mount -t sysfs sys /mnt/myarch/sys
mount -o bind /dev /mnt/myarch/dev
Next step is to use the command "chroot <target> <consolebin>" to "move" the system root to the <target> directory, using the <consolebin> command interpreter:
chroot /mnt/myarch/ /bin/bash
Now, you will be using your system just like if you had actually booted from your hard disk, but running the kernel from the liveCD, so the only remaining step is to generate the initcpio image.
In the example for this step, I will run the mkinitcpio twice, the first one to check that it's correctly generated, and the second to install it, using the parameter "-g". Another thing to keep in mind is that even before chrooting, the liveCD kernel is still running, so you will have tu use the "-k <kernelversion>" parameter to manually specify the kernel to use. Otherwise, mkinitcpio won't be able to find the correct modules to use:
mkinitcpio -k 2.6.27-ARCH #This will simulate the generation, if it runs fine, run the next command
mkinitcpio -g /boot/kernel26.img -k 2.6.27-ARCH #This will actually generate the image
And that's all, this should regenerate a default image. More info about mkinitcpio: http://wiki.archlinux.org/index.php/Mkinitcpio
Hope this heps
PS: Sweden, nice country .
I follow this guide and I saved my Arch installation. I don't know why the HOOKS array in my mkinitcpio.conf just contains "base" :-?
So, just before regenerate the ramdisk image I edit my /etc/mkinitcpio.conf and add all the neccessary hooks and generate. I can bring my Arch box back to life

[SOLVED]kexec into arch fails : root device not found

Hello,
I have a fresh arch install with only base, base-devel and openssh.
I boot on penbuntu, at this point I can see my devices in /dev.
Then I mount my root arch partition on /mnt/rootfs and do :
kexec --load /mnt/rootfs/boot/vmlinuz-linux --initrd=/mnt/rootfs/boot/initramfs-linux.img --command-line="root=/dev/sda3 ro vesa video=vesafb"
which returns :
setup_linux_vesafb: 1280x720x32 @ 10028000 +708000
I then do kexec -e, It seems to start loading the kernel since the screen is cleared and each time it does
[0.845500] i8042: No controller found
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/sda3 ...
ERROR: device '/dev/sda3' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda3' /
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#
I tried everything as root in the kexec --command-line, root=LABEL, root=UUID but it always do exactly the same thing, waits for 10s for device and then ERROR and drops to the recovery shell.
Any idea of what's going on ? Why can't it see devices ?
EDIT : If that can help, the kernel from which I am kexecing is 2.6.24.3 and If I try to just chroot I notice :
mount -t proc proc proc/
mount -t sysfs sys sys/
Works but when I :
mount -o bind /dev dev/
It returns :
mount: mounting /dev on dev/ failed: Invalid argument
So somehow I think when the kernel loads it has trouble passing the /dev along and therefore sees no devices. But I still can't figure out what to do.
Thanks in advance
Last edited by Nolhian (2012-07-28 17:47:30)

I can't because I'm booting on penbuntu and not arch linux. Anyways the command used in the wiki is similar to the one I'm using.

[PPC] new install fails to boot: root partition not found

Hi,
new ArchPPC installation on a iMac G3. It does not boot further than initramfs because root partition is not found. I get something like:
Root device /dev/sda4 doesn't exist
Attempting to created it
ERROR: unable to determine major/minor number of root device /dev/sda4
then I get a dropbox recovery console but keyboard doesn't work.
I chroot in the installed system to change mkinicpio pata hook to ide, regenerated initramfs but that didn't help.
Any guidance to diagnose and solve this issue would be greatly appreciated.

Hi, sorry I just realized you replied to my thread.
I don't have my mac at the moment, but I must have done something like :
- boot the live CD
- get the output of lsmod
- copy this output to mkinitcpio.conf (the one that's on your HD), remove the autodetect hook
- chroot into your HD setup
- regenerate initramfs
- update yaboot (is this really mandatory?)
- exit chroot and reboot.

[SOLVED] "Can't find root device" after hardware change

My old computer died so I got a replacement. The only hardware changes were the motherboard/CPU and a lack of GPU (since it died too). GRUB was setting root to /dev/sda2, but in this new computer that wouldn't work. I figured I'd change it to /dev/disk/by-label, but it still won't boot. I have udev loaded in mkinitcpio.conf and have tried what I could find on google (it had to do with pacman mostly, which is not the issue here).
I'm currently running a gparted parted magic live disc and checked already if the partition is corrupted; it isn't.
What should I be looking at to get by-label working? What kind of info do I need to provide in order to get some help (fdisk, blkid, etc)?
Thanks in advance.
Last edited by knuck (2012-08-19 02:07:01)

Are you sure that that label/partition still exists? (e.g. your filesystem hasn't gotten corrupted)
Have you rebuilt the initramfs since you changed hardware (e.g. via chroot)? If not, try booting using the fallback image.
All you should need to do to get booting by label is change the root= statement in the bootloader's kernel params to
root=LABEL=arch
the initram image's code should handle the rest at boot time.

What do i do if my computer says boot device not found

I turned on my computer and all it does is pop up a screen says boot up device not found please install operation system what do I do to fix it

may i have some more information about the product you have? check if there is some external device connected, and check for HDD self test in BIOS. if test passes without any error and there is no external device or disc on ODD. you may need to re-install OS.
Regards,
WW
“I am an HP Employee“
***** Click the KUDOS star on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem***

T410 bluetooth device NOT FOUND

Hello Everyone,
I have a t410, product id is 2539AJ6 (bluetooth included), running Windows 8.
however i can't get bluetooth to work, in addition it seems like there is no trace for a bluetooth device on this computer:
- Can't install driver ("Device not found").
- Not Recognized by Windows 8.
- on BIOS, Security -> I/O Port blah blah -> no mention of bluetooth settings there.
where do i go from here? anybody ever encountered such an issue with bluetooth?
btw, im pretty sure there is a bluetooth device on this laptop.
appreciate any help

Here's the Link for the 2539-AJ6, it does indicate that you have Bluetooth. Dowload and install the latest drivers.
http://support.lenovo.com/en_US/downloads/default.page?

My computer wont start up says boot device not found how can i fix that

I HAVE AN HP PROBOOK 4430S
SERIAL NUMBER {Removed for privacy}
THE ERROR MESSAGE IS BOOT DEVICE NOT FOUND HOW CAN I FIX THAT ERROR

Hi:
Go into the BIOS and run the hard drive diagnostics test and see what that reports.
Sounds like the hard drive failed.
Paul

[SOLVED] Device not found and kernel panic

Hi,
I'm having an issue with the kernel. I get this weird error while booting:
Booting the kernel.
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
ERROR: device '' not found. Skipping fsck.
ERROR: Unable to find root device ''.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]# _
I don't have the slightest idea what to type in that shell, so I exit (^D) and get an error with its shell, another one and finally a kernel panic. Do I have to report the other two error as well? I think this might be related to a recent change in my syslinux.cfg. I wanted to add hibernation cabability to my arch, so I added "resume=/dev/sda2" (my swap) to kernel options. It should not yield such a result though. As a matter of fact, I get it even if I remove that parameter at runtime. For now, I managed to boot with Fallback Initramfs.
Here is syslinux.cfg, as well:
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 1 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
# (0) Arch Linux
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/disk/by-uuid/dc891acc-9ff7-4d95-bba4-bc2e502301e7 ro
APPEND resume=/dev/sda2
INITRD ../initramfs-linux.img
# (1) Arch Linux Fallback
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/disk/by-uuid/dc891acc-9ff7-4d95-bba4-bc2e502301e7 ro
INITRD ../initramfs-linux-fallback.img
# (2) Windows
#LABEL windows
#COM32 chain.c32
#APPEND hd0 0
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com
Any ideas?
Thank you,
rubik
Last edited by rubik (2012-07-22 10:03:59)

Also, don't use "root=/dev/disk/by-uuid/...", that's just wrong. Udev kicks in after the bootloader phase.
https://wiki.archlinux.org/index.php/Sy … nux_Config
Here's mine:
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=UUID=978e3e81-8048-4ae1-8a06-aa727458e8ff ro quiet vga=current
INITRD ../initramfs-linux.img
And don't forget to mark it as solved.

Presario CQ61 - Boot Device not found, Hard dis not exist

Hi i bought my presario CQ61-405AX 2nd hand roughly a year ago and it was almost new, my laptop was running fine, and then it froze, and so i had to turn it off, after i waited 30min for it to unfreeze, it now, when i boot it up, appears with a black screen, with the error
"Boot Device Not Found
Pleae install a operating system on your hard disk
F2 system diagnostiscs"
I went onto hp support and followed the prompts until it did a hard disk test and the error, "Hard Disk Not Exist" appeared
I have no idea how to fix it, i am running Windows 7 home premium, and i fear i may have to buy another hard drive
Thank's in advance
This question was solved.
View Solution.

Hi,
The most likely explanation is that your Hard Drive has failed and will need to be replaced, however as a further test, try the following.
1. Create a bootable Ubuntu CD - a guide on creating an Ubuntu CD and the download can be found Here.
2. When created, follow the guide on the link below to Try Ubuntu.
http://www.ubuntu.com/download/help/try-ubuntu-before-you-install
The 'Try Ubuntu' option runs the OS from the CD without the need to install on your HDD. If this runs Ok ( it will be slow running from a CD ), this would tend to confirm that the problem is with the HDD.
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

Boot device not found, hard disk not exist.... does that mean my computer is dead?

Suspecting that Im in a world of hurt here. I tried turning on my computer and it says "boot device not found" - run in test failed... when I hit F4 and run a hard disk test it says "hard disk not exist". The memory test passes, but under the boot device not found it says in blue "please install an operating system on your hard disk"... and to make matters worse it's making some funny noises when it tries to boot.
Is there any hope at all that this computer will work again? Is there any chance that any of the things I had on my hard disk can be recovered?
This question was solved.
View Solution.

You're very welcome, Jonathan.
dv5 still isn't enough info for me to provide the service manual (in case there are differerent ones for the different dv5 models).
However here is the link to the service manual I randomly pulled.
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01550108/c01550108.pdf
Assume it is safe to say all dv5 models come with SATA notebook drives.
So, if you want to spring for $15, you can get this enclosure which apparently has very good reviews.
http://www.newegg.com/Product/Product.aspx?Item=N82E16817182138
From what you are describing (noise and stuff), I would say you don't have much of a chance to recover data but that is up to you if you want to try the enclosure or not.
Here is what I recommend:
Yank the hard drive, and power on the notebook.
If the odd noise you heard is gone, then you can pretty much safely assume the drive was the cause, and that replacing the drive, and reinstalling the operating system will solve the issue.
If the noise is still there, then there could be another issue, and it might be risky throwing good money after bad.
Paul

Boot Device Not Found Please Intall an Operating system on your hard disk. Hard Disk - (3F0)

Hello,
I tried to re-install de OS from windows 7 to windows 8.1 and when the bios update driever was installed and the laptop was restaring it appeared the folowing window and message:
Boot Device Not Found Please Intall an Operating system on your hard disk. Hard Disk - (3F0)
After that i tried a lot of different ways to get to boot device select ...but i couldn't do anything. I removed the HDD and i put it back, i've tried with holding in the same time windows +B and pressing the power button in the same time for 1..2 seconds and then i've waited for at least 1 minute..and it didn't appeared anything on the screen. I've done the hard drive check and it passed. The weirdest thing is that when i want to select a boot device to re-install again the OS, i can't see any boot device to select. I need to mention that i've formatted the HDD in another computer. I dont care about the informations from the HDD beacause i saved all the informations on another device storage.
Please help me repair this problem!!! thanks a lot!
Have a nice evening.!!!

Whenever you get a message stating that the boot device not found it could be because of bad sectors on the Hard Drive. Its not necessary that the Hard Drive Test should fail to determine if the Hard Drive if its faulty or not. Sometimes even if the Hard Drive Test passes the Hard Drive will still not work because of the bad sectors in it.
Best way to find out if its the Hard Drive you can try the Hard Deive on a different Notebook which would help you determine if it's faulty or not.
Could be due to Application or driver conflicts, virus issues, file corruptions due to incompatible applications, improper shutdowns, update failures due to conflicts, sudden power surges, if notebook is dropped etc..
HP will provide a replacement Hard Disk Drive if the Notebook warranty is Active, If not you need buy a SATA Hard Disk Drive from a retail shop nearby
Please make sure you are getting at least equal capacity as the original one in order to use Recovery Disks. If you need you can buy a larger, but not smaller capacity Hard Disk Drive. For example if you have a 500GB Hard Disk Drive you can upgrade it to 750GB Hard Disk Drive but not 320GB Hard Disk Drive
Please try the below shown troubleshooting steps once:
Step 01. Remove the battery and unplug the AC/Power Adapter
Step 02. Press and hold the Power button for more than 30 Seconds
Step 03. Plug in the AC/Power Adapter (leave the Battery out for now)
Step 04. Press the Power button and check if the Unit works normal
If the above mentioned steps does not help, then you can try reseating the Hard Drive on your Notebook
If the issue persists again please Contact HP if your HP Notebook is under warranty, HP would replace the Hard Disk Drive and provide you a Recovery media to restore factory operating system after replacement (if you've not yet created Recovery Discs/USB Media)
Note: Back up all the personal data to an external drive if it's possible. Otherwise you could connect the failed HDD via SATA to USB adapter with another PC or same PC after replacement of HDD & re-installation of OS and try copying /recovering the files.
Please click on the link In order to Identify, Prevent, Diagnose & Recover from Drive Failures on HP Notebook Hard Drives & Solid State Drives :
http://h10032.www1.hp.com/ctg/Manual/c02876562.pdf
Please check your notebook warranty to verify the status and order a new Hard Disk Drive
Hope this helps, for any further queries reply to the post and feel free to join us again
**Click the KUDOS star on left to say Thanks**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.
Thank You,
K N R K
Although I am an HP employee, I am speaking for myself and not for HP

My screen says boot device not found. Please install an operating system on hard drive,

My screen says boot device not found. Please install an operating system on hard drive. What could have caused this problem? Help!!!!!

Hi,
Can you post back with the following.
1. The full Model No. and Product No. of the notebook - see Here for a further explanation.
2. The full version of the operating system you are using ( ie Windows 7 32bit ).
3. Shut down the notebook. Tap away at f10 as you start the notebook to enter the bios menu. Under the Advanced or Diagnostic tab you should find the facility to run a test on the Hard Drive. Post back with the details of any error messages.
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

[Solved] Can't boot, root device not found

Similar Messages

Maybe you are looking for