Possible Issue with liveusb from rufus on 64 bit

[ghost]

'Fixed: Don't use rufus or unetbootin'

nouveau E[ DRM] Pointer to TDMS table invalid
nouveau E[ DRM] Pointer to flat table invalid
sd 6:0:0:0P [sdc] No Caching mode found
sd 6:0:0:0P [sdc] Assuming drive cache: write through
ERROR 'dev/by-label/APRICITY_201507' device did not show up after 30 seconds...
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finished
sh: can't access tty: job controll turned off
[rootfs /]#

[ghost]

Update: Tried to write to usb again, and to no avail. Trying to re-download.

[agajews]

Your download is probably fine as I have reproduced this issue when writing to USB with Rufus. I am currently evaluating other Windows ISO writing tools to recommend in the installation instructions. At the moment, I'm leaning towards Win32 Disk Imager which can be found at sourceforge.net/projects/win32diskimager. This tool does not have the same issue Rufus (and possibly UNetbootin) has. Note that you may have to select '.' instead of '*.img' when selecting the Apricity OS .iso file.

[Boomer67]

I had the same issue with Rufus 2.3, so I used Linux Live USB Creator to create a bootable USB flash drive in Windows and was able to use it to boot into Apricity. From there I installed it onto my hard drive successfully.

[pbatard]

Note that the issue is probably related to the one detailed here.

Basically, any distribution that uses /dev/disk/by-label/<SOME_ID> needs to be very mindful that, whereas you can choose a long ID when booting ISO9660 or UDF media, such as APRICITY_201507, as soon as you copy the content to a FAT32 drive, which is typical of USB installations, you are going to face the limitations of the FAT32 file system in terms of volume label, such as no more than 11 characters, everything uppercase, and so on.

The Arch distro maintainers are aware of this, which is why they keep a short uppercase label that is compliant with the FAT32 restrictions. But it's not something that might be obvious downstream, until you actually try to boot from a FAT32 USB drive on an UEFI system...

[marciusvinicius]

I has the same probleam, trying with rufus 64 bit does'nt works, but with the same image (.iso file) in a linux I write sucess.

[darkn3rd]

This is a bug, inherited from ArchLinux it seems: https://bbs.archlinux.org/viewtopic.php?id=142473