Replace USB sticks - error grub

Status
Not open for further replies.

ulus

Dabbler
Joined
Jan 14, 2015
Messages
14
Hello,
I just replaced the usb sticks in our FreeNAS-9.3-STABLE-201512121950 box.
Status reported 1 of the sticks with checksum error.
So I started to replace the sticks by gui using brand new SanDisk Cruzer Fit 16GB.
What make me confusing is the grub error Messages for both stick (copied last ones)

Jan 14 02:08:06 freenas93 ugen1.4: <SanDisk> at usbus1
Jan 14 02:08:06 freenas93 umass3: <SanDisk Cruzer Fit, class 0/0, rev 2.10/1.00, addr 4> on usbus1
Jan 14 02:08:06 freenas93 umass3: SCSI over Bulk-Only; quirks = 0xc100
Jan 14 02:08:06 freenas93 umass3:14:3:-1: Attached to scbus14
Jan 14 02:08:06 freenas93 da3 at umass-sim3 bus 3 scbus14 target 0 lun 0
Jan 14 02:08:06 freenas93 da3: <SanDisk Cruzer Fit 1.00> Removable Direct Access SCSI-6 device
Jan 14 02:08:06 freenas93 da3: Serial Number 4C531000641019111232
Jan 14 02:08:06 freenas93 da3: 40.000MB/s transfers
Jan 14 02:08:06 freenas93 da3: 15264MB (31260672 512 byte sectors: 255H 63S/T 1945C)
Jan 14 02:08:06 freenas93 da3: quirks=0x2<NO_6_BYTE>
Jan 14 11:09:05 freenas93 notifier: 32+0 records in
Jan 14 11:09:05 freenas93 notifier: 32+0 records out
Jan 14 11:09:05 freenas93 notifier: 33554432 bytes transferred in 2.228065 secs (15059900 bytes/sec)
Jan 14 11:09:07 freenas93 notifier: dd: /dev/da3: end of device
Jan 14 11:09:07 freenas93 notifier: 33+0 records in
Jan 14 11:09:07 freenas93 notifier: 32+0 records out
Jan 14 11:09:07 freenas93 notifier: 33554432 bytes transferred in 2.214630 secs (15151259 bytes/sec)
Jan 14 11:09:42 freenas93 notifier: Installing for i386-pc platform.
Jan 14 11:10:30 freenas93 notifier: /usr/local/sbin/grub-install: error: failed to get canonical path of `/dev/replacing-0'.

Did scrub of the boot pool without Errors.
Should I be concernd about the message?

Best Regards
 
D

dlavigne

Guest
This was reported in #6993, but it is unclear if that really was fixed or not. When you have time to experiment, can you try booting off of each stick singly and report back whether or not it worked for both devices? If the bug is not fixed, the sticke that gave the error should not be able to boot by itself.
 

bmcclure937

Contributor
Joined
Jul 13, 2012
Messages
110
History
#1
2fbacaf3ac190ccab75d3b16968e92c9
Updated by Sean Fagan about 21 hours ago

  • Status changed from Unscreened to Waiting For Feedback
You need to ensure your BIOS is set up correctly.

Most BIOSes will in fact only pick one USB drive, and if that fails, or even if it disappears, not necessarily pick another one.
 
Status
Not open for further replies.
Top