February 6, 20197 yr Hi Guys, I have my Unraid mapped to my Windows 10 desktop. I can access all my folders from windows, and I could access my Samsung_SSD_960_EVO_250GB drive in the (M2 Slot) Now I can't, and the SSD is showing the following errors below. I have my dockers installed on this drive, obviously the dockers won't load. The drive seems to be in there fairly tight. This is also causing reboot issues. Can't shutdown unless I do a hard power down with the button. Drives only 6 months old. It looks more like a disconnection error, I don't know. I'm also having issues with the webui, just seems to hang there, pretty much have to shutdown and bootup to get back in. Any help is appreciated. Disk Log Info Feb 5 19:17:39 BadBoy kernel: nvme0n1: p1 Feb 5 19:17:39 BadBoy kernel: BTRFS: device fsid 70817376-1c3f-45f0-9fb7-55bdd47c560a devid 1 transid 2440087 /dev/nvme0n1p1 Feb 5 19:18:55 BadBoy emhttpd: Samsung_SSD_960_EVO_250GB_S3ESNX0K101752Y (nvme0n1) 512 488397168 Feb 5 19:19:05 BadBoy unassigned.devices: Adding disk '/dev/nvme0n1p1'... Feb 5 19:19:05 BadBoy unassigned.devices: Mount drive command: /sbin/mount -t btrfs -o auto,async,noatime,nodiratime '/dev/nvme0n1p1' '/mnt/disks/Samsung_SSD_960_EVO_250GB_S3ESNX0K101752Y' Feb 5 19:19:05 BadBoy kernel: BTRFS info (device nvme0n1p1): disk space caching is enabled Feb 5 19:19:05 BadBoy kernel: BTRFS info (device nvme0n1p1): has skinny extents Feb 5 19:19:05 BadBoy kernel: BTRFS info (device nvme0n1p1): enabling ssd optimizations Feb 5 19:19:05 BadBoy kernel: BTRFS info (device nvme0n1p1): checking UUID tree Feb 5 19:19:05 BadBoy unassigned.devices: Successfully mounted '/dev/nvme0n1p1' on '/mnt/disks/Samsung_SSD_960_EVO_250GB_S3ESNX0K101752Y'. Feb 5 19:22:14 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 12272224 Feb 5 19:22:14 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 13445896 Feb 5 19:22:14 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 13520632 Feb 5 19:22:14 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 13780936 Feb 5 19:24:04 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 98182760 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 98220272 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 395993536 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 395995072 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 395997632 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 395999168 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396001728 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396003264 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396005824 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 395990976 Feb 5 19:25:54 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 3249416 Feb 5 19:28:03 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 12293560 Feb 5 19:28:03 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396584672 Feb 5 19:28:03 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396587232 Feb 5 19:28:03 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396588768 Feb 5 19:28:03 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396591328 Feb 5 19:28:03 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396592864 Feb 5 19:28:03 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396595424 Feb 5 19:28:03 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396596960 Feb 5 19:28:03 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 396599520 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 288641792 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 288644352 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 98446792 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 397625680 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 397631312 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 397633872 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 397620040 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 397621112 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 397622176 Feb 5 19:29:57 BadBoy kernel: print_req_error: I/O error, dev nvme0n1, sector 397623120 Edited February 6, 20197 yr by Badboy
February 6, 20197 yr Community Expert I had to add a heatsink to the nvme drive on my desktop machine.
February 6, 20197 yr Author 19 hours ago, trurl said: I had to add a heatsink to the nvme drive on my desktop machine. Thanks for the reply Trurl. For some reason the drive is working. Don't ask me why...Lol I'm wondering if the USB is stating to go. I did push on it when I was putting something else in one of the other usb ports. Maybe somehow it was loose. I do think this drive is going bad. Still showing those errors in the disk logs. I checked while I was typing this. FYI: From what I was told the danger zone for the M2 drive is 68. Mine was at 44 so it wasn't heat related. Personally I think 44 is a little high.
February 6, 20197 yr Author 8 minutes ago, Badboy said: Thanks for the reply Trurl. For some reason the drive is working. Don't ask me why...Lol I'm wondering if the USB is stating to go. I did push on it when I was putting something else in one of the other usb ports. Maybe somehow it was loose. I do think this drive is going bad. Still showing those errors in the disk logs. I checked while I was typing this. FYI: From what I was told the danger zone for the M2 drive is 68. Mine was at 44 so it wasn't heat related. Personally I think 44 is a little high. Sorry, curious what brand did you buy? Looks like drive jumps from 30 to the 40s when it's being worked. Might go get a heatsink myself.
February 6, 20197 yr Community Expert My Samsung was the 950. It is my Windows OS drive. Before I put a heatsink on it would crash and the BIOS wouldn't find it to reboot until it had cooled. I have a very compact fanless PC though. Here is the heatsink I got: https://goo.gl/QxgV7D
February 7, 20197 yr Author 1 hour ago, trurl said: My Samsung was the 950. It is my Windows OS drive. Before I put a heatsink on it would crash and the BIOS wouldn't find it to reboot until it had cooled. I have a very compact fanless PC though. Here is the heatsink I got: https://goo.gl/QxgV7D Thanks, looks good.
Archived
This topic is now archived and is closed to further replies.