Cannot Import Disk (usb)

[larlap]

FreeNAS-9.3-STABLE-201412200530

In attempting to Import Disk, an external USB hard disk, it displays the failure as shown on the attached file.

I don't know if this problem is related to this bug. If it is, I don't know how to perform the fix. Any suggestions?

I am using the external disk for backup and therefore cannot do it. Yes, I know this practice is not recommended and I am backing up to the cloud. Still, it provides some degree of comfort.

Thanks Larry

 

[mjws00]

The import function has changed. Looks like it tries to copy data to a pool instead of set a mount point. It's also broken with ntfs as far as I can tell. If you want to mount an external drive as per 9.2 I think it is CLI only. I only tested briefly but that's what I experienced.

 

[larlap]

It's formatted UFS.

How can I mount this via CLI? Will that command persist across reboots?

 

[mjws00]

I haven't tested that, sorry. Has to be a way to keep /etc/fstab persistent but might require a configuration db touch... not sure. The command will be something like 'mount -w /dev/da2 /mnt/tmpufs' check the man page for all the options. Best thing to do is just test for yourself. Not many posts or people messing with this yet.

 

[dlavigne]

See http://doc.freenas.org/9.3/freenas_storage.html#import-disk. You need to first create a dataset to copy the data to, then refer to it in "Destination".

 

[larlap]

Thanks for the documentation, dlavigne. It explains what I was doing wrong.

I do not want to copy the data from the USB drive to a dataset. I want to mount the drive for writing/backing-up data from existing datasets.

What is strange to me is that on the machine I use at my office and running FreeNAS-9.3-STABLE-201412200530, I have done this successfully and am able to run rsync scripts to copy data from zfs datasets to the USB device.

/dev/ufs/usback on /mnt/usback (ufs, local, soft-updates, nfsv4acls)
​

It identifies itself as:

$ sudo camcontrol identify da0
pass8: <ST4000DM000-1F2168 CC54> ATA-9 SATA 3.x device
pass8: 40.000MB/s transfers

protocol ATA/ATAPI-9 SATA 3.x
device model ST4000DM000-1F2168
​

The disk on the system I'm having trouble with does not respond to identify but does to inquiry:

$ sudo camcontrol inquiry da0
pass6: <WD My Book 1230 1065> Fixed Direct Access SCSI-6 device
pass6: Serial Number SomeSerialNumber
pass6: 40.000MB/s transfers​

When I attempted to mount the USB on the original system via CLI, it waited for about 60 seconds before returning the error:

$ sudo mount -w /dev/ufs/sysback /mnt/sysback
Password:

mount: /dev/ufs/sysback: Input/output error​

Maybe I should reboot and hope that the system sees the disk?

 

[dlavigne]

The importer has changed for 9.3. You can no longer import (i.e. mount and use) UFS volumes and the import of disks is restricted to read-only for the only purpose of copying the data to an existing ZFS pool.

See http://doc.freenas.org/9.3/freenas_intro.html#what-s-new-in-9-3:

FreeNAS® is now ZFS only. This means that the “UFS Volume Manager” has been removed and disks can no longer be formatted with UFS. However, for backwards compatibility, existing UFS-formatted disks can still be imported using “Import Disk” so that their contents can be copied to a ZFS pool.

 

[larlap]

OK, I understand. I have two questions.

First, how do you explain that I could/did import an existing UFS-formatted external USB drive and am able to write to it for backup purposes on my personal 9.3 system (see attached image)?

What do you recommend for backup now? Can I format a single drive zfs and use that for backup?

 

[mjws00]

Can't say I've looked too closely, but if the office 9.3 was an upgrade, it likely kept the fstab entry and the mount point.

The /dev/ufs/sysback won't exist on the second machine. The old UFS Volume Manager created that. Use the actual /dev/<device>. 'camcontrol devlist' will show it to you. The GUI is gone, but BSD is still BSD.

mkdir /mnt/sysback
mount -w /dev/da0 /mnt/sysback

You may have to tweak those commands slightly, but should be close.

I'd like to see the current recommendation for a simple backup such as yours. Single device zfs pools have their own issues. But the GUI is now limited. I'd just use the CLI, but interested in seeing if there is an actual model in the system that will be recommended.

 

[larlap]

Thanks for the advice, mjws00. I don't feel it's OK not to do backup.

I tried the mount on that device, but it says it does not exist. Something is wrong.

$ sudo camcontrol devlist
Password:
<WDC WD3000FYYZ-01UL1B1 01.01K02> at scbus1 target 0 lun 0 (pass0,ada0)
<WDC WD3000FYYZ-01UL1B1 01.01K02> at scbus2 target 0 lun 0 (pass1,ada1)
<WDC WD3000FYYZ-01UL1B1 01.01K02> at scbus3 target 0 lun 0 (pass2,ada2)
<WDC WD3000FYYZ-01UL1B1 01.01K02> at scbus4 target 0 lun 0 (pass3,ada3)
<WDC WD3000FYYZ-01UL1B1 01.01K02> at scbus5 target 0 lun 0 (pass4,ada4)
<WDC WD3000FYYZ-01UL1B1 01.01K02> at scbus6 target 0 lun 0 (pass5,ada5)
<WD My Book 1230 1065> at scbus8 target 0 lun 0 (da0,pass6)
<WD SES Device 1065> at scbus8 target 0 lun 1 (ses0,pass9)
<JetFlash Transcend 16GB 8.07> at scbus9 target 0 lun 0 (da1,pass7)
<JetFlash Transcend 16GB 8.07> at scbus10 target 0 lun 0 (da2,pass8)
$ sudo mount -w /dev/da0 /mnt/sysback
Password:
mount: /dev/da0: No such file or directory

~# ll /dev/d*
crw-r----- 1 root operator 0xc4 Dec 22 10:58 /dev/da1
crw-r----- 1 root operator 0xca Dec 22 10:58 /dev/da1p1
crw-r----- 1 root operator 0xcb Dec 22 10:58 /dev/da1p2
crw-r----- 1 root operator 0xc5 Dec 22 10:58 /dev/da2
crw-r----- 1 root operator 0xcc Dec 22 10:58 /dev/da2p1
crw-r----- 1 root operator 0xcd Dec 22 10:58 /dev/da2p2
crw------- 1 root wheel 0x4 Dec 22 10:58 /dev/devctl
cr-------- 1 root wheel 0x63 Dec 22 10:58 /dev/devstat
lrwxr-xr-x 1 root wheel 11 Dec 22 10:59 /dev/dumpdev@ -> /dev/ada0p1​

What am I missing here?

 

[mjws00]

Not sure why you'd have da0 in the camcontrol devlist and not a corresponding device in /dev/
I'd unplug and replug and see if you can spot what happens at the console. Should be a ugen1.2 entry and umass() entry and the drive listed.
No idea if the <ses device 1065> is that mybook screwing with you, but could be.

A BSD wiz might have a quick answer. I haven't had this problem to solve.

 

[larlap]

Thanks again, mjws00. I'll have to wait until I can get over to the site where the Supermicro is.

And I believe you're correct about the difference between the two 9.3 installs. On the one where I'm able to use the USB as backup, I loaded the 9.3 onto two thumb drives and loaded the config from the 9.2.1.8 version. I was not able to do that on the Supermicro machine; the config failed to load so I had to join an AD domain, import the volume, re-do permissions on the datasets and create the cron jobs. It was good practice since I'd never done that before. It made me to trust that I could do a recovery.