LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 11-04-2018, 05:01 PM   #1
giancarlo64
Member
 
Registered: Jul 2018
Location: Switzerland
Distribution: debian
Posts: 33

Rep: Reputation: Disabled
Failure reading sector 0x...... from hd0


Hi to all,
I have the following HW:

Motherboard: ASUS ROG MAXIMUS VII RANGER with Intel I7-4790K
Memory 24GB
SSD M.2 PCIE SAMSUNG SSD 970 EVO 1TB (new 2 days old)

Linux Mint 19 installed.

Sometimes on boot I get the message: Failure reading sector 0x...... from hd0: Hit a key to continue (The address can change at every error message).
Keyboard is not responding so I have to reboot the PC to boot again. Sometimes it start normally and sometimes I get the error

Time to boot take usually quite long (25 seconds)

I have also verified the SSD with the command: smartctl -a /dev/nvme0n1p1

this is the result

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-20-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 970 EVO 1TB
Serial Number: S467NX0K805417H
Firmware Version: 1B2QEXE7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 1'000'204'886'016 [1.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 1'000'204'886'016 [1.00 TB]
Namespace 1 Utilization: 160'459'276'288 [160 GB]
Namespace 1 Formatted LBA Size: 512
Local Time is: Sun Nov 4 22:34:46 2018 CET
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL *Other*
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat *Other*
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 85 Celsius
Critical Comp. Temp. Threshold: 85 Celsius

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.20W - - 0 0 0 0 0 0
1 + 4.30W - - 1 1 1 1 0 0
2 + 2.10W - - 2 2 2 2 0 0
3 - 0.0400W - - 3 3 3 3 210 1200
4 - 0.0050W - - 4 4 4 4 2000 8000

Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0x1)
Critical Warning: 0x00
Temperature: 31 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 116'135 [59.4 GB]
Data Units Written: 323'991 [165 GB]
Host Read Commands: 961'184
Host Write Commands: 416'098
Controller Busy Time: 6
Power Cycles: 26
Power On Hours: 1
Unsafe Shutdowns: 18
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 31 Celsius
Temperature Sensor 2: 36 Celsius

Error Information (NVMe Log 0x01, max 64 entries)
No Errors Logged

It seems ok.

I don't understand where the problem could be. Is the new SSD ?

I also attach the dmesg on boot. I don't know is it can help.

Gian Carlo
Attached Files
File Type: txt problemi boot.txt (58.1 KB, 15 views)
 
Old 11-04-2018, 06:28 PM   #2
kilgoretrout
Senior Member
 
Registered: Oct 2003
Posts: 2,732

Rep: Reputation: 259Reputation: 259Reputation: 259
Quote:
SSD M.2 PCIE SAMSUNG SSD 970 EVO 1TB (new 2 days old)
I'm assuming you cloned your old hard drive to your new nvme drive. The hd0 error sounds to me like a grub2 error; namely, grub is looking for your old hard drive on the sata bus and can't find it or finds it but doesn't find the boot info it expects and finally finds something bootable on your nvme drive. This would explain the delay. Could you verify that I've guessed correctly and, if so, describe how you did the clone. Also, post the output of:
Code:
$ lsblk
As to a possible fix, you could try updating grub with:
Code:
sudo update-grub
If that doesn't help, there may be something in your initrd causing an issue. You can generate a new one but before doing so, I'd like to be more sure of the assumptions I'm making here.
 
Old 11-04-2018, 11:02 PM   #3
JJJCR
Senior Member
 
Registered: Apr 2010
Posts: 1,645

Rep: Reputation: 278Reputation: 278Reputation: 278
Have you tried booting to Linux Live CD?

If Linux live CD, doesn't show any error then I think you might need to reinstall and reformat your drive. Not sure though whether it will solve the error.

I just base my assumption from this link: https://arstechnica.com/civis/viewtopic.php?t=1170086

Scroll down on the link above and look for: Paul Bartz comment.

If it is still under warranty you can always return it.

Good luck!
 
Old 11-05-2018, 01:20 AM   #4
giancarlo64
Member
 
Registered: Jul 2018
Location: Switzerland
Distribution: debian
Posts: 33

Original Poster
Rep: Reputation: Disabled
Hi kilgoretrout

I didn't clone the drive. Is a fresh new install from scratch. I want to replace my old AMD PC (10 years old). So until all is not working ok I will use my old PC.
I have created a bootable USB pen with Mint 19 and installed from it

$ lsblk give me the following result:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 931.5G 0 disk
└─nvme0n1p1 259:1 0 931.5G 0 part /

To be sure I have also loaded the BIOS default settings

For information I have a NVIDIA GTX 970 GPU and also a card reader (micro-SD, SD ..... and also USB 3.0 and 3.1) connected to the USB3.0 (19 pin) MOBO internal connector.
This give me some problems because at boot when I have to introduce my password I have to wait 3-4 seconds because the keyboard and mouse are not responding.(But also without the card reader I get the hdo error)

I have done the upgrade of grub and I have rebooted now 8-10 times the PC without receive no more the message "Failure reading sector 0x....."
I still have long delay from power up to login but now I can introduce immediately my password

For the delay I tried the following command: systemd-analyze blame

3.363s NetworkManager-wait-online.service
586ms NetworkManager.service
393ms lightdm.service
392ms plymouth-quit-wait.service
144ms dev-nvme0n1p1.device
129ms udisks2.service
127ms systemd-timesyncd.service
116ms systemd-resolved.service
104ms ubuntu-system-adjustments.service
102ms networkd-dispatcher.service
71ms networking.service
65ms apparmor.service
63ms systemd-journal-flush.service
58ms ModemManager.service
53ms accounts-daemon.service
51ms upower.service
....................

In dmesg I see lot of delay on the following lines


[ 3.840131] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 4.247330] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
[ 4.247433] caller os_map_kernel_space.part.7+0xda/0x120 [nvidia] mapping multiple BARs
[ 6.962034] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 6.962061] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready


[ 7.044609] vboxpci: IOMMU not found (not registered)
[ 8.051389] kauditd_printk_skb: 11 callbacks suppressed
[ 8.051392] audit: type=1400 audit(1541397763.837:22): apparmor="DENIED" operation="open" profile="/usr/sbin/cups-browsed" name="/usr/share/cups/locale/" pid=937 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 8.054180] audit: type=1400 audit(1541397763.837:23): apparmor="DENIED" operation="open" profile="/usr/sbin/cups-browsed" name="/usr/share/locale/" pid=937 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 42.564010] random: crng init done


This evening I will do some more boot to be sure that I get no more the problem.

Regards

Gian Carlo
 
Old 11-05-2018, 01:23 AM   #5
giancarlo64
Member
 
Registered: Jul 2018
Location: Switzerland
Distribution: debian
Posts: 33

Original Poster
Rep: Reputation: Disabled
HI JJJCR
the error is not on address 0x00 I wrote 0x.... to tell that the address is always different sometimes 0xce5980 or 0xd15980 or 0xcec400

now with grub update it seems that I get no more the problem. Only long boot time. I will do some more boot tests this evening

Gian Carlo
 
Old 11-05-2018, 03:39 AM   #6
tuwamichael
LQ Newbie
 
Registered: Nov 2018
Posts: 1

Rep: Reputation: 1
thanks
 
Old 11-05-2018, 04:20 AM   #7
giancarlo64
Member
 
Registered: Jul 2018
Location: Switzerland
Distribution: debian
Posts: 33

Original Poster
Rep: Reputation: Disabled
Hi to all,
talking to a work colleague, he had also this slow boot problem. He solved the problem installin the "haveged" package

https://www.linuxuprising.com/2018/0...te-causes.html

About the hd0 problem, could it be that hd0 was the USB-stick used to install Linux and after udating grub it has been removed from it?

Gian Carlo

Last edited by giancarlo64; 11-05-2018 at 04:21 AM.
 
1 members found this post helpful.
Old 11-05-2018, 07:59 AM   #8
kilgoretrout
Senior Member
 
Registered: Oct 2003
Posts: 2,732

Rep: Reputation: 259Reputation: 259Reputation: 259
One other thing you might check is for a bios update from Asus. When that board came out, and NVME-PCIE drives were just starting to come out. I have a similar vintage Asus board and needed a bios update for proper NVME functioning. Here's the Asus support page for your board listing the bios updates issued:

https://www.asus.com/Motherboards/MA...HelpDesk_BIOS/

One of the updates specifically mentions enhancing compatibility with PCIE devices. There's also another one mentioning M2 drive compatibility.

Last edited by kilgoretrout; 11-05-2018 at 08:44 AM.
 
Old 11-05-2018, 08:02 AM   #9
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 8,904

Rep: Reputation: 1859Reputation: 1859Reputation: 1859Reputation: 1859Reputation: 1859Reputation: 1859Reputation: 1859Reputation: 1859Reputation: 1859Reputation: 1859Reputation: 1859
I don't know if you are familiar with the boot repair software for the Ubuntu based systems? It has an option to Create BootInfo Summary which will output a lot of details on your system to review which is very helpful resolving boot problems. See the link below. Best to use the 2nd option with the ppa.

https://help.ubuntu.com/community/Boot-Repair
 
Old 11-05-2018, 04:25 PM   #10
giancarlo64
Member
 
Registered: Jul 2018
Location: Switzerland
Distribution: debian
Posts: 33

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by kilgoretrout View Post

https://www.asus.com/Motherboards/MA...HelpDesk_BIOS/

One of the updates specifically mentions enhancing compatibility with PCIE devices. There's also another one mentioning M2 drive compatibility.
Hi kilgoretrout
I have the 3003 version, not the last one (3503) that is still in beta version. I didn't find the changelog of the last bios 3503.

By the way I have installed haveged pakage but nothing changed

try to find the boot time with "systemd-analyze" command
Result:

Startup finished in 2.718s (kernel) + 4.241s (userspace) = 6.959s
graphical.target reached after 4.237s in userspace

It seems all ok but the login screen appear only after 40 seconds!
Strange

Gian Carlo

Last edited by giancarlo64; 11-05-2018 at 04:42 PM.
 
Old 11-05-2018, 08:45 PM   #11
giancarlo64
Member
 
Registered: Jul 2018
Location: Switzerland
Distribution: debian
Posts: 33

Original Poster
Rep: Reputation: Disabled
Hi again,
I have tried to speed up the boot but at the end I have got again the hd0 problem.

I have tried changing Secure Boot in the BIOS from Windows UEFI to Other OS,

I have found another problem with bluetooth (not available!) dbus-daemon[928]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

At the end I give it up (sorry) and I downloaded Debian 9 with cinnamon and installed it. This distro work fine. No boot delay, up to now no boot problem (hd0)

I will test it next days to be sure that the hd0 problem doesn't show up again

Regards

Gian Carlo
 
Old 05-28-2019, 05:46 AM   #12
adubourg
LQ Newbie
 
Registered: May 2019
Distribution: Debian
Posts: 1

Rep: Reputation: Disabled
Hi,

I have the very same ASUS MAXIMUS VII RANGER motherboard, the same Samsung 970 EVO NVMe M.2 SSD with Debian 10 "Buster", and the same occasional "Failure reading sector 0x from hd0" error message -- or rather the occasional *boot without* this error message.
Did you manage to solve your problem, and if so, how?

Thanks!

-- Alex
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Failure reading sector 0xfc from 'hd1' error... codyngr Linux - Newbie 4 12-08-2016 09:49 AM
[SOLVED] grub hd0,0 hd0,1 clarification for using single /boot partition zeebra Linux - General 2 02-28-2012 04:07 PM
Corrupted font after reading the 1st sector from an USB drive using dd Geriao Linux - Software 4 03-19-2010 07:38 PM
Error reading sector 2 firewiz87 SUSE / openSUSE 2 05-09-2009 03:58 AM
Failure to Dualboot with Mepis and Windows ; Error message of 'rootnoverify (hd0,1)' blooperspree Linux - Software 1 11-02-2006 07:08 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 03:35 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration