Re: [DNG] ultrabook boot issues - hybrid hard disk

2021-10-18 Thread Olaf Meeuwissen via Dng
Hi Riccardo,

Riccardo Mottola via Dng writes:

> I have installed Chimaera on my Ultrabook - first as beta, then
> upgraded constantly.  The system has a dual-disk setup under windows
> called smart cache or fast cache.  One spinning rust and one smaller
> SSD. ON windows the two drives are one as one with a cache.

That sounds a lot like my Dell Vostro 3360 at the office, apart from the
fact that it doesn't have Windows (anymore, I zeroed both disks ;-).

> Actually, when installing linux, they are seen as two drives, sda and
> sdb. I thought, originally, to install on the SSD disk so to have a
> fast boot system and the rest of apps and user directories on spinning
> rust. However, I could not even partition the SSD, it always gave
> errors. SO I installed everything on sda. I had delays at boot
> however, later.

I vaguely remember something about not being able to "use" my SSD but
forgot the details.  Whatever they were, letting

  dd if=/dev/zero of=/dev/sdb bs=4M

run until it complained about no disk space left fixed it for me.

Of course, if you want to keep that other OS around, that's not really
an option but I thought I'd mention it anyway.

Just a thought, I may also have fiddled with the BIOS to make it boot
from the SSD before trying the HDD and made sure I installed GRUB in
the MBR of the SSD.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] ultrabook boot issues - hybrid hard disk

2021-10-15 Thread Riccardo Mottola via Dng

Hi,

I have installed Chimaera on my Ultrabook - first as beta, then 
upgraded constantly.
The system has a dual-disk setup under windows called smart cache or 
fast cache.
One spinning rust and one smaller SSD. ON windows the two drives are 
one as one with a cache.


Actually, when installing linux, they are seen as two drives, sda and 
sdb. I thought, originally, to install on the SSD disk so to have a 
fast boot system and the rest of apps and user directories on spinning 
rust. However, I could not even partition the SSD, it always gave 
errors. SO I installed everything on sda. I had delays at boot 
however, later.


Now, with the latest kernel upgrade the delays became quite unbearable.

First.. can I stop this? maybe disabling or tweaking some setting?
Second, can this SSD disk actually be used? 32gb should be plenty for 
kernels boot and core system!


[1.642710] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[1.642750] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[1.643105] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE 
LOCK) filtered out
[1.643572] ata2.00: ATA-9: SanDisk SSD i100 32GB, 11.50.16, max 
UDMA/133

[1.643580] ata2.00: 62533296 sectors, multi 1: LBA48 NCQ (depth 32)
[1.644006] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE 
LOCK) filtered out

[1.644111] ata2.00: configured for UDMA/133
[1.646662] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE 
LOCK) filtered out
[1.652345] ata1.00: ATA-8: ST500LT012-9WS142, 0001SDM1, max 
UDMA/133
[1.652353] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 
32)
[1.692629] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE 
LOCK) filtered out

[1.692893] ata1.00: configured for UDMA/133
[1.693448] scsi 0:0:0:0: Direct-Access ATA  
ST500LT012-9WS14 SDM1 PQ: 0 ANSI: 5
[1.694217] scsi 1:0:0:0: Direct-Access ATA  SanDisk SSD 
i100 0.16 PQ: 0 ANSI: 5
[1.707706] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: 
(500 GB/466 GiB)

[1.707712] sd 0:0:0:0: [sda] 4096-byte physical blocks
[1.707741] sd 0:0:0:0: [sda] Write Protect is off
[1.707744] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[1.707766] sd 0:0:0:0: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[1.707839] sd 1:0:0:0: [sdb] 62533296 512-byte logical blocks: 
(32.0 GB/29.8 GiB)

[1.707850] sd 1:0:0:0: [sdb] Write Protect is off
[1.707852] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[1.707866] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA




but later I see:

[3.167019] scsi 6:0:0:0: Direct-Access Generic- Multi-Card 
  1.00 PQ: 0 ANSI: 0 CCS

[3.167626] sd 6:0:0:0: Attached scsi generic sg2 type 0
[3.241626] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[   31.831866] ata2.00: exception Emask 0x0 SAct 0x8000 SErr 0x4 
action 0x6 frozen

[   31.831979] ata2: SError: { CommWake }
[   31.832036] ata2.00: failed command: READ FPDMA QUEUED
[   31.832115] ata2.00: cmd 60/08:78:a8:2d:ba/00:00:03:00:00/40 tag 15 
ncq dma 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 
0x4 (timeout)

[   31.832300] ata2.00: status: { DRDY }
[   31.832355] ata2: hard resetting link
[   37.183839] ata2: link is slow to respond, please be patient 
(ready=0)

[   41.863839] ata2: COMRESET failed (errno=-16)
[   41.863917] ata2: hard resetting link
[   47.215836] ata2: link is slow to respond, please be patient 
(ready=0)

[   51.895839] ata2: COMRESET failed (errno=-16)
[   51.895916] ata2: hard resetting link
[   57.247839] ata2: link is slow to respond, please be patient 
(ready=0)

[   86.947859] ata2: COMRESET failed (errno=-16)
[   86.947938] ata2: limiting SATA link speed to 3.0 Gbps
[   86.947941] ata2: hard resetting link
[   91.999840] ata2: COMRESET failed (errno=-16)
[   91.19] ata2: reset failed, giving up
[   91.76] ata2.00: disabled
[   92.08] sd 1:0:0:0: [sdb] tag#15 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE cmd_age=90s

[   92.15] sd 1:0:0:0: [sdb] tag#15 Sense Key : Not Ready [current]
[   92.21] sd 1:0:0:0: [sdb] tag#15 Add. Sense: Logical unit not 
ready, hard reset required
[   92.27] sd 1:0:0:0: [sdb] tag#15 CDB: Read(10) 28 00 03 ba 2d 
a8 00 00 08 00
[   92.34] blk_update_request: I/O error, dev sdb, sector 62533032 
op 0x0:(READ) flags 0x80700 phys_seg 1 prio cl

ass 0
[   92.000188] ata2: EH complete
[   92.000327] sd 1:0:0:0: [sdb] tag#16 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[   92.000337] sd 1:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 03 ba 2d 
a8 00 00 08 00
[   92.000344] blk_update_request: I/O error, dev sdb, sector 62533032 
op 0x0:(READ) flags 0x0 phys_seg 1 prio class

0
[   92.000486] Buffer I/O error on dev sdb, logical block 7816629, 
async page read
[   92.002262] sd 1:0:0:0: [sdb] tag#12 FAILED Result: