device descriptor read/64, error -110. How-to copy OMV from usb3 drive > usb2 drive?

nettozzie · 11. Januar 2016

At random times my selfbuild nas reboots and gets stuck at "device descriptor read/64, error -110". I've installed my nas on a kingston datatraveler r3.0 g2 16gb usbdrive. My motherboard is quite old and doesn't have dedicated usb 3 ports so I stuck it in a usb 2 port.

What I found while looking for a solution is:

Zitat

USB error -110 means power exceeded, the host could not provide enough electric power for the pendrive to operate. Because it has not enough power also the USB stick cannot provide the device descriptor to the host, as a result it cannot be identified and so on. Maybe your motherboard it's overloaded with devices that consume all the available power.

And

Zitat

he problem was a USB 3.0 Stick that needed more current than usual for a USB 2.0 device. This lead to the errors. I replaced the stick and in addition to that I installed the latest BIOS-Drivers. No more problems!

So to fix the problem I want to copy the OMV installation to a usb 2 drive. How can I do this? (including bootloader etc.)

The source drive is a USB 3 16gb and I have a spare USB 2 8gb drive available. I'm on windows but could boot a linux live cd. Please help

ryecoaaron · 11. Januar 2016

Are you running the backports 3.16 kernel on your OMV install?

nettozzie · 11. Januar 2016

While booting it says 3.2.0-4-amd

ryecoaaron · 11. Januar 2016

Install omv-extras (if you haven't) and install the backports 3.16 from the kernel tab. This might fix your usb3 problem.

nettozzie · 11. Januar 2016

Currently I can't boot into OMW. I'm unable to get past the "device descriptor read/64, error -110" error. That's why I thought about copying the usb3 disk to a usb2.0 disk.

Can I boot OMW in another computer, or would that change my configuration?

ryecoaaron · 11. Januar 2016

Are you sure the usb stick isn't failing? If you didn't have the flashmemory plugin installed, I would almost guarantee that is the problem.

nettozzie · 11. Januar 2016

Zitat von ryecoaaron

Are you sure the usb stick isn't failing? If you didn't have the flashmemory plugin installed, I would almost guarantee that is the problem.

I don't think so. If I plug it into my Windows laptop I can view the partitions and it just works normally. It also boots the GRUB bootloader, but after that I get the error message described earlier.

nettozzie · 11. Januar 2016

On second though, you might be right. I can't copy the disk. I get an crc error (something with a bad sector). Is it possible to install OMV on another disk/usbdrive and use my old data that's on my 2x3TB harddrives?

WastlJ · 12. Januar 2016

Zitat von nettozzie

Is it possible to install OMV on another disk/usbdrive and use my old data that's on my 2x3TB harddrives?

Yes, without worries. - (Re)Installation of OpenMediaVault

nettozzie · 14. Januar 2016

Zitat von WastlJ

Yes, without worries. - (Re)Installation of OpenMediaVault

Thanks for the link. I've reinstalled OMV, mounted the drives and installed (and activated) the flashmemory plugin. On the flashmemory page it says:

Code

Fstab (/etc/fstab) needs to be changed manually. Following these steps to change:


Login as root locally or via ssh
Execute the following command:  nano /etc/fstab
Add noatime and nodiratime to root options.  See before and after example lines:
BEFORE:UUID=ccd327d4-a1ed-4fd2-b356-3b492c6f6c34  /  ext4  errors=remount-ro  0  1AFTER:UUID=ccd327d4-a1ed-4fd2-b356-3b492c6f6c34  /  ext4  noatime,nodiratime,errors=remount-ro  0  1Comment out the swap partition.  See before and after example lines (only need to add a # to beginning of the line):
BEFORE:UUID=a3c989d8-e12b-41d3-b021-098155d6b21b  none  swap  sw  0  0AFTER:#UUID=a3c989d8-e12b-41d3-b021-098155d6b21b  none  swap  sw  0  0Ctrl-o to save
Ctrl-x to exit
Enable the plugin
Reboot

Alles anzeigen

I've tried this and couldn't run OMV properly after. The usb drive on which I installed it became read only for all users. Below is my fstab file. Could somebody have a look at it and tell me what to edit exactly? Also do I need to edit the file through nano or can I use manually edit it in a texteditor (notepad) and upload it through ssh?

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=7834048b-3863-4e2b-9c4a-f435ac20e59b /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=37671ed5-cf81-438e-aa19-4f23f3d97d7c none            swap    sw              0       0
/dev/sda1       /media/usb0     auto    rw,user,noauto  0       0
/dev/sda2       /media/usb1     auto    rw,user,noauto  0       0
/dev/sda5       /media/usb2     auto    rw,user,noauto  0       0
/dev/sdb1       /media/usb3     auto    rw,user,noauto  0       0
# >>> [openmediavault]
UUID=dbb0fa51-526d-4b60-a37c-4edb12a05f34 /media/dbb0fa51-526d-4b60-a37c-4edb12a05f34 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]

Alles anzeigen

nettozzie · 17. Januar 2016

I think I've fixed it. This is now my fstab file:

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=7834048b-3863-4e2b-9c4a-f435ac20e59b /               ext4    noatime,nodiratime,errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
#UUID=37671ed5-cf81-438e-aa19-4f23f3d97d7c none            swap    sw              0       0
/dev/sda1       /media/usb0     auto    rw,user,noauto  0       0
/dev/sda2       /media/usb1     auto    rw,user,noauto  0       0
/dev/sda5       /media/usb2     auto    rw,user,noauto  0       0
/dev/sdb1       /media/usb3     auto    rw,user,noauto  0       0
# >>> [openmediavault]
UUID=dbb0fa51-526d-4b60-a37c-4edb12a05f34 /media/dbb0fa51-526d-4b60-a37c-4edb12a05f34 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]

Alles anzeigen

device descriptor read/64, error -110. How-to copy OMV from usb3 drive > usb2 drive?

Jetzt mitmachen!

Tags