[opensuse-support] Sata SSD physical sector size shown as 512bytes? And other stuff when moving root drive to new physical drive.
Hi list, had thought that all SSD actually had like 4kilobytes as physical sector size and only 512bytes emulation stuff. My leap 15.0 machine upgraded the hardware of the root disk to SSD from HDD. fdisk -l now shows 512/512 for both logical and physical of this root disk. With the help of gparted distro, I have migrated, copied, over the / and /home partitions from the old HDD to the new empty SSD. Created, enlarged the partition sizes, and marked the / as bootable, and then used the rescue system of Leap 15.0 bootmedia to mount all that stuff, addtl proc sys and dev ans --rbind and then chroot into the system. Then added some grub2 stuff to make the mbr bootinfo be written again and at the end mkinitrd. All went basically fine (using /dev/disk/by-uuid/ mostly everywhere in /etc/default/grub and in /etc/fstab ). I basically followed the suse.com KB articles: <https://www.suse.com/de-de/support/kb/doc/?id=7018639> <https://www.suse.com/de-de/support/kb/doc/?id=7018126> But now I am wondering if I need to consider more stuff when making the switch from HDD to SSD, or did I do bascially just fine? fdisk shows as 512/512 as stated above and the bootlogging (dmesg -e or journalctl -b ) show some weird stuff for this new SSD early during bootup with those ata.1 lines printing some drivenotready or something I can look up later to be precise. This error didnt show when using the HDD. Now I wonder if my SSD is too new for the sata chipset of the rather oldish motherboard or if something else is missing. Everything is working as AHCI according to bios and settings but I never mess much with this. Any hints into this? TY. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/01/2019 18.46, cagsm wrote:
Hi list, had thought that all SSD actually had like 4kilobytes as physical sector size and only 512bytes emulation stuff.
My leap 15.0 machine upgraded the hardware of the root disk to SSD from HDD. fdisk -l now shows 512/512 for both logical and physical of this root disk.
Yes, same here on four machines. ...
All went basically fine (using /dev/disk/by-uuid/ mostly everywhere in /etc/default/grub and in /etc/fstab ).
And it boots? Then good :-)
I basically followed the suse.com KB articles: <https://www.suse.com/de-de/support/kb/doc/?id=7018639> <https://www.suse.com/de-de/support/kb/doc/?id=7018126>
You could use clonezilla. Or you can use "rsync" instead of "dd", creating yourself the partitions. Huh, unless it is btrfs.
But now I am wondering if I need to consider more stuff when making the switch from HDD to SSD, or did I do bascially just fine?
There is a fstrim service or timer that should be on. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Wed, Jan 30, 2019 at 10:58 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
And it boots? Then good :-)
Yes the system came back up fine, boots normally. The Suse logo graphics stuff is not showing, only real text screen mode grub2 already to begin with, but that was already prior to the switch to ssd.
There is a fstrim service or timer that should be on.
Okay thanks will see about those trim commands or procedures with SSD. The current situation is: on every boot the system is detecting the sata devices, shown in the kernel logs (journalctl -b) just fine, and a bit later it shows some kind of exception and a reset of this one sata device. the other sata disks (classical hdd) and cdrom dont show this messages. Also the same sata cable worked fine on the previous hdd type of device, but I even replaced the old sata cable with a newer one for the ssd now. But still. This message shows up on every boot. when the device is initialised. Is this something to worry about? Thanks. ============================ Jan 29 19:21:33 linux010 kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 29 19:21:33 linux010 kernel: ata3.00: supports DRM functions and may not be fully accessible Jan 29 19:21:33 linux010 kernel: ata3.00: ATA-11: Samsung SSD 860 EVO 500GB, RVT02B6Q, max UDMA/133 Jan 29 19:21:33 linux010 kernel: ata3.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA Jan 29 19:21:33 linux010 kernel: ata8.00: ATAPI: HL-DT-ST DVDRAM GH22NS50, TN02, max UDMA/100 Jan 29 19:21:33 linux010 kernel: ata3.00: supports DRM functions and may not be fully accessible Jan 29 19:21:33 linux010 kernel: ata3.00: configured for UDMA/133 Jan 29 19:21:33 linux010 kernel: scsi 2:0:0:0: Direct-Access ATA Samsung SSD 860 2B6Q PQ: 0 ANSI: 5 Jan 29 19:21:33 linux010 kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0 Jan 29 19:21:33 linux010 kernel: ata3.00: Enabling discard_zeroes_data Jan 29 19:21:33 linux010 kernel: sd 2:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) Jan 29 19:21:33 linux010 kernel: sd 2:0:0:0: [sda] Write Protect is off Jan 29 19:21:33 linux010 kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 Jan 29 19:21:33 linux010 kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 29 19:21:33 linux010 kernel: ata3.00: Enabling discard_zeroes_data Jan 29 19:21:33 linux010 kernel: sda: sda1 sda2 sda3 Jan 29 19:21:33 linux010 kernel: ata3.00: Enabling discard_zeroes_data Jan 29 19:21:33 linux010 kernel: sd 2:0:0:0: [sda] supports TCG Opal Jan 29 19:21:33 linux010 kernel: sd 2:0:0:0: [sda] Attached SCSI disk Jan 29 19:21:35 linux010 kernel: ata3.00: exception Emask 0x0 SAct 0xf00 SErr 0x0 action 0x6 Jan 29 19:21:35 linux010 kernel: ata3.00: irq_stat 0x40000008 Jan 29 19:21:35 linux010 kernel: ata3.00: failed command: READ FPDMA QUEUED Jan 29 19:21:35 linux010 kernel: ata3.00: cmd 60/08:40:f8:40:40/00:00:01:00:00/40 tag 8 ncq dma 4096 in res 41/84:08:f8:40:40/00:00:01:00:00/00 Emask 0x410 (ATA bus error) <F> Jan 29 19:21:35 linux010 kernel: ata3.00: status: { DRDY ERR } Jan 29 19:21:35 linux010 kernel: ata3.00: error: { ICRC ABRT } Jan 29 19:21:35 linux010 kernel: ata3: hard resetting link Jan 29 19:21:35 linux010 kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 29 19:21:35 linux010 kernel: ata3.00: supports DRM functions and may not be fully accessible Jan 29 19:21:35 linux010 kernel: ata3.00: supports DRM functions and may not be fully accessible Jan 29 19:21:35 linux010 kernel: ata3.00: configured for UDMA/133 Jan 29 19:21:35 linux010 kernel: ata3: EH complete Jan 29 19:21:35 linux010 kernel: ata3.00: Enabling discard_zeroes_data -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 31/01/2019 10.52, cagsm wrote:
On Wed, Jan 30, 2019 at 10:58 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
And it boots? Then good :-)
Yes the system came back up fine, boots normally. The Suse logo graphics stuff is not showing, only real text screen mode grub2 already to begin with, but that was already prior to the switch to ssd.
There is a fstrim service or timer that should be on.
Okay thanks will see about those trim commands or procedures with SSD.
The current situation is: on every boot the system is detecting the sata devices, shown in the kernel logs (journalctl -b) just fine, and a bit later it shows some kind of exception and a reset of this one sata device. the other sata disks (classical hdd) and cdrom dont show this messages. Also the same sata cable worked fine on the previous hdd type of device, but I even replaced the old sata cable with a newer one for the ssd now. But still. This message shows up on every boot. when the device is initialised. Is this something to worry about?
I don't know. :-( You could try another cable, just in case. On my laptop I did the same operation, replace with an SSD. A percent of the boots, the disk is not recognized and the machine claims there is no operating system. I just try again. Some times I hit it with my palm, maybe there is a connector a bit lose. I have to open it again one day to reseat the cables to see if that's it. Maybe SSD gives those problems on old machines. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (2)
-
cagsm -
Carlos E. R.