Hi. I changed userdata disk from HDD to SSD. It’s work but only from from this USB 2.0. port when I used to copy data to new disk. When I change new disk to USB 3.0. after plug-off old disk system doesn’t work ok. What should I need to do?
I did that with one of my machines
I used a livecd (ventoy) with a live version of clonezilla
Have both the drives on one machine…boot into the live clonezilla do a device->device clone…done
You might have to modify /etc/fstab to reflect the new UUID of the cloned drive (if the ID is different) but I think clonezilla fixes that automatically
Another method would be to use gparted(or cli fdisk) to create “new” partitions on the new drive, then use rsync to archive over (copy all settings/links/date-time) flags to new partition
Thanks but I moved userdata of DietPi from old disk to new one already. So what should I cloned? In fstab I have only UUID sdcard and new external drive. Only I cant change the USB port.
What device do you use? Maybe it can only boot from USB 2?
Rock64 No, because old disk HDD was booting from USB 3.0. I wrote about it before.
- I used Rock64 with DietPi one year with HDD plug in to USB 3.0. and I bought new SSD
- Plug in to USB 2 and mount
- Format SSD
- Change userdata do SSD from HDD and wait to proces finish.
- Plug off old disk.
- System start from USB 2.0
- ok.
- When I change new SSD to USB 3.0 system boot from SDCard but can’t find new disc and userdata and I cannot login.
I moved this into an own topic as the other one was 2 years old.
Can you confirm that the USB-SATA adapter supports USB 3.0? Probably it’s only capable for 2.0.
I found an older issue related to USB3 on Rock64 no usb3 after apt upgrade / Rock64
Seems to be kernel related, to bad but it looks there was no solution. Can you share following
Required
- DietPi version |
cat /boot/dietpi/.version - Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN - Kernel version |
uname -a - Architecture |
dpkg --print-architecture - SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3)
@MichaIng probably you can have a look.
J can confirm because I used it with old disk.
# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=22
G_DIETPI_VERSION_RC=3
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
bullseye
Linux Rock64 6.1.50-current-rockchip64 #3 SMP PREEMPT Wed Aug 30 14:11:13 UTC 2023 aarch64 GNU/Linux
arm64
ROCK64 (aarch64)
old HDD is working on USB3 but new SSD not?
yes
For precision. The system boot from the SD card. It is only about the external USB drive that has been selected to change destination of userdata.
So you don’t try to boot from it, you just can’t mount it?
only mounting user data from it. Boot media is SD card.
@Krotosz6
can you try to boot the system having your SSD plugged into USB3 and keep USB2 empty. Even if it take time. You should be able to login using SSH. It might services are failing but wenn need to have a look how your system looks like while SSD is connected to USB3
I can’t log in via SSH, but I can see what it displays on a screen connected directly via HDMI.
When I connect to USB 3.0 it displays this. When I connect to US 2.0 it logs in normally.
Arabian 23.8.1 bullseye tty1
Rock64 login: root (automatic login)
Linux Rock64 6.1.50-current-rockchip64 83 SHP PREEMPT Ned Aug 30 14:11:13 UTC 2023 aarch64
The programs included with the Debian Gil/Linux system are free software;
the exact distribution terms for each prpgram described in the
individual files in /usr/share/doc/*/copyright.
Debian Gil/Linux comes math ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
scsi host0: uas_pre_reset: timed out
usb device not accepting address 2, error -71
scsi host0: uas_pre_reset: timed out
I/0 error, dev sda, sector 2000408864 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
device offline error, dev sda, sector 2000408864 op 0x0:(READ) flags 0x0 phys...seg 1 prio class 2
Buffer 1/0 error on dev sda, logical block 250051108, async page read
scsi host0: uas_pre_reset: timed out
scsi host0: uas_pre_reset: timed out
sd 0:0:0:0: Wed Asking for cache data failed
usb 3-1: device not accepting address 2, error -71
scsi host0: uss_pre_reset: timed out
scsi host0: uas_pre_reset: timed out
might need to disable UAS for that device
Have you run a fsck check on the drive…it could be dying? OR…is the drive externally powered, or are you trying to pull power from the USB?
fsck -l /dev/sda
Also…you do a blkid to get the UUID of the new drive, you then can change the mount point in /etc/fstab to reflect the mount point to where the new data is located by using the UUID= entry
Here is my /etc/fstab on my RPiZero2W, on a POE hat w/ 3x USB 2.0 and ethernet
warhawk@RPiZero2:~ $ cat /etc/fstab
proc /proc proc defaults 0 0
PARTUUID=265582b0-01 /boot vfat defaults 0 2
#PARTUUID=265582b0-02 / ext4 defaults,noatime 0 1
PARTUUID=9d981849-02a4-44be-8550-e3a3be218fee / ext4 defaults,noatime 0 1
PARTUUID=a9917cab-5fb3-40dc-806d-1e3a119c86ec /home ext4 defaults 02
# a swapfile is not a swap partition, no line here
# use dphys-swapfile swap[on|off] for that
warhawk@RPiZero2:~ $ sudo blkid
/dev/mmcblk0p1: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="0B22-2966" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="265582b0-01"
/dev/mmcblk0p2: LABEL="rootfs" UUID="3ad7386b-e1ae-4032-ae33-0c40f5ecc4ac" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="265582b0-02"
/dev/sda1: UUID="da1a2987-69f0-45b8-8a84-18b4ef88fd61" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="a9917cab-5fb3-40dc-806d-1e3a119c86ec"
/dev/sdb1: LABEL="rootfs" UUID="2e85c21b-014a-481f-9699-f569465d82cb" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="9d981849-02a4-44be-8550-e3a3be218fee"
/dev/zram0: UUID="c5af9da8-ef32-447a-a0e8-2a19ea84fdac" TYPE="swap"
warhawk@RPiZero2:~ $ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 57.3G 0 disk
└─sda1 8:1 1 57.3G 0 part /home
sdb 8:16 1 28.7G 0 disk
└─sdb1 8:17 1 28.7G 0 part /
mmcblk0 179:0 0 14.4G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot
└─mmcblk0p2 179:2 0 14.2G 0 part
zram0 254:0 0 512M 0 disk [SWAP]
I have a 32GB Sandisk Ultrafit for /, a 64gb Sanddisk Ultrafit for /home, and I boot off the 16gb cheapo SD card I got in bulk so I don’t have to flash the eeprom on the board, and it always comes up
I am running a 64bit build of Raspbian I believe
The problem seems to be your USB adapter, the OS or the port doesn’t seem to like how it’s communicating
As someone else said…seems there was a snafu with a new kernel release…or power
https://forum.pine64.org/showthread.php?tid=5557
My fstab file:
# You can use "dietpi-drive_manager" to setup mounts.
# NB: It overwrites and re-creates physical drive mount entries on use.
#----------------------------------------------------------------
# NETWORK
#----------------------------------------------------------------
#----------------------------------------------------------------
# TMPFS
#----------------------------------------------------------------
tmpfs /tmp tmpfs size=991M,noatime,lazytime,nodev,nosuid,mode=1777
tmpfs /var/log tmpfs size=50M,noatime,lazytime,nodev,nosuid
#----------------------------------------------------------------
# MISC: ecryptfs, vboxsf, glusterfs, mergerfs, bind, Btrfs subvolume
#----------------------------------------------------------------
#----------------------------------------------------------------
# SWAP SPACE
#----------------------------------------------------------------
#----------------------------------------------------------------
# PHYSICAL DRIVES
#----------------------------------------------------------------
UUID=19e46d43-2ef4-45d3-be06-ceee5e2cb50f / ext4 noatime,lazytime,rw 0 1
UUID=81b0e856-8635-4fa1-bbb6-a0b740623313 /mnt/81b0e856-8635-4fa1-bbb6-a0b740623313 ext4 noatime,lazytime,rw,nofail,noauto,x-systemd.automount
UUID=85d9c442-e5ec-43fc-9658-5f230be1e58d /mnt/85d9c442-e5ec-43fc-9658-5f230be1e58d ext4 noatime,lazytime,rw,nofail,noauto,x-systemd.automount
Here my lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 953,9G 0 disk
└─sda1 8:1 0 953,9G 0 part /mnt/81b0e856-8635-4fa1-bbb6-a0b740623313
mtdblock0 31:0 0 16M 0 disk
mmcblk0 179:0 0 29,7G 0 disk
└─mmcblk0p1 179:1 0 29,7G 0 part /
following is showing more information.
lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
readlink /mnt/dietpi_userdata/
readlink -f /mnt/dietpi_userdata/
sda 953,9G 0 disk
└─sda1 ext4 953,9G 0 part /mnt/81b0e856-8635-4fa1-bbb6-a0b740623313 14d43ac0-01 81b0e856-8635-4fa1-bbb6-a0b740623313
mtdblock0 16M 0 disk
mmcblk0 29,7G 0 disk
└─mmcblk0p1 ext4 29,7G 0 part /
/mnt/81b0e856-8635-4fa1-bbb6-a0b740623313/dietpi_userdata