cancel
Showing results for 
Search instead for 
Did you mean: 

P4610 NVMe XFS I/O Error ??

yout
New Contributor

Suddenly XFS I / O error in idle state after 16:00 booting completion on server.

Q1. I want to find the cause of the error.

Q2. If you receive this error, provide a link to a similar case.

The server information is as follows:

Ubuntu 16.04.6 LTS

Kernel 4.4.150- Generic

NVMe P4610 1.6 TB (XFS Format)

The error log is as follows:

Aug 12 15:51:43 mm-ai-df142 kernel: [ 392.330675] Code: 08 c0 ff ff 0f 01 c8 49 8b 80 08 c0 ff ff a8 08 0f 85 2f 01 00 00 e9 07 00 00 00 0f 00 2d 98 b5 9c 00 31 c0 48 89 c1 fb 0f 01 c9 <85> ff 74 15 48 89 f0 b9 48 00 00 00 48 83 c8 01 48 89 c2 48 c1 

Aug 12 15:59:36 mm-ai-df142 kernel: [ 865.704633] usb 1-1: USB disconnect, device number 5

Aug 12 15:59:44 mm-ai-df142 kernel: [ 874.055484] usb 1-1: new low-speed USB device number 6 using xhci_hcd

Aug 12 15:59:45 mm-ai-df142 kernel: [ 874.250784] usb 1-1: New USB device found, idVendor=04d9, idProduct=a0be

Aug 12 15:59:45 mm-ai-df142 kernel: [ 874.250787] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

Aug 12 15:59:45 mm-ai-df142 kernel: [ 874.250866] usb 1-1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes

Aug 12 15:59:45 mm-ai-df142 kernel: [ 874.250870] usb 1-1: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes

Aug 12 15:59:45 mm-ai-df142 kernel: [ 874.259611] input: HID 04d9:a0be as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:04D9:A0BE.0007/input/input7

Aug 12 15:59:45 mm-ai-df142 kernel: [ 874.315628] hid-generic 0003:04D9:A0BE.0007: input,hidraw0: USB HID v1.11 Keyboard [HID 04d9:a0be] on usb-0000:00:14.0-1/input0

Aug 12 15:59:45 mm-ai-df142 kernel: [ 874.336051] input: HID 04d9:a0be as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:04D9:A0BE.0008/input/input8

Aug 12 15:59:45 mm-ai-df142 kernel: [ 874.391556] hid-generic 0003:04D9:A0BE.0008: input,hidraw1: USB HID v1.11 Mouse [HID 04d9:a0be] on usb-0000:00:14.0-1/input1

Aug 12 16:00:26 mm-ai-df142 kernel: [ 915.228186] usb 1-1: USB disconnect, device number 6

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.487353] blk_update_request: I/O error, dev nvme0n1, sector 787107632

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.494103] Buffer I/O error on dev nvme0n1p1, logical block 98388198, lost async page write

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.502886] blk_update_request: I/O error, dev nvme0n1, sector 787107640

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.509626] Buffer I/O error on dev nvme0n1p1, logical block 98388199, lost async page write

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.518326] blk_update_request: I/O error, dev nvme0n1, sector 787107648

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.525060] Buffer I/O error on dev nvme0n1p1, logical block 98388200, lost async page write

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.533760] blk_update_request: I/O error, dev nvme0n1, sector 848517408

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.540492] Buffer I/O error on dev nvme0n1p1, logical block 106064420, lost async page write

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.549290] blk_update_request: I/O error, dev nvme0n1, sector 848517416

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.556022] Buffer I/O error on dev nvme0n1p1, logical block 106064421, lost async page write

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.564824] blk_update_request: I/O error, dev nvme0n1, sector 848517424

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.571563] Buffer I/O error on dev nvme0n1p1, logical block 106064422, lost async page write

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.580374] blk_update_request: I/O error, dev nvme0n1, sector 848517432

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.587114] Buffer I/O error on dev nvme0n1p1, logical block 106064423, lost async page write

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.595914] blk_update_request: I/O error, dev nvme0n1, sector 848518048

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.602649] Buffer I/O error on dev nvme0n1p1, logical block 106064500, lost async page write

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.611454] blk_update_request: I/O error, dev nvme0n1, sector 848518056

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.618188] Buffer I/O error on dev nvme0n1p1, logical block 106064501, lost async page write

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.627007] blk_update_request: I/O error, dev nvme0n1, sector 848518064

Aug 12 17:29:05 mm-ai-df142 kernel: [ 6234.633756] Buffer I/O error on dev nvme0n1p1, logical block 106064502, lost async page write

Aug 12 17:29:07 mm-ai-df142 kernel: [ 6236.670633] XFS (nvme0n1p1): metadata I/O error: block 0x5d295fa6 ("xlog_iodone") error 5 numblks 512

Aug 12 17:29:07 mm-ai-df142 kernel: [ 6236.679886] XFS (nvme0n1p1): xfs_do_force_shutdown(0x2) called from line 1197 of file /build/linux-MNTIf1/linux-4.4.0/fs/xfs/xfs_log.c. Return address = 0xffffffffc0647d68

Aug 12 17:29:07 mm-ai-df142 kernel: [ 6236.679931] XFS (nvme0n1p1): Log I/O Error Detected. Shutting down filesystem

Aug 12 17:29:07 mm-ai-df142 kernel: [ 6236.687184] XFS (nvme0n1p1): Please umount the filesystem and rectify the problem(s)

Aug 12 17:29:37 mm-ai-df142 kernel: [ 6266.750101] XFS (nvme0n1p1): xfs_log_force: error -5 returned.

Aug 12 17:30:07 mm-ai-df142 kernel: [ 6296.829614] XFS (nvme0n1p1): xfs_log_force: error -5 returned.

Aug 12 17:30:37 mm-ai-df142 kernel: [ 6326.909118] XFS (nvme0n1p1): xfs_log_force: error -5 returned.

Aug 12 17:31:07 mm-ai-df142 kernel: [ 6356.988617] XFS (nvme0n1p1): xfs_log_force: error -5 returned.

Aug 12 17:31:37 mm-ai-df142 kernel: [ 6387.068076] XFS (nvme0n1p1): xfs_log_force: error -5 returned.

Aug 12 17:32:08 mm-ai-df142 kernel: [ 6417.147559] XFS (nvme0n1p1): xfs_log_force: error -5 returned.

Aug 12 17:32:38 mm-ai-df142 kernel: [ 6447.227053] XFS (nvme0n1p1): xfs_log_force: error -5 returned.

Aug 12 17:33:08 mm-ai-df142 kernel: [ 6477.306532] XFS (nvme0n1p1): xfs_log_force: error -5 returned.

1 ACCEPTED SOLUTION

Santiago_A_Inte
Contributor III

Hello 3000022912991.565936085680946E12,

Thank you for posting in the Intel® SSD community on your request for support for your Intel® SSD DC P4610 Series (1.6TB, 2.5in PCIe 3.1 x4, 3D2, TLC) drive.

In order to further assist you regarding your inquiry related to your Intel® SSD DC P4610 Series. We will appreciate if you can provide us with the following information:

·        SSU logs, using the Intel® System Support Utility for the Linux* Operating System.

o   Go to https://downloadcenter.intel.com/download/26735/ and download the software.

o   When finished downloading it, open it.

o   Attach the log file obtained to your reply.

·        SMART logs extracted from your Intel® SSD DC P4610 drive.

Please use the Intel® SSD Data Center Tool (Intel® SSD DCT) can be used to read out the SMART attributes; to download this tool, please follow this link: https://downloadcenter.intel.com/download/28639/Intel-SSD-Data-Center-Tool-Intel-SSD-DCT-?product=35...

For further information on how to use this tool to extract the SMART logs, please check the User guide: https://www.intel.com/content/dam/support/us/en/documents/memory-and-storage/Intel_SSD_DCT_3_0_x_Use... go to page 25 section 2.1.3.

We will be looking forward to your reply.

Have a nice day.

Santiago A.

Intel® Customer Support Technician

Under Contract to Intel Corporation

View solution in original post

3 REPLIES 3

Santiago_A_Inte
Contributor III

Hello 3000022912991.565936085680946E12,

Thank you for posting in the Intel® SSD community on your request for support for your Intel® SSD DC P4610 Series (1.6TB, 2.5in PCIe 3.1 x4, 3D2, TLC) drive.

In order to further assist you regarding your inquiry related to your Intel® SSD DC P4610 Series. We will appreciate if you can provide us with the following information:

·        SSU logs, using the Intel® System Support Utility for the Linux* Operating System.

o   Go to https://downloadcenter.intel.com/download/26735/ and download the software.

o   When finished downloading it, open it.

o   Attach the log file obtained to your reply.

·        SMART logs extracted from your Intel® SSD DC P4610 drive.

Please use the Intel® SSD Data Center Tool (Intel® SSD DCT) can be used to read out the SMART attributes; to download this tool, please follow this link: https://downloadcenter.intel.com/download/28639/Intel-SSD-Data-Center-Tool-Intel-SSD-DCT-?product=35...

For further information on how to use this tool to extract the SMART logs, please check the User guide: https://www.intel.com/content/dam/support/us/en/documents/memory-and-storage/Intel_SSD_DCT_3_0_x_Use... go to page 25 section 2.1.3.

We will be looking forward to your reply.

Have a nice day.

Santiago A.

Intel® Customer Support Technician

Under Contract to Intel Corporation

Santiago_A_Inte
Contributor III

Hi 3000022912991.565936085680946E12,

Greetings from Intel® SSD communities support group.

This is a friendly reminder your case remains open, awaiting for your reply.

We will be looking forward to your reply.

Have a nice day.

Santiago A.

Intel® Customer Support Technician

A Contingent Worker at Intel

Santiago_A_Inte
Contributor III

Hi 3000022912991.565936085680946E12,

Greetings from Intel® SSD support group

This is to let you know, this case is being closed.

Please feel free to get back to Intel® communities, whenever you might feel necessary.

Have a nice day,

Santiago A.

Intel® Customer Support Technician

A Contingent Worker at Intel