Bug #232
NC 3.0 rc3 install onto USB stick fails
| Status: | New | Start: | 08/14/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
(Issue tracker doesn't have a 'target version' entry for rc3).
Possibly related to Issue #51
USB stick is Corsair voyager, 16GB. Initially formatted with FAT32, then tried again after wiping the partition table, no change.
Installation fails with:
Cannot create ZFS 'root' pool using disks with error: cannot open '/dev/dsk/c0t0d0s0': no such device or address
After looking at the discussion on Issue #51 I modified nexenta-install.sh to grab the value of $(RM_DISK}, which is: /dev/rdsk/c0t0d0p0
Commenting out that section of the autopart routine (per discussion of #51) and running the install again produces the error:
Cannot auto-partition /dev/rdsk/c0t0d0p0 disk with error: Operation on mounted disks must be interactive
History
Updated by Jérôme Warnier about 1 year ago
Did you try to clear the partition table as explained in #51?
PC are using a partitioning scheme, while BSD systems (as Solaris is) use slices. Both are different and maybe the autopartitioner doesn't like the first one.
Updated by Nick Brown about 1 year ago
Yes, I used the dd command given in #51. The same error still occurs.
Updated by Rob Elmes 9 months ago
I initially had the same problem with the same USB Stick, which had been used in a Windows environment previously.
To fix, get to the point where the installer has detected the various storage devices and is asking you to choose where to install. Drop to the log screen and obtain the full path for the device on /dev/rdsk/xxxxxx. In my case this was /dev/rdsk/c3t0d0p0
Then at the console:
fdisk /dev/rdsk/c3t0d0p0
Now delete all the partitions from the device (option 3) Once all deleted update the device and exit (option 6)
Go back to the installer screen and choose the device and start the install - it should now partition it.
I'd have thought that using DD to wipe the device would have the same effect as this though!