Solus installation live USB does not recognize/cannot use internal SSD

[vtcakavsmoace]

I'm attempting to install Solus onto a MacBook Pro "Core i5" 2.4 13" Late 2013 (model no. A1502). During the installation process, the installer informs me that there are no suitable disks to install to, despite the internal SSD having more than enough space to install to.

Not only does the installer not recognize the disk, but GParted also does not detect the disk. The disk is under /dev as sda, but is not located anywhere else.

This is the result of dmesg | grep "sd":

live@solus ~ $ dmesg | grep "sd"
[ 0.000000] ACPI: SSDT 0x000000008AD76000 000032 (v01 APPLE SsdtS3 00001000 INTL 20100915)
[ 3.501024] sd 1:0:0:0: [sda] Attached SCSI removable disk
[ 3.822432] sd 2:0:0:0: [sdb] 3891200 512-byte logical blocks: (1.99 GB/1.86 GiB)
[ 3.824216] sd 2:0:0:0: [sdb] Write Protect is off
[ 3.824219] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 3.825457] sd 2:0:0:0: [sdb] No Caching mode page found
[ 3.825479] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 3.833573] sdb: sdb1 sdb2
[ 3.839395] sd 2:0:0:0: [sdb] Attached SCSI removable disk

What other information should I post to help me solve this issue?

[sunnyflunk]

I'm attempting to install Solus onto a MacBook Pro "Core i5" 2.4 13" Late 2013 (model no. A1502). During the installation process, the installer informs me that there are no suitable disks to install to, despite the internal SSD having more than enough space to install to.

Not only does the installer not recognize the disk, but GParted also does not detect the disk. The disk is under /dev as sda, but is not located anywhere else.

This is the result of dmesg | grep "sd":

live@solus ~ $ dmesg | grep "sd"
[ 0.000000] ACPI: SSDT 0x000000008AD76000 000032 (v01 APPLE SsdtS3 00001000 INTL 20100915)
[ 3.501024] sd 1:0:0:0: [sda] Attached SCSI removable disk
[ 3.822432] sd 2:0:0:0: [sdb] 3891200 512-byte logical blocks: (1.99 GB/1.86 GiB)
[ 3.824216] sd 2:0:0:0: [sdb] Write Protect is off
[ 3.824219] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 3.825457] sd 2:0:0:0: [sdb] No Caching mode page found
[ 3.825479] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 3.833573] sdb: sdb1 sdb2
[ 3.839395] sd 2:0:0:0: [sdb] Attached SCSI removable disk

What other information should I post to help me solve this issue?

What's the output of

Code: Select all

lspci -v

[vtcakavsmoace]

This is the result of sudo lspci -v (removed irrelevant portions):

04:00.0 SATA controller: Marvell Technology Group Ltd. 88SS9183 PCIe SSD Controller (rev 14) (prog-if 01 [AHCI 1.0])
Subsystem: Marvell Technology Group Ltd. 88SS9183 PCIe SSD Controller
Flags: bus master, fast devsel, latency 0, IRQ 48
I/O ports at 2028 (size=8]
I/O ports at 2034 (size=4]
I/O ports at 2020 (size=8]
I/O ports at 2030 (size=4]
I/O ports at 2000 (size=32]
Memory at b0700000 (32-bit, non-prefetchable) (size=512]
Expansion ROM at b0720000 [disabled] (size=128K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Express Legacy Endpoint, MSI 00
Capabilities: [e0] SATA HBA v0.0
Kernel driver in use: ahci

I had to modify the bracketed portions in the output in order to post this, as size tags were being recognized unintentionally and I couldn't seem to escape the tag.

[vtcakavsmoace]

This is the changed text during dmesg -w when removing then re-adding ahci kernelmod through modprobe on Solus:

[ 224.122268] ahci 0000:04:00.0: version 3.0
[ 224.132862] ahci 0000:04:00.0: AHCI 0001.0000 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
[ 224.132866] ahci 0000:04:00.0: flags: 64bit ncq sntf led pio slum part
[ 224.133213] scsi host0: ahci
[ 224.133295] ata2: SATA max UDMA/133 abar m512@0xb0700000 port 0xb0700100 irq 47
[ 224.138368] DMAR: DRHD: handling fault status reg 2
[ 224.138372] DMAR: [DMA Write] Request device [04:00.1] fault addr fffa0000 [fault reason 02] Present bit in context entry is clear
[ 224.445451] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 224.445828] DMAR: DRHD: handling fault status reg 3
[ 224.445837] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[ 224.445845] DMAR: [DMA Write] Request device [04:00.1] fault addr fffa0000 [fault reason 02] Present bit in context entry is clear
[ 229.859447] DMAR: DRHD: handling fault status reg 2
[ 229.859461] DMAR: [DMA Write] Request device [04:00.1] fault addr fffa0000 [fault reason 02] Present bit in context entry is clear
[ 230.164725] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 230.165095] DMAR: DRHD: handling fault status reg 3
[ 230.165101] DMAR: [DMA Write] Request device [04:00.1] fault addr fffa0000 [fault reason 02] Present bit in context entry is clear
[ 230.165104] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[ 230.165145] ata2: limiting SATA link speed to 3.0 Gbps
[ 235.491211] DMAR: DRHD: handling fault status reg 2
[ 235.491226] DMAR: [DMA Write] Request device [04:00.1] fault addr fffa0000 [fault reason 02] Present bit in context entry is clear
[ 235.797120] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 235.797493] DMAR: DRHD: handling fault status reg 3
[ 235.797505] DMAR: [DMA Write] Request device [04:00.1] fault addr fffa0000 [fault reason 02] Present bit in context entry is clear
[ 235.797542] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[ 241.123047] DMAR: DRHD: handling fault status reg 2
[ 241.123061] DMAR: [DMA Write] Request device [04:00.1] fault addr fffa0000 [fault reason 02] Present bit in context entry is clear
[ 241.428839] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

Here it is again, but from a Ubuntu live USB:

[ 331.531504] ahci 0000:04:00.0: version 3.0
[ 331.541905] ahci 0000:04:00.0: AHCI 0001.0000 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
[ 331.541908] ahci 0000:04:00.0: flags: 64bit ncq sntf led pio slum part
[ 331.542318] scsi host0: ahci
[ 331.542534] ata2: SATA max UDMA/133 abar m512@0xb0700000 port 0xb0700100 irq 49
[ 331.858250] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 331.858926] ata2.00: unexpected _GTF length (8)
[ 331.859004] ata2.00: ATA-8: APPLE SSD SD0256F, A223321, max UDMA/133
[ 331.859008] ata2.00: 490234752 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[ 331.859886] ata2.00: unexpected _GTF length (8)
[ 331.860027] ata2.00: configured for UDMA/133
[ 331.860646] scsi 0:0:0:0: Direct-Access ATA APPLE SSD SD0256 321 PQ: 0 ANSI: 5
[ 331.902727] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 331.902773] sd 0:0:0:0: [sda] 490234752 512-byte logical blocks: (251 GB/234 GiB)
[ 331.902779] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 331.902806] sd 0:0:0:0: [sda] Write Protect is off
[ 331.902810] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 331.902875] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 331.905271] sda: sda1 sda2
[ 331.906308] sd 0:0:0:0: [sda] Attached SCSI disk

[vtcakavsmoace]

Also of note: since the time of original posting, I have established a GPT partition table and added a single ext4 partition to the SSD through GParted Live. I successfully installed Ubuntu Server 17.04 on the target SSD, then reformatted with GParted Live again. This seems to be a problem specific to Solus live USB, not to the disk.

[sunnyflunk]

Also of note: since the time of original posting, I have established a GPT partition table and added a single ext4 partition to the SSD through GParted Live. I successfully installed Ubuntu Server 17.04 on the target SSD, then reformatted with GParted Live again. This seems to be a problem specific to Solus live USB, not to the disk.

I see in the kernel it is listed under needing a workaround for it to function. From what I've seen, then most likely fix would be a newer kernel. It should be in time for the next ISO to provide the option for a more recent kernel with better hardware support.

[vtcakavsmoace]

Thanks. I'll update this thread on next release if it is resolved.

[Locinine]

Trying to install Solus Budgie on a Macbook Pro but I keep receiving the following error.

"Oh no! Your system has no usable disks available. There is nowhere to install Solus. Please ensure you have a minimum of 10GB available storage to complete a full Solus installation. "

I can boot into the live disk and receive this error once I try to install Solus onto my hard drive.

I noticed this discussion has died off but since no resolution has been found, hoping my comment may spur more discussion.

[schmoetz]

I have the same problem with my MacBook Air. Is there any solution available yet or is there a known workaround?

[brent]

Also of note: since the time of original posting, I have established a GPT partition table and added a single ext4 partition to the SSD through GParted Live. I successfully installed Ubuntu Server 17.04 on the target SSD, then reformatted with GParted Live again. This seems to be a problem specific to Solus live USB, not to the disk.

To the last two persons at the bottom of this post, this is spot on. It's not a Mac thing, and the last 15 words are accurate. It wasn't always this way during live install, it's recent. Learn Gparted. I ran into this problem, too. GPT then ext4. The OS snugged right in with success.