Cant switch userdata to new HDD

I have a 4 TB HDD connected via USB 3.0 on my Odroid N2 where all my downloads are sent to.
I bought a new 6 TB HDD and im trying to switch all my userdata to this HDD using dietpi-drive_manager.
I mounted the new 6 TB HDD and tried swapping the user_data to this drive but
everytime i try it just runs for a little bit and then gives me an error.
The error message is flashed for just a millisecond (too fast to tell what it says) and then I get returned to the drive_manager settings page.
After this happens and I exit, the dietpi installation will freeze up and when I try reconnecting via SSH it will let me login, display the MOTD and then freeze up again. I need to power cycle the Odroid to get it working again.

Any help would be much appreciated!

Hi,

many thanks for your report. Are you connected via SSH? Can you scroll up on your SSH client once hit by the issue. Maybe there are some error messages. As well, can you check if you are able to run following

dmesg -l err,crit,alert,emerg

Thanks for the quick response.
Unfortunately, I cant scroll up to get any error message diagnostic as it’ll freeze up immediately after exiting the drive_manager
This is the error list I get from the dmesg command


[    0.334933] codec_mm_module_init
[    0.343763] clkmsr ffd18004.meson_clk_msr: failed to get msr ring reg0
[    0.360864] cvbs_out: chrdev devno 263192576 for disp
[    0.474919] dmi: Firmware registration failed.
[    0.763914] perf_event: read sys_cpu_status0_offset failed, ret = -22
[    0.776608] meson-pwm ff802000.pwm: pwm pinmux : can't get pinctrl
[    0.776820] meson-pwm ffd1b000.pwm: pwm pinmux : can't get pinctrl
[    0.783451] mtdoops: mtd device (mtddev=name/number) must be supplied
[    0.804206] meson_cpufreq_probe: Registered platform drive
[    0.804320] ff803000.serial: clock gate not found
[    3.009250] gpio-keypad ff800000.gpio_keypad: failed to get gpio index from dts
[    3.023172] efuse efuse:  open efuse clk gate error!!
[    3.497999] di_get_vpu_clkb: get clk vpu error.
[    3.677453] PPMGRDRV: err: ppmgr_driver_probe called
[    3.682568] Reserved memory: failed to init DMA memory pool at 0x00000000e3000000, size 0 MiB
[    3.811477] meson-mmc: >>>>>>>>hostbase ffffff8008687000, dmode
[    3.864396] meson-mmc: >>>>>>>>hostbase ffffff80086a1000, dmode
[    3.864613] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff
[    3.864616] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7
[    3.864628] meson-mmc: meson_mmc_irq_thread_v3() 567: set 1st retry!
[    3.864629] meson-mmc: retry cmd 1 the 3-th time(s)
[    3.872517] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff
[    3.872518] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7
[    3.872528] meson-mmc: retry cmd 1 the 2-th time(s)
[    3.879258] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff
[    3.879259] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7
[    3.879268] meson-mmc: retry cmd 1 the 1-th time(s)
[    3.885240] meson-mmc: emmc: resp_timeout,vstat:0x9dff0800,virqc:3fff
[    3.885241] meson-mmc: emmc: err: wait for desc write back, bus_fsm:0x7
[    3.890771] meson-mmc: Command retried failed line:585, cmd:1
[    4.016262] cectx ff80023c.aocec: cec driver date:Ver 2019/1/7

[    4.029428] cectx ff80023c.aocec: not find 'port_num'
[    4.034538] cectx ff80023c.aocec: using cec:1
[    4.039055] cectx ff80023c.aocec: no hdmirx regs
[    4.043808] cectx ff80023c.aocec: no hhi regs
[    4.048320] cectx ff80023c.aocec: not find 'output'
[    4.058071] cectx ff80023c.aocec: irq cnt:2
[    4.061098] cectx ff80023c.aocec: wakeup_reason:0x0
[    4.066041] cectx ff80023c.aocec: cev val1: 0x0;val2: 0x0
[    4.071543] cectx ff80023c.aocec: aml_cec_probe success end
[    4.191735] defendkey ff630218.defendkey: Reserved memory is not enough!
[    4.218055] meson-mmc: card IN
[    4.221769] Error: Driver 'spdif-dit' is already registered, aborting...
[    4.234030] aml_card_probe error ret:-517
[    4.590614] meson-mmc: Tuning transfer error: nmatch=0 tuning_err:0xffffffac
[    7.955057] rtc-pcf8563 3-0051: low voltage detected, date/time is not reliable.
[   14.084956] sd 0:0:0:0: [sda] No Caching mode page found
[   14.092377] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   14.151477] sd 1:0:0:0: [sdb] No Caching mode page found
[   14.155601] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[  200.239862] rtc-pcf8563 3-0051: low voltage detected, date/time is not reliable.
[  227.869373] rtc-pcf8563 3-0051: low voltage detected, date/time is not reliable.
[ 2825.766981] CIFS VFS: error -95 on ioctl to get interface list
[ 2830.378987] blk_update_request: critical target error, dev sdb, sector 1681930496

So I lied, it still freezes but I can scroll up.

Here is the output:


cp: cannot stat '/mnt/7a82ee98-c8e0-42cd-8011-ee2d09ad8b05/dietpi_userdata/./downloads/TD TV shows': Input/output error
cp: clearing permissions for '/mnt/3a35bd03-5964-48ce-95a1-cf3cc9fb8373/dietpi_userdata/./downloads': Read-only file system
cp: cannot stat '/mnt/7a82ee98-c8e0-42cd-8011-ee2d09ad8b05/dietpi_userdata/./nzbget': No such file or directory
cp: cannot stat '/mnt/7a82ee98-c8e0-42cd-8011-ee2d09ad8b05/dietpi_userdata/./sonarr': No such file or directory
cp: cannot stat '/mnt/7a82ee98-c8e0-42cd-8011-ee2d09ad8b05/dietpi_userdata/./radarr': No such file or directory
cp: cannot stat '/mnt/7a82ee98-c8e0-42cd-8011-ee2d09ad8b05/dietpi_userdata/./lidarr': No such file or directory
cp: cannot stat '/mnt/7a82ee98-c8e0-42cd-8011-ee2d09ad8b05/dietpi_userdata/./New': No such file or directory
cp: clearing permissions for '/mnt/3a35bd03-5964-48ce-95a1-cf3cc9fb8373/dietpi_userdata/.': Read-only file system
[FAILED] DietPi-Set_userdata | ERROR: Failed to copy /mnt/7a82ee98-c8e0-42cd-8011-ee2d09ad8b05/dietpi_userdata/ to /mnt/3a35bd03-5964-48ce-95a1-cf3cc9fb8373/dietpi_userdata.
[FAILED]  An issue has occurred
dumpe2fs 1.43.4 (31-Jan-2017)
dumpe2fs: No such file or directory while trying to open /dev/sdb1
(standard_in) 1: syntax error
(standard_in) 1: syntax error

hmm you some issues on your device.

[  200.239862] rtc-pcf8563 3-0051: low voltage detected, date/time is not reliable.
[  227.869373] rtc-pcf8563 3-0051: low voltage detected, date/time is not reliable.
[ 2825.766981] CIFS VFS: error -95 on ioctl to get interface list
[ 2830.378987] blk_update_request: critical target error, dev sdb, sector 1681930496

Especially low voltage could lead to issues, as you system is consuming more power than it get. Do you use external power supply’s for your HDD’s or are they just plugged into your SDC?

As well blk_update_request: critical target error, dev sdb is pointing into direction of connection issues betwenn your SBC and the HDD. Most probably due issues with power. But could be a bad cable es well.

Drive Manager as well has issues to write to your 2nd HDD dumpe2fs: No such file or directory while trying to open /dev/sdb1

I highly recommend to use external power supplies for your HDD’s

The 4tb HDD is a WD passport that gets its power through the SBC. So far I’ve never had any problems writing data to it.

The 6tb HDD has its own power supply. I think the voltage errors may be due to a power outage we had here.

I’ll try switching power supply to the SBC. If you have any other suggestions I can try please let me know. Thank you.

can you try to change cable or USB ports? What about to copy your disk on a different machine and just re-plug the new disk to your SBC?

So it looks like I got it to work :slight_smile:
It’s been running for an hour now, fingers crossed.
I formatted the 6 TB disk and then rebooted
Checked to make sure both disks show up in fstab correctly, they do.
Then started swapping userdata and it works.
Think my problem was formatting disk and then swapping userdata immediately afterwards without rebooting.
So it looks like it was all my Noob mistake causing this issue.
Thanks Joulinar for offering your help!

ok good that it’s working now. Probably there was something wrong on the first run to format your HD. And this was leading to these issues. Who knows :slight_smile:

Still doesnt work unfortunately. It runs for a while and then usually ends with an issue alert and then an sdb1 error no such file or device.
In the dmesg log I then see a host of errors concerning the new hdd. Interestingly enough when I plug the HDD into other computers it seems to work fine. Im using Diskgenius in windows to check for bad sectors right now, it’ll take 9 hours to complete. I’m hoping after this I’ll get a clue if there is anything wrong with the disk. Since this is a brand new disk there shouldnt be though. Anyway I’ll keep this updated for anyone having a similar problem in the future.

Next things to try:

  • Copy over the data without using dietpi and see if that works
  • Cry and rethink my life

to bad that this is not working. Did you tried to switch cable and USB ports?