Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
10-30-2019, 09:57 AM
|
#1
|
|
LQ Newbie
Registered: Oct 2019
Posts: 7
Rep: 
|
How to solve "Background long Failed in segment" problem ?
Hello,
My server reports a problem, it displays without stopping this message:
blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
and when I execute the smartctl command:
smartctl -d cciss,3 -l selftest /dev/cciss/c0d0
I get the following:
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-8-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Failed in segment --> - 63321 155950023 [0x3 0x11 0x0]
# 2 Background short Completed - 63321 - [- - -]
Long (extended) Self Test duration: 2070 seconds [34.5 minutes]
can you tell me what do I have to do to solve this problem
I thank you in advance |
|
|
|
|
10-30-2019, 10:03 AM
|
#2
|
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,663
|
Quote:
Originally Posted by pipa85
Hello,
My server reports a problem, it displays without stopping this message:
blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
and when I execute the smartctl command:
smartctl -d cciss,3 -l selftest /dev/cciss/c0d0
I get the following:
Code:
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-8-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Failed in segment --> - 63321 155950023 [0x3 0x11 0x0]
# 2 Background short Completed - 63321 - [- - -]
Long (extended) Self Test duration: 2070 seconds [34.5 minutes]
can you tell me what do I have to do to solve this problem I thank you in advance |
You replace the failed disk and restore from backup.
And you should also read the LQ Rules about not posting the same question in multiple forums, and about providing details when asking questions, such as version/distro of Linux, what kind of hardware, what you've done/tried/etc. |
|
|
1 members found this post helpful.
|
|
11-03-2019, 06:57 AM
|
#3
|
|
LQ Newbie
Registered: Oct 2019
Posts: 7
Original Poster
Rep:
|
Hello,
I'm sorry for the duplicate message I did not know it's forbidden and I thank you for your answer. Concerning my system we have debian installed on a 64 bits server, I do not know too much about hardware. as I told you above, our server displays without stopping the message below:
blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
and the output of the following command
dmesg -T --level=err,warn
is:
[ 0.000000] ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20160831/tbfadt-708)
[ 0.088000] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 186 is 43003c)
[ 0.088000] Intel PMU driver.
[ 0.244757] ACPI Error: Field [CDW3] at 96 exceeds Buffer [NULL] size 64 (bits) (20160831/dsopcode-236)
[ 0.244875] ACPI Error: Method parse/execution failed [\_SB._OSC] (Node ffff8fdfef5b24d8), AE_AML_BUFFER_LIMIT (20160831/psparse-543)
[ 0.751215] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.751365] ACPI Error: Method parse/execution failed [\_PR.CPU0._CST] (Node ffff8fdfef5c3230), AE_NOT_FOUND (20160831/psparse-543)
[ 0.751618] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.751763] ACPI Error: Method parse/execution failed [\_PR.CPU4._CST] (Node ffff8fdfef5c33e8), AE_NOT_FOUND (20160831/psparse-543)
[ 0.752000] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.752153] ACPI Error: Method parse/execution failed [\_PR.CPU2._CST] (Node ffff8fdfef5c3640), AE_NOT_FOUND (20160831/psparse-543)
[ 0.752392] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.752536] ACPI Error: Method parse/execution failed [\_PR.CPU6._CST] (Node ffff8fdfef5c32a8), AE_NOT_FOUND (20160831/psparse-543)
[ 0.752772] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.752916] ACPI Error: Method parse/execution failed [\_PR.CPU1._CST] (Node ffff8fdfef5c3ca8), AE_NOT_FOUND (20160831/psparse-543)
[ 0.753180] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.753351] ACPI Error: Method parse/execution failed [\_PR.CPU5._CST] (Node ffff8fdfef5c3690), AE_NOT_FOUND (20160831/psparse-543)
[ 0.753616] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.753788] ACPI Error: Method parse/execution failed [\_PR.CPU3._CST] (Node ffff8fdfef5c3c80), AE_NOT_FOUND (20160831/psparse-543)
[ 0.754051] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.754223] ACPI Error: Method parse/execution failed [\_PR.CPU7._CST] (Node ffff8fdfef5c3528), AE_NOT_FOUND (20160831/psparse-543)
[ 0.754551] ERST: Failed to get Error Log Address Range.
[ 0.913103] cciss 0000:1f:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 11.557954] ACPI Warning: SystemIO range 0x0000000000000928-0x000000000000092F conflicts with OpRegion 0x0000000000000928-0x000000000000092F (\SGPE) (20160831/utaddress-247)
[ 11.558009] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 12.293440] CRAT table not found
[ 12.319040] radeon 0000:01:03.0: firmware: failed to load radeon/R100_cp.bin (-2)
[ 12.319156] radeon 0000:01:03.0: Direct firmware load for radeon/R100_cp.bin failed with error -2
[ 12.319392] [drm:r100_cp_init [radeon]] *ERROR* Failed to load firmware!
[ 12.319465] radeon 0000:01:03.0: failed initializing CP (-2).
[ 12.319533] radeon 0000:01:03.0: Disabling GPU acceleration
[ 12.331463] kvm: disabled by bios
[ 12.550154] kvm: disabled by bios
[ 42.603516] cciss 0000:1f:00.0: cmd ffff8fdbf6900000 has CHECK CONDITION sense key = 0x3
[ 42.603531] blk_update_request: I/O error, dev cciss/c0d0, sector 779750048
[ 42.729249] cciss 0000:1f:00.0: cmd ffff8fdbf6900280 has CHECK CONDITION sense key = 0x3
[ 42.729256] blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
[ 52.617100] cciss 0000:1f:00.0: cmd ffff8fdbf6900000 has CHECK CONDITION sense key = 0x3
[ 52.617119] blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
[ 61.443842] cciss 0000:1f:00.0: cmd ffff8fdbf6900000 has CHECK CONDITION sense key = 0x3
[ 61.443863] blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
[ 70.148486] cciss 0000:1f:00.0: cmd ffff8fdbf6900000 has CHECK CONDITION sense key = 0x3
and as I said above, the smart command displays the following result:
#smartctl -d cciss,3 -l selftest /dev/cciss/c0d0
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-8-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Failed in segment --> - 63321 155950023 [0x3 0x11 0x0]
# 2 Background short Completed - 63321 - [- - -]
Long (extended) Self Test duration: 2070 seconds [34.5 minutes]
so for you I have to replace the failing disk ?
can you tell me what do the errors displayed by the dmesg command mean?
Thank you for your help |
|
|
|
|
11-03-2019, 07:20 AM
|
#4
|
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,663
|
Quote:
Originally Posted by pipa85
Hello,
I'm sorry for the duplicate message I did not know it's forbidden and I thank you for your answer. Concerning my system we have debian installed on a 64 bits server, I do not know too much about hardware. as I told you above, our server displays without stopping the message below:
Code:
blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
and the output of the following command
Code:
dmesg -T --level=err,warn
[ 0.000000] ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20160831/tbfadt-708)
[ 0.088000] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 186 is 43003c)
[ 0.088000] Intel PMU driver.
[ 0.244757] ACPI Error: Field [CDW3] at 96 exceeds Buffer [NULL] size 64 (bits) (20160831/dsopcode-236)
[ 0.244875] ACPI Error: Method parse/execution failed [\_SB._OSC] (Node ffff8fdfef5b24d8), AE_AML_BUFFER_LIMIT (20160831/psparse-543)
[ 0.751215] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.751365] ACPI Error: Method parse/execution failed [\_PR.CPU0._CST] (Node ffff8fdfef5c3230), AE_NOT_FOUND (20160831/psparse-543)
[ 0.751618] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.751763] ACPI Error: Method parse/execution failed [\_PR.CPU4._CST] (Node ffff8fdfef5c33e8), AE_NOT_FOUND (20160831/psparse-543)
[ 0.752000] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.752153] ACPI Error: Method parse/execution failed [\_PR.CPU2._CST] (Node ffff8fdfef5c3640), AE_NOT_FOUND (20160831/psparse-543)
[ 0.752392] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.752536] ACPI Error: Method parse/execution failed [\_PR.CPU6._CST] (Node ffff8fdfef5c32a8), AE_NOT_FOUND (20160831/psparse-543)
[ 0.752772] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.752916] ACPI Error: Method parse/execution failed [\_PR.CPU1._CST] (Node ffff8fdfef5c3ca8), AE_NOT_FOUND (20160831/psparse-543)
[ 0.753180] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.753351] ACPI Error: Method parse/execution failed [\_PR.CPU5._CST] (Node ffff8fdfef5c3690), AE_NOT_FOUND (20160831/psparse-543)
[ 0.753616] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.753788] ACPI Error: Method parse/execution failed [\_PR.CPU3._CST] (Node ffff8fdfef5c3c80), AE_NOT_FOUND (20160831/psparse-543)
[ 0.754051] ACPI Error: [CS03] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[ 0.754223] ACPI Error: Method parse/execution failed [\_PR.CPU7._CST] (Node ffff8fdfef5c3528), AE_NOT_FOUND (20160831/psparse-543)
[ 0.754551] ERST: Failed to get Error Log Address Range.
[ 0.913103] cciss 0000:1f:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 11.557954] ACPI Warning: SystemIO range 0x0000000000000928-0x000000000000092F conflicts with OpRegion 0x0000000000000928-0x000000000000092F (\SGPE) (20160831/utaddress-247)
[ 11.558009] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 12.293440] CRAT table not found
[ 12.319040] radeon 0000:01:03.0: firmware: failed to load radeon/R100_cp.bin (-2)
[ 12.319156] radeon 0000:01:03.0: Direct firmware load for radeon/R100_cp.bin failed with error -2
[ 12.319392] [drm:r100_cp_init [radeon]] *ERROR* Failed to load firmware!
[ 12.319465] radeon 0000:01:03.0: failed initializing CP (-2).
[ 12.319533] radeon 0000:01:03.0: Disabling GPU acceleration
[ 12.331463] kvm: disabled by bios
[ 12.550154] kvm: disabled by bios
[ 42.603516] cciss 0000:1f:00.0: cmd ffff8fdbf6900000 has CHECK CONDITION sense key = 0x3
[ 42.603531] blk_update_request: I/O error, dev cciss/c0d0, sector 779750048
[ 42.729249] cciss 0000:1f:00.0: cmd ffff8fdbf6900280 has CHECK CONDITION sense key = 0x3
[ 42.729256] blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
[ 52.617100] cciss 0000:1f:00.0: cmd ffff8fdbf6900000 has CHECK CONDITION sense key = 0x3
[ 52.617119] blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
[ 61.443842] cciss 0000:1f:00.0: cmd ffff8fdbf6900000 has CHECK CONDITION sense key = 0x3
[ 61.443863] blk_update_request: I/O error, dev cciss/c0d0, sector 779750080
[ 70.148486] cciss 0000:1f:00.0: cmd ffff8fdbf6900000 has CHECK CONDITION sense key = 0x3
and as I said above, the smart command displays the following result:
#smartctl -d cciss,3 -l selftest /dev/cciss/c0d0
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-8-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Failed in segment --> - 63321 155950023 [0x3 0x11 0x0]
# 2 Background short Completed - 63321 - [- - -]
Long (extended) Self Test duration: 2070 seconds [34.5 minutes]
so for you I have to replace the failing disk ? can you tell me what do the errors displayed by the dmesg command mean? Thank you for your help |
They mean that your DISK HAS FAILED. Smartctl tells you that the disk failed, and it even tells you what device/partition failed at what sector.
If you can't tell us anything about the hardware it's on, then there's nothing much we can tell you past what we're seeing. Saying a "64 bits server" tells us next to nothing. Again; it appears you have a failed disk. Replace it, reload the OS, and restore your data from backups. |
|
|
|
|
11-04-2019, 01:24 AM
|
#5
|
|
LQ Addict
Registered: Dec 2013
Posts: 19,872
|
pipa85, what have you done to troubleshoot this problem?
Maybe did a search for an error message? |
|
|
|
|
11-04-2019, 07:32 AM
|
#6
|
|
LQ Newbie
Registered: Oct 2019
Posts: 7
Original Poster
Rep:
|
Hello,
How do I know which of the disks on the server is failing, the system sees all disks as a single disk. our server has actually 5 physical disks.
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 1024M 0 rom
cciss/c0d0 104:0 0 683,5G 0 disk
├─cciss/c0d0p1 104:1 0 655,9G 0 part /
├─cciss/c0d0p2 104:2 0 1K 0 part
└─cciss/c0d0p5 104:5 0 27,7G 0 part [SWAP]
thank you for your help
|
|
|
|
|
11-04-2019, 08:01 AM
|
#7
|
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,663
|
Quote:
Originally Posted by pipa85
Hello,
How do I know which of the disks on the server is failing, the system sees all disks as a single disk. our server has actually 5 physical disks.
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 1024M 0 rom
cciss/c0d0 104:0 0 683,5G 0 disk
├─cciss/c0d0p1 104:1 0 655,9G 0 part /
├─cciss/c0d0p2 104:2 0 1K 0 part
└─cciss/c0d0p5 104:5 0 27,7G 0 part [SWAP]
thank you for your help
|
Have you tried actually *LOOKING AT THE SERVER*?? There are typically lights on the front of the drives, indicating drive status/failures. You *STILL* say nothing about your actual hardware, despite being asked. If you are the admin, how did you build this server without knowing anything about it?
You have a RAID controller in your server; have you tried going in to the RAID BIOS and looking at anything?? Asking us the same thing repeatedly won't get you different answers. You have a failed disk and need to replace it. Since you won't answer ANY questions about your hardware we can't tell you anything past that...and even if you DID, we could only then tell you "Go look at the server". You have an array configured; look at the array, look at the drive(s). |
|
|
|
|
11-04-2019, 09:04 AM
|
#8
|
|
LQ Newbie
Registered: Oct 2019
Posts: 7
Original Poster
Rep:
|
I have already looked at the lights on the front of the drives, they are all as usual neither orange nor red
as I told you above I don't know much about hardware, tell me what do you want to know exctly ? what command you want me to execute? I have only installed the system on this server (HP Proliant ML 370 G5) wich has 5 disks each one 146 G
I know that I have to replace de failing disk but I dont know wich one
I will see if I can disable the raid in the bios in order to run the smartctl command on each disk
I thank you for your patience
|
|
|
|
|
11-04-2019, 09:22 AM
|
#9
|
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,663
|
Quote:
Originally Posted by pipa85
I have already looked at the lights on the front of the drives, they are all as usual neither orange nor red
|
And we don't know what you've done unless you tell us.
Quote:
|
as I told you above I don't know much about hardware, tell me what do you want to know exctly ? what command you want me to execute? I have only installed the system on this server (HP Proliant ML 370 G5) wich has 5 disks each one 146 G
|
Sorry, if you don't know about the hardware, you need to find a co-worker who does. AGAIN, as you were told, go into the RAID controller BIOS and look at things, and it should tell you which drive failed. Read the manual on your hardware, look at the user and admin guides you can find on the HP website.
Quote:
|
I know that I have to replace de failing disk but I dont know wich one I will see if I can disable the raid in the bios in order to run the smartctl command on each disk
|
If you disable the RAID, you will LOSE YOUR ENTIRE ARRAY. AGAIN: go into the RAID BIOS and execute whatever tests you have available to you. We cannot read the manual on your system for you, and tell you what to look at. |
|
|
|
|
11-04-2019, 03:05 PM
|
#10
|
|
Member
Registered: Apr 2019
Location: Esbjerg
Distribution: Windows 7...
Posts: 773
|
|
|
|
|
|
11-05-2019, 02:34 AM
|
#11
|
|
LQ Newbie
Registered: Oct 2019
Posts: 7
Original Poster
Rep:
|
Thank you very much to both of you for this useful information, I will explore the links that JAN K gave me and I will keep you informed of my progress.
That's how we learn, there is always a beginning
sorry for my bad English
|
|
|
|
|
11-05-2019, 06:50 AM
|
#12
|
|
LQ Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 27,663
|
Quote:
Originally Posted by pipa85
Thank you very much to both of you for this useful information, I will explore the links that JAN K gave me and I will keep you informed of my progress.
That's how we learn, there is always a beginning sorry for my bad English
|
Right; and that beginning should be reading the manual and documentation, and doing basic research. |
|
|
|
|
11-17-2019, 08:55 AM
|
#13
|
|
LQ Newbie
Registered: Oct 2019
Posts: 7
Original Poster
Rep:
|
Hello,
the server was delivered with a set of tools for server configuration and management among them diagnostic tools wich allowed me to find the failed drives, so I replaced the failing disks.
|
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 05:42 AM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
