[SOLVED] Boot up problem [Crucial MX300 SSD]

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
MintWithaHole
Level 1
Level 1
Posts: 25
Joined: Fri May 18, 2012 9:32 am

[SOLVED] Boot up problem [Crucial MX300 SSD]

Postby MintWithaHole » Mon Jun 19, 2017 3:15 pm

One of the things that surprised me about Linux MINT was the amount of time it took to boot up. I have recently installed an SSD drive in my PC and am using that to boo operating systems from. Mint currently takes about 4-5 minutes to boot. Having disabled the splash screen, I have noticed the following error comes up at least twice, each time the PC pauses for maybe 40-50 seconds.

Does anyone know what this error means please?
Last edited by MintWithaHole on Mon Jul 10, 2017 6:49 pm, edited 2 times in total.

User avatar
austin.texas
Level 20
Level 20
Posts: 11696
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: Boot up problem

Postby austin.texas » Mon Jun 19, 2017 3:21 pm

What is the error message?
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2017

MintWithaHole
Level 1
Level 1
Posts: 25
Joined: Fri May 18, 2012 9:32 am

Re: Boot up problem

Postby MintWithaHole » Mon Jun 19, 2017 4:19 pm

Sorry, I did add an image but it has failed to appear. trying again...
Attachments
mint-boot-error3.jpg

User avatar
austin.texas
Level 20
Level 20
Posts: 11696
Joined: Tue Nov 17, 2009 3:57 pm
Location: at /home

Re: Boot up problem

Postby austin.texas » Mon Jun 19, 2017 5:20 pm

It is likely that you have a hardware problem.
Check all your SATA cable connections, and different SATA cables, if possible.
Run the memory check from the Grub menu. Let that run for a long time for the best results.
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2017

MintWithaHole
Level 1
Level 1
Posts: 25
Joined: Fri May 18, 2012 9:32 am

Re: Boot up problem

Postby MintWithaHole » Tue Jun 20, 2017 5:03 am

This morning I was able to obtain an IP address and connect to the network so I can post this directly. Its in the output from DMESG, and contains a bit more info:

[ 127.136992] ata5.00: failed command: READ FPDMA QUEUED
[ 127.137699] ata5.00: cmd 60/08:e8:60:28:cc/00:00:29:00:00/40 tag 29 ncq 4096 in
res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 127.139125] ata5.00: status: { DRDY }
[ 127.139829] ata5.00: failed command: READ FPDMA QUEUED
[ 127.140538] ata5.00: cmd 60/08:f0:68:28:cc/00:00:29:00:00/40 tag 30 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 127.141959] ata5.00: status: { DRDY }
[ 127.142673] ata5: hard resetting link
[ 127.634204] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 127.634560] ata5.00: supports DRM functions and may not be fully accessible
[ 127.635759] ata5.00: supports DRM functions and may not be fully accessible
[ 127.636623] ata5.00: configured for UDMA/133
[ 127.636657] ata5.00: device reported invalid CHS sector 0
[ 127.636659] ata5.00: device reported invalid CHS sector 0
[ 127.636661] ata5.00: device reported invalid CHS sector 0
.
.
.
[ 127.636663] ata5.00: device reported invalid CHS sector 0
[ 127.636665] ata5.00: device reported invalid CHS sector 0
[ 127.636689] sd 4:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 127.636693] sd 4:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] [descriptor]
[ 127.636697] sd 4:0:0:0: [sda] tag#0 Add. Sense: Unaligned write command
[ 127.636701] sd 4:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 29 cc 28 70 00 00 08 00
[ 127.636704] blk_update_request: I/O error, dev sda, sector 701245552
[ 127.637130] sd 4:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 127.637134] sd 4:0:0:0: [sda] tag#1 Sense Key : Illegal Request [current] [descriptor]
[ 127.637137] sd 4:0:0:0: [sda] tag#1 Add. Sense: Unaligned write command
[ 127.637140] sd 4:0:0:0: [sda] tag#1 CDB: Read(10) 28 00 29 cc 28 78 00 00 08 00
[ 127.637142] blk_update_request: I/O error, dev sda, sector 701245560
.
.
.
[ 199.047474] ata5.00: failed command: WRITE FPDMA QUEUED
[ 199.047479] ata5.00: cmd 61/08:88:c8:2b:cc/00:00:29:00:00/40 tag 17 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 199.047481] ata5.00: status: { DRDY }
[ 199.047485] ata5: hard resetting link
[ 199.539362] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 199.539644] ata5.00: supports DRM functions and may not be fully accessible
[ 199.540898] ata5.00: supports DRM functions and may not be fully accessible
[ 199.541761] ata5.00: configured for UDMA/133
[ 199.541765] ata5.00: device reported invalid CHS sector 0
[ 199.541768] ata5.00: device reported invalid CHS sector 0
[ 199.541770] ata5.00: device reported invalid CHS sector 0
[ 199.541772] ata5.00: device reported invalid CHS sector 0
[ 199.541774] ata5.00: device reported invalid CHS sector 0
[ 199.541776] ata5.00: device reported invalid CHS sector 0
[ 199.541778] ata5.00: device reported invalid CHS sector 0
[ 199.541785] ata5: EH complete
[ 199.542117] ata5.00: Enabling discard_zeroes_data


It finishes at this point. I have removed much of the superfluous repetition. This is a bit worrying since the device 'sda', specifically /dev/sda5 is on my new Crucial SSD drive. I don't know whether this makes a difference. In the meantime, I'm off to do the memory test from the GRUB menu and maybe order some replacement SATA cables. Thanks.

EDIT: I have just tried booting from Kali Linux live CD and then mounted /dev/sda5. I checked dmesg and there did not seem to be a problem with ata5:

root@kali:/media/root/USB# dmesg |grep ata5
[ 1.649776] ata5: SATA max UDMA/133 abar m512@0xf7100000 port 0xf7100100 irq 37
[ 2.127121] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.127498] ata5.00: supports DRM functions and may not be fully accessible
[ 2.128317] ata5.00: ATA-10: Crucial_CT525MX300SSD1, M0CR040, max UDMA/133
[ 2.128398] ata5.00: 1025610768 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 2.129206] ata5.00: supports DRM functions and may not be fully accessible
[ 2.130527] ata5.00: configured for UDMA/133
[ 2.517550] ata5.00: Enabling discard_zeroes_data
[ 2.517813] ata5.00: Enabling discard_zeroes_data
[ 2.518878] ata5.00: Enabling discard_zeroes_data


So now I am not so sure the problem is my hardware? Equally, Kali does not seem to have a problem with my mounting my NTFS volumes, neither /dev/sda1 and /dev/sda2 on the SSD, nor /dev/sdb3 which is on the hard drive. MINT does and refuses to mount them claiming they are corrupted. Windows would normally prompt for a chkdisk on boot-up if that were the case but it does not. This might possibly be a separate issue but I mention it here in case it is somehow related.

MintWithaHole
Level 1
Level 1
Posts: 25
Joined: Fri May 18, 2012 9:32 am

Re: Boot up problem

Postby MintWithaHole » Tue Jun 20, 2017 7:55 am

I have completed the memory tests as suggested and everything passed OK. I had to reduce the size of the image and greyscale it in order to make it small enough to upload. 100kb is very limiting!
Attachments
memtests.jpg

MintWithaHole
Level 1
Level 1
Posts: 25
Joined: Fri May 18, 2012 9:32 am

Re: Boot up problem

Postby MintWithaHole » Thu Jun 29, 2017 8:20 am

Just to update, I purchased genuine Asus 6Gbit cables and received and installed them today. In the meantime, I also upgraded the SSD drive firmware. I checked the motherboard (Asus P8H61-M Pro) firmware as well and it is already up to the latest available version. Although I get the impression that boot-up is a bit quicker, I am still getting some errors. I saved the output of dmesg to a file (dmesg.txt) but the forum would not allow me to upload it - apparently .txt files are not allowed? I have therefore pasted the relevant bit here:

[ 39.031756] ata5.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
[ 39.031901] ata5.00: failed command: READ FPDMA QUEUED
[ 39.032142] ata5.00: cmd 60/20:00:e0:f3:54/00:00:28:00:00/40 tag 0 ncq 16384 in
res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 39.033343] ata5.00: status: { DRDY }
[ 39.033939] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.034522] ata5.00: cmd 61/08:08:28:10:4c/00:00:1d:00:00/40 tag 1 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.035713] ata5.00: status: { DRDY }
[ 39.036300] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.036900] ata5.00: cmd 61/08:10:08:31:4c/00:00:1d:00:00/40 tag 2 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.038112] ata5.00: status: { DRDY }
[ 39.038729] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.039337] ata5.00: cmd 61/08:18:b0:15:0c/00:00:1e:00:00/40 tag 3 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.040569] ata5.00: status: { DRDY }
[ 39.041188] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.041804] ata5.00: cmd 61/08:20:08:11:8c/00:00:1e:00:00/40 tag 4 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.043058] ata5.00: status: { DRDY }
[ 39.043687] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.044311] ata5.00: cmd 61/10:28:40:11:8c/00:00:1e:00:00/40 tag 5 ncq 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.045591] ata5.00: status: { DRDY }
[ 39.046235] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.046869] ata5.00: cmd 61/08:30:b0:11:8c/00:00:1e:00:00/40 tag 6 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.048132] ata5.00: status: { DRDY }
[ 39.048774] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.049412] ata5.00: cmd 61/08:38:c0:11:8c/00:00:1e:00:00/40 tag 7 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.050716] ata5.00: status: { DRDY }
[ 39.051369] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.052019] ata5.00: cmd 61/10:40:40:12:8c/00:00:1e:00:00/40 tag 8 ncq 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.053331] ata5.00: status: { DRDY }
[ 39.053982] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.054637] ata5.00: cmd 61/08:48:20:13:8c/00:00:1e:00:00/40 tag 9 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.055979] ata5.00: status: { DRDY }
[ 39.056653] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.057317] ata5.00: cmd 61/08:50:30:13:8c/00:00:1e:00:00/40 tag 10 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.058661] ata5.00: status: { DRDY }
[ 39.059332] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.060004] ata5.00: cmd 61/20:58:48:13:8c/00:00:1e:00:00/40 tag 11 ncq 16384 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.061351] ata5.00: status: { DRDY }
[ 39.062030] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.062696] ata5.00: cmd 61/08:60:b8:14:8c/00:00:1e:00:00/40 tag 12 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.064075] ata5.00: status: { DRDY }
[ 39.064769] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.065463] ata5.00: cmd 61/10:68:28:15:8c/00:00:1e:00:00/40 tag 13 ncq 8192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.066870] ata5.00: status: { DRDY }
[ 39.067577] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.068283] ata5.00: cmd 61/08:70:58:15:8c/00:00:1e:00:00/40 tag 14 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.069715] ata5.00: status: { DRDY }
[ 39.070433] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.071143] ata5.00: cmd 61/08:78:e0:15:8c/00:00:1e:00:00/40 tag 15 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.072581] ata5.00: status: { DRDY }
[ 39.073293] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.074035] ata5.00: cmd 61/08:80:58:17:8c/00:00:1e:00:00/40 tag 16 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.075439] ata5.00: status: { DRDY }
[ 39.076153] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.076856] ata5.00: cmd 61/08:88:90:17:8c/00:00:1e:00:00/40 tag 17 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.078285] ata5.00: status: { DRDY }
[ 39.078996] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.079705] ata5.00: cmd 61/08:90:08:11:8c/00:00:1f:00:00/40 tag 18 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.081158] ata5.00: status: { DRDY }
[ 39.081848] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.082560] ata5.00: cmd 61/08:98:e0:13:8c/00:00:1f:00:00/40 tag 19 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.084016] ata5.00: status: { DRDY }
[ 39.084703] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.085408] ata5.00: cmd 61/30:a0:30:14:8c/00:00:1f:00:00/40 tag 20 ncq 24576 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.086846] ata5.00: status: { DRDY }
[ 39.087562] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.088274] ata5.00: cmd 61/08:a8:f8:14:8c/00:00:1f:00:00/40 tag 21 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.089715] ata5.00: status: { DRDY }
[ 39.090432] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.091143] ata5.00: cmd 61/08:b0:90:15:8c/00:00:1f:00:00/40 tag 22 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.092615] ata5.00: status: { DRDY }
[ 39.093306] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.094024] ata5.00: cmd 61/08:b8:68:16:8c/00:00:1f:00:00/40 tag 23 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.095490] ata5.00: status: { DRDY }
[ 39.096186] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.096899] ata5.00: cmd 61/08:c0:a8:16:8c/00:00:1f:00:00/40 tag 24 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.098347] ata5.00: status: { DRDY }
[ 39.099070] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.099788] ata5.00: cmd 61/08:c8:08:17:8c/00:00:1f:00:00/40 tag 25 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.101239] ata5.00: status: { DRDY }
[ 39.101960] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.102682] ata5.00: cmd 61/08:d0:78:18:8c/00:00:1f:00:00/40 tag 26 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 39.104134] ata5.00: status: { DRDY }
[ 39.104854] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.105575] ata5.00: cmd 61/08:d8:a0:18:8c/00:00:1f:00:00/40 tag 27 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.107030] ata5.00: status: { DRDY }
[ 39.107757] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.108469] ata5.00: cmd 61/08:e0:10:19:8c/00:00:1f:00:00/40 tag 28 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.109920] ata5.00: status: { DRDY }
[ 39.110644] ata5.00: failed command: WRITE FPDMA QUEUED
[ 39.111361] ata5.00: cmd 61/08:e8:d0:19:8c/00:00:1f:00:00/40 tag 29 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.112842] ata5.00: status: { DRDY }
[ 39.113539] ata5.00: failed command: SEND FPDMA QUEUED
[ 39.114252] ata5.00: cmd 64/01:f0:00:00:00/00:00:00:00:00/a0 tag 30 ncq 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 39.115704] ata5.00: status: { DRDY }
[ 39.116421] ata5: hard resetting link
[ 39.607661] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 39.607929] ata5.00: supports DRM functions and may not be fully accessible
[ 39.609160] ata5.00: supports DRM functions and may not be fully accessible
[ 39.610020] ata5.00: configured for UDMA/133
[ 39.610025] ata5.00: device reported invalid CHS sector 0
[ 39.610027] ata5.00: device reported invalid CHS sector 0
[ 39.610029] ata5.00: device reported invalid CHS sector 0
[ 39.610031] ata5.00: device reported invalid CHS sector 0
[ 39.610033] ata5.00: device reported invalid CHS sector 0
[ 39.610035] ata5.00: device reported invalid CHS sector 0
[ 39.610037] ata5.00: device reported invalid CHS sector 0
[ 39.610039] ata5.00: device reported invalid CHS sector 0
[ 39.610041] ata5.00: device reported invalid CHS sector 0
[ 39.610043] ata5.00: device reported invalid CHS sector 0
[ 39.610045] ata5.00: device reported invalid CHS sector 0
[ 39.610047] ata5.00: device reported invalid CHS sector 0
[ 39.610049] ata5.00: device reported invalid CHS sector 0
[ 39.610051] ata5.00: device reported invalid CHS sector 0
[ 39.610053] ata5.00: device reported invalid CHS sector 0
[ 39.610055] ata5.00: device reported invalid CHS sector 0
[ 39.610057] ata5.00: device reported invalid CHS sector 0
[ 39.610059] ata5.00: device reported invalid CHS sector 0
[ 39.610061] ata5.00: device reported invalid CHS sector 0
[ 39.610063] ata5.00: device reported invalid CHS sector 0
[ 39.610065] ata5.00: device reported invalid CHS sector 0
[ 39.610067] ata5.00: device reported invalid CHS sector 0
[ 39.610069] ata5.00: device reported invalid CHS sector 0
[ 39.610071] ata5.00: device reported invalid CHS sector 0
[ 39.610073] ata5.00: device reported invalid CHS sector 0
[ 39.610075] ata5.00: device reported invalid CHS sector 0
[ 39.610077] ata5.00: device reported invalid CHS sector 0
[ 39.610091] ata5: EH complete
[ 39.610155] ata5.00: Enabling discard_zeroes_data
[ 39.623356] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[ 39.625669] vboxdrv: Found 8 processor cores
[ 39.644108] vboxdrv: TSC mode is Invariant, tentative frequency 3391436426 Hz
[ 39.644109] vboxdrv: Successfully loaded version 5.0.40_Ubuntu (interface 0x00240000)
[ 39.647523] VBoxNetFlt: Successfully started.
[ 39.650016] VBoxNetAdp: Successfully started.
[ 39.652752] VBoxPciLinuxInit
[ 39.654210] vboxpci: IOMMU not found (not registered)
[ 75.043538] ata5.00: exception Emask 0x0 SAct 0x7c0000 SErr 0x0 action 0x6 frozen
[ 75.043545] ata5.00: failed command: SEND FPDMA QUEUED
[ 75.043552] ata5.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 75.043555] ata5.00: status: { DRDY }
[ 75.043558] ata5.00: failed command: READ FPDMA QUEUED
[ 75.043563] ata5.00: cmd 60/20:98:f0:10:d4/00:00:27:00:00/40 tag 19 ncq 16384 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 75.043566] ata5.00: status: { DRDY }
[ 75.043568] ata5.00: failed command: WRITE FPDMA QUEUED
[ 75.043573] ata5.00: cmd 61/e8:a0:c8:3d:4d/00:00:1d:00:00/40 tag 20 ncq 118784 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 75.043576] ata5.00: status: { DRDY }
[ 75.043578] ata5.00: failed command: WRITE FPDMA QUEUED
[ 75.043583] ata5.00: cmd 61/08:a8:e0:b6:15/00:00:2a:00:00/40 tag 21 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 75.043585] ata5.00: status: { DRDY }
[ 75.043587] ata5.00: failed command: WRITE FPDMA QUEUED
[ 75.043592] ata5.00: cmd 61/08:b0:a8:3a:94/00:00:2a:00:00/40 tag 22 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 75.043595] ata5.00: status: { DRDY }
[ 75.043599] ata5: hard resetting link
[ 75.535509] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 75.535875] ata5.00: supports DRM functions and may not be fully accessible
[ 75.537135] ata5.00: supports DRM functions and may not be fully accessible
[ 75.538005] ata5.00: configured for UDMA/133
[ 75.538009] ata5.00: device reported invalid CHS sector 0
[ 75.538012] ata5.00: device reported invalid CHS sector 0
[ 75.538022] ata5.00: device reported invalid CHS sector 0
[ 75.538024] ata5.00: device reported invalid CHS sector 0
[ 75.538026] ata5.00: device reported invalid CHS sector 0
[ 75.538033] ata5: EH complete
[ 75.538062] ata5.00: Enabling discard_zeroes_data
[ 106.059401] ata5.00: exception Emask 0x0 SAct 0x1c000000 SErr 0x0 action 0x6 frozen
[ 106.059408] ata5.00: failed command: WRITE FPDMA QUEUED
[ 106.059415] ata5.00: cmd 61/e8:d0:c8:3d:4d/00:00:1d:00:00/40 tag 26 ncq 118784 out
res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 106.059417] ata5.00: status: { DRDY }
[ 106.059420] ata5.00: failed command: READ FPDMA QUEUED
[ 106.059425] ata5.00: cmd 60/20:d8:f0:10:d4/00:00:27:00:00/40 tag 27 ncq 16384 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 106.059428] ata5.00: status: { DRDY }
[ 106.059430] ata5.00: failed command: SEND FPDMA QUEUED
[ 106.059435] ata5.00: cmd 64/01:e0:00:00:00/00:00:00:00:00/a0 tag 28 ncq 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 106.059438] ata5.00: status: { DRDY }
[ 106.059442] ata5: hard resetting link
[ 106.551378] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 106.551649] ata5.00: supports DRM functions and may not be fully accessible
[ 106.590945] ata5.00: supports DRM functions and may not be fully accessible
[ 106.591884] ata5.00: configured for UDMA/133
[ 106.591891] ata5.00: device reported invalid CHS sector 0
[ 106.591894] ata5.00: device reported invalid CHS sector 0
[ 106.591902] ata5: EH complete
[ 106.591938] ata5.00: Enabling discard_zeroes_data
[ 149.067214] ata5.00: NCQ disabled due to excessive errors
[ 149.067220] ata5.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x6 frozen
[ 149.067224] ata5.00: failed command: SEND FPDMA QUEUED
[ 149.067231] ata5.00: cmd 64/01:20:00:00:00/00:00:00:00:00/a0 tag 4 ncq 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 149.067234] ata5.00: status: { DRDY }
[ 149.067239] ata5: hard resetting link
[ 149.559194] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 149.559571] ata5.00: supports DRM functions and may not be fully accessible
[ 149.560850] ata5.00: supports DRM functions and may not be fully accessible
[ 149.561721] ata5.00: configured for UDMA/133
[ 149.561729] ata5: EH complete
[ 149.561764] ata5.00: Enabling discard_zeroes_data

FreedomTruth
Level 4
Level 4
Posts: 315
Joined: Fri Sep 23, 2016 10:19 am

Re: Boot up problem

Postby FreedomTruth » Thu Jun 29, 2017 1:25 pm

MintWithaHole wrote:EDIT: I have just tried booting from Kali Linux live CD and then mounted /dev/sda5. I checked dmesg and there did not seem to be a problem with ata5:
So now I am not so sure the problem is my hardware? Equally, Kali does not seem to have a problem with my mounting my NTFS volumes, neither /dev/sda1 and /dev/sda2 on the SSD, nor /dev/sdb3 which is on the hard drive. MINT does and refuses to mount them claiming they are corrupted. Windows would normally prompt for a chkdisk on boot-up if that were the case but it does not. This might possibly be a separate issue but I mention it here in case it is somehow related.
I am not sure what is the difference in how kali and mint handle these things. What is the kernel version on kali, and what is your kernel version on mint? uname -a should give that information. Just maybe its something that is fixed in a newer kernel than you are using on mint? It's a long shot, but maybe. Gotta admit, it sounds more like bad cable or bad drive, but if it works in other OS that would seem to rule out the hardware.

Also, from looking at your motherboard (your memtest screenshot shows Asus P8H61-M PRO) your drives are probably plugged in the navy blue sata ports (asmedia asm1061 6gbps)? Just for troubleshooting, try to plug them in the light blue sata ports (intel h61b3 3gbps) and see if mint plays better with that. Or if they happen to be in the light blue now, switch them to the navy blue, which should perform better anyway.
If you abide in My word, you are My disciples indeed. And you shall know the truth, and the truth shall make you free... Most assuredly, I say to you, whoever commits sin is a slave of sin... Therefore if the Son makes you free, you shall be free indeed.

MintWithaHole
Level 1
Level 1
Posts: 25
Joined: Fri May 18, 2012 9:32 am

Re: Boot up problem

Postby MintWithaHole » Fri Jun 30, 2017 2:36 pm

The Kali issue might be a red herring to a degree. I was testing Kali by booting from the a LiveCD, but when I installed it to a spare partition on the same SSD I had the same problem, just not quite so many messages. It obviously had no problem with the DVD drive but it does with the SSD.

I have both SSD and HDD plugged into the dark navy blue slots. I have now tried swapping them around as well as leaving the HDD unplugged (had to comment it out in fstab for Mint to boot). I will now try your suggestion with the SSD plugged into the light blue connector, although obviously I this limits the speed to 3Gb, but it would be interesting to see whether it plays any better.

MintWithaHole
Level 1
Level 1
Posts: 25
Joined: Fri May 18, 2012 9:32 am

Re: Boot up problem

Postby MintWithaHole » Mon Jul 03, 2017 11:04 am

I tried out the suggestion to put both drives into the light blue connectors. I took care to ensure that the devices were in the same order on the controller (/dev/sda, /dev/sdb) and re-booted. Booting into Mint took just a few seconds compared to the previous 4-5mins as did booting into Debian. Even Win10 seemed to boot a little quicker. I am still getting some errors but a bit different this time (see below) and am not sure whether these still relate to the SATA controller. I then re-instated the drives back into the original ports and we are back to the original behaviour. Clearly then, there is some issue with using the 6gbit ports. Yet, the manufacturer (Crucial) states that the drive is compatible with this m/board so I'm not sure what to do next. I have been in touch with them but after doing a couple of tests they suggested that as the firmware of the drive and the m/board is at the latest revision that the issue must be with the drivers. The bottom line is I have a m/board with 6gbit ports but have to run the drives at 3gbit? I am wondering whether to return the SSD to Amazon and get something from another manufacturer.

[ 3.696435] systemd-journald[380]: Received request to flush runtime journal from PID 1
[ 3.704635] lp0: using parport0 (interrupt-driven).
[ 3.757632] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150930/utaddress-254)
[ 3.757639] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.757642] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150930/utaddress-254)
[ 3.757646] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150930/utaddress-254)
[ 3.757650] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.757651] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150930/utaddress-254)
[ 3.757655] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150930/utaddress-254)
[ 3.757658] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.757660] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150930/utaddress-254)
[ 3.757663] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB_.PCI0.LPCB.GPBX) (20150930/utaddress-254)
[ 3.757667] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000050F (\_GPE.GPIO) (20150930/utaddress-254)
[ 3.757670] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

User avatar
Spearmint2
Level 14
Level 14
Posts: 5061
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Boot up problem

Postby Spearmint2 » Mon Jul 03, 2017 12:06 pm

MintWithaHole wrote:I tried out the suggestion to put both drives into the light blue connectors. I took care to ensure that the devices were in the same order on the controller (/dev/sda, /dev/sdb) and re-booted. Booting into Mint took just a few seconds compared to the previous 4-5mins as did booting into Debian. Even Win10 seemed to boot a little quicker. I am still getting some errors but a bit different this time (see below) and am not sure whether these still relate to the SATA controller. I then re-instated the drives back into the original ports and we are back to the original behaviour. Clearly then, there is some issue with using the 6gbit ports. Yet, the manufacturer (Crucial) states that the drive is compatible with this m/board so I'm not sure what to do next. I have been in touch with them but after doing a couple of tests they suggested that as the firmware of the drive and the m/board is at the latest revision that the issue must be with the drivers. The bottom line is I have a m/board with 6gbit ports but have to run the drives at 3gbit? I am wondering whether to return the SSD to Amazon and get something from another manufacturer.


https://en.wikipedia.org/wiki/Master_boot_record

https://superuser.com/questions/974952/ ... -and-not-0

I found this part below VERY interesting. On a standard HDD I'd consider that evidence the drive was dying, but not sure if it applies to SDD's. Also would note that mounting a drive is not the same as "using" that drive for reading from, nor writing to. As you discovered, once you actually started using it with the same alternate system, the problems returned. Keep your proof, send it along with the RMA on the drive.



Code: Select all

[ 39.610025] ata5.00: device reported invalid CHS sector 0
[ 39.610027] ata5.00: device reported invalid CHS sector 0
[ 39.610029] ata5.00: device reported invalid CHS sector 0
[ 39.610031] ata5.00: device reported invalid CHS sector 0
[ 39.610033] ata5.00: device reported invalid CHS sector 0
[ 39.610035] ata5.00: device reported invalid CHS sector 0
[ 39.610037] ata5.00: device reported invalid CHS sector 0
[ 39.610039] ata5.00: device reported invalid CHS sector 0
[ 39.610041] ata5.00: device reported invalid CHS sector 0
[ 39.610043] ata5.00: device reported invalid CHS sector 0
[ 39.610045] ata5.00: device reported invalid CHS sector 0
[ 39.610047] ata5.00: device reported invalid CHS sector 0
[ 39.610049] ata5.00: device reported invalid CHS sector 0
[ 39.610051] ata5.00: device reported invalid CHS sector 0
[ 39.610053] ata5.00: device reported invalid CHS sector 0
[ 39.610055] ata5.00: device reported invalid CHS sector 0
[ 39.610057] ata5.00: device reported invalid CHS sector 0
[ 39.610059] ata5.00: device reported invalid CHS sector 0
[ 39.610061] ata5.00: device reported invalid CHS sector 0
[ 39.610063] ata5.00: device reported invalid CHS sector 0
[ 39.610065] ata5.00: device reported invalid CHS sector 0
[ 39.610067] ata5.00: device reported invalid CHS sector 0
[ 39.610069] ata5.00: device reported invalid CHS sector 0
[ 39.610071] ata5.00: device reported invalid CHS sector 0
[ 39.610073] ata5.00: device reported invalid CHS sector 0
[ 39.610075] ata5.00: device reported invalid CHS sector 0
[ 39.610077] ata5.00: device reported invalid CHS sector 0


other possibilities, but don't address the CHS sector zero errors.

https://askubuntu.com/questions/133946/ ... -dangerous

https://superuser.com/questions/438998/ ... rive-dying

Hopefully you don't have one of those junk Logisys PSU or something similar.
Read these 9-10 pages on Logisys, because it gives good information also on why cheap PSU can cause such
problems, even damaging drives and RAM. If the "ripple" (excess frequency) is too great in the rectified (from AC) DC power from the PSU, it can cause all sorts
of problems. Scroll past the distracting ads at end of each page section.

http://www.hardwaresecrets.com/logisys- ... ly-review/

general knowledge about PSU
http://www.hardwaresecrets.com/anatomy- ... -supplies/
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

MintWithaHole
Level 1
Level 1
Posts: 25
Joined: Fri May 18, 2012 9:32 am

Re: Boot up problem

Postby MintWithaHole » Tue Jul 04, 2017 4:29 am

The PSU is a 500W Corsair. Not sure how they rate is terms of supply quality.

Those CHS sector errors do not appear when the SSD is connected to a 3gbit (light blue - i.e Intel) interface. The errors appear only when the SSD is connected to the ASMedia 1062 6gbit interface. I did see a comment that swapping the SSD drive from Crucial to another vendor solved the problem for at least one individual so I am considering returning the drive. In the meantime I am running it on the 3gb port and everything is so much faster.

This is what it looks like when running on the 3gbit Intel port:

[ 1.064365] scsi host0: ahci
[ 1.064559] scsi host1: ahci
[ 1.064727] scsi host2: ahci
[ 1.064866] scsi host3: ahci
[ 1.064973] scsi host4: ahci
[ 1.065070] scsi host5: ahci
[ 1.065102] ata1: SATA max UDMA/133 abar m2048@0xf7306000 port 0xf7306100 irq 34
[ 1.065107] ata2: SATA max UDMA/133 abar m2048@0xf7306000 port 0xf7306180 irq 34
[ 1.065111] ata3: DUMMY
[ 1.065113] ata4: DUMMY
[ 1.065115] ata5: DUMMY
[ 1.065120] ata6: SATA max UDMA/133 abar m2048@0xf7306000 port 0xf7306380 irq 34

[ 1.065375] ahci 0000:05:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[ 1.065380] ahci 0000:05:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs
[ 1.065632] scsi host6: ahci
[ 1.065725] scsi host7: ahci
[ 1.065758] ata7: SATA max UDMA/133 abar m512@0xf7100000 port 0xf7100100 irq 37
[ 1.065765] ata8: SATA max UDMA/133 abar m512@0xf7100000 port 0xf7100180 irq 37

[ 1.383804] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.383807] ata7: SATA link down (SStatus 0 SControl 300)
[ 1.383848] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.383893] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

[ 1.384070] ata1.00: supports DRM functions and may not be fully accessible

[ 1.384489] ata1.00: ATA-10: Crucial_CT525MX300SSD1, M0CR050, max UDMA/133
[ 1.384494] ata1.00: 1025610768 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.384530] ata2.00: ATA-9: WDC WD10EZEX-00BN5A0, 01.01A01, max UDMA/133
[ 1.384534] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA

[ 1.385365] ata1.00: supports DRM functions and may not be fully accessible
[ 1.386289] ata1.00: configured for UDMA/133

[ 1.386364] ata6.00: ATAPI: ATAPI iHAS122, ZL0E, max UDMA/100
[ 1.386552] scsi 0:0:0:0: Direct-Access ATA Crucial_CT525MX3 R050 PQ: 0 ANSI: 5
[ 1.386855] ata1.00: Enabling discard_zeroes_data
[ 1.386873] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.386880] sd 0:0:0:0: [sda] 1025610768 512-byte logical blocks: (525 GB/489 GiB)
[ 1.387082] sd 0:0:0:0: [sda] Write Protect is off
[ 1.387090] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.387141] scsi 1:0:0:0: Direct-Access ATA WDC WD10EZEX-00B 1A01 PQ: 0 ANSI: 5

[ 1.387147] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 1.387155] ata6.00: configured for UDMA/100
[ 1.387257] ata1.00: Enabling discard_zeroes_data
[ 1.387343] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 1.387352] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[ 1.387391] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 1.387399] sd 1:0:0:0: [sdb] Write Protect is off
[ 1.387403] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.387419] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.388073] sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 >
[ 1.388378] ata1.00: Enabling discard_zeroes_data
[ 1.388552] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.389117] scsi 5:0:0:0: CD-ROM ATAPI iHAS122 ZL0E PQ: 0 ANSI: 5
[ 1.398995] sdb: sdb1 sdb2 sdb3
[ 1.399403] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 1.408557] sr 5:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[ 1.408563] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 1.408658] sr 5:0:0:0: Attached scsi CD-ROM sr0
[ 1.408792] sr 5:0:0:0: Attached scsi generic sg2 type 5

[ 1.727760] ata8: SATA link down (SStatus 0 SControl 300)


Even at the 3gbit speed I can see a dramatic difference in boot up time. When the SSD is connected to the 6bit port there is practically no difference. I'm not sure what ata7 and ata8 are as there are only 6 SATA connectors.

BTW, How does one measure the actual throughput (on Linux)?

EDIT: I have requested an RMA for the Crucial SSD drive and ordered a Samsung 850 EVO. Will update the thread when it arrives.

User avatar
Spearmint2
Level 14
Level 14
Posts: 5061
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Boot up problem

Postby Spearmint2 » Tue Jul 04, 2017 11:14 am

BTW, How does one measure the actual throughput (on Linux)?


I don't know.

I do know you can find files of various exact sizes for testing transfer rates, often used for testing USB flashdrives.

One way I did test such was using the dd command since it gives information when finished for how much data was transferred and the amount of time it took, so rates can be done then by calculator.

Here's a google with some pages on using dd to measure transfer rates.
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

MintWithaHole
Level 1
Level 1
Posts: 25
Joined: Fri May 18, 2012 9:32 am

[SOLVED] Re: Boot up problem [Crucial MX300 SSD]

Postby MintWithaHole » Mon Jul 10, 2017 6:38 pm

Problem solved - it was a compatibility issue! I returned the Crucial SSD drive last week and in its place purchased a Samsung EVO 850. This EVO850 drive has slightly less capacity then the Crucial (500GB vs 525GB), but those errors no longer appear when booting into MINT with the new SSD drive connected to the 6GB interface. Boot-up speed is impressively fast.

Dmesg just reports as follows:

[ 1.559834] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.561359] ata7.00: supports DRM functions and may not be fully accessible
[ 1.561638] ata7.00: disabling queued TRIM support
[ 1.561640] ata7.00: ATA-9: Samsung SSD 850 EVO 500GB, EMT02B6Q, max UDMA/133
[ 1.561644] ata7.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[ 1.562299] ata7.00: supports DRM functions and may not be fully accessible
[ 1.562535] ata7.00: disabling queued TRIM support
[ 1.562891] ata7.00: configured for UDMA/133
[ 1.563136] scsi 6:0:0:0: Direct-Access ATA Samsung SSD 850 2B6Q PQ: 0 ANSI: 5
[ 1.563450] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 1.563469] sd 6:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 1.563786] sd 6:0:0:0: [sda] Write Protect is off
[ 1.563791] sd 6:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.563910] sd 6:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.564852] sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 >
[ 1.565411] sd 6:0:0:0: [sda] Attached SCSI disk


I post the solution in the hope that this might help someone else having this problem. Its also worth having a look at this thread:

https://bbs.archlinux.org/viewtopic.php?id=218390

The author of that thread also had the same error and eventually replaced their Crucial MX300 drive with an Intel one and found that it also solved their problem. This would seem to further support the view that despite the vendor claiming full compatibility, there is a firmware/compatibility issue with the Crucial MX300 SSD drives and some motherboards.

ginahoy
Level 3
Level 3
Posts: 122
Joined: Sun May 28, 2017 3:15 pm

Re: [SOLVED] Re: Boot up problem [Crucial MX300 SSD]

Postby ginahoy » Sat Jul 22, 2017 2:46 am

MintWithaHole wrote:his would seem to further support the view that despite the vendor claiming full compatibility, there is a firmware/compatibility issue with the Crucial MX300 SSD drives and some motherboards.

You mentioned Win10. Sounds like Win10 was installed on the MX300. Did you experience errors/delays boot Win10 with MX300 connected to SATA III ports (6gb)? I'm just trying to make sure this wasn't a Linux compatibility issue, as I'm considering an MX300 for my new machine, which I will be building. Being that this will be my first experience with Linux, I don't want to invite disaster :wink:
Linux Mint 18.2 Xfce x64 | ASRock Z270 Extreme4 | Core i7 7700K | Cryorig H7 cooler| 32GB DDR4 2400| modded legacy Evercase LE4252 | EVGA 450W B3 | Samsung 850 EVO SSD


Return to “Installation & Boot”

Who is online

Users browsing this forum: adrianmdi and 15 guests