[arch-general] Another 'gotta be something idiotic': trying to create bootable USB thumb drive
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I can't believe I'm having trouble with this. I'm trying to follow the directions at https://wiki.archlinux.org/index.php/USB_Installation_Media Specifically: dd bs=4M if=/path/to/archlinux.iso of=/dev/sdx Which I translate to: sudo dd bs=4M if=Downloads/archlinux-2013.04.01-dual.iso of=/dev/sdb dd: failed to open ‘/dev/sdb’: No medium found And you see the result. /dev/sdb does indeed exist and is writable. It's a brand new 4GB flash drive and I moved the crap that came preloaded on it somewhere else before dismounting it. Here's the dmesg snippet: [151086.251674] usb 2-3.1.4: new high-speed USB device number 5 using ehci-pci [151087.600267] Initializing USB Mass Storage driver... [151087.600770] scsi6 : usb-storage 2-3.1.4:1.0 [151087.601106] usbcore: registered new interface driver usb-storage [151087.601112] USB Mass Storage support registered. [151088.603391] scsi 6:0:0:0: Direct-Access SanDisk Cruzer Glide 1.26 PQ: 0 ANSI: 5 [151088.606083] sd 6:0:0:0: [sdb] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB) [151088.608130] sd 6:0:0:0: [sdb] Write Protect is off [151088.608149] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 [151088.611180] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [151088.632405] sdb: sdb1 [151088.637930] sd 6:0:0:0: [sdb] Attached SCSI removable disk [151129.666614] usb 2-3.2: new high-speed USB device number 6 using ehci-pci [152047.595383] ------------[ cut here ]------------ [152047.595438] WARNING: at drivers/usb/host/ehci-hcd.c:1054 ehci_endpoint_reset+0x113/0x120 [ehci_hcd]() [152047.595444] Hardware name: p2-1120 [152047.595449] clear_halt for a busy endpoint [152047.595453] Modules linked in: usb_storage tun nls_cp437 vfat fat fuse joydev acpi_cpufreq mperf evdev kvm radeon ttm microcode drm_kms_helper pcspkr psmouse drm snd_hda_codec_realtek snd_hda_intel serio_raw sp5100_tco i2c_piix4 snd_hda_codec k10temp i2c_algo_bit snd_hwdep snd_pcm i2c_core atl1c snd_page_alloc snd_timer snd soundcore button video processor vboxnetadp(O) vboxdrv(O) ext4 crc16 jbd2 mbcache hid_generic usbhid hid sr_mod cdrom sd_mod ahci libahci ohci_hcd ehci_pci ehci_hcd libata usbcore scsi_mod usb_common [152047.595550] Pid: 30474, comm: pool Tainted: G O 3.8.6-1-ARCH #1 [152047.595556] Call Trace: [152047.595574] [<ffffffff81057190>] warn_slowpath_common+0x70/0xa0 [152047.595584] [<ffffffff8105720c>] warn_slowpath_fmt+0x4c/0x50 [152047.595612] [<ffffffffa0043645>] ? usb_control_msg+0xe5/0x130 [usbcore] [152047.595628] [<ffffffffa0178cf3>] ehci_endpoint_reset+0x113/0x120 [ehci_hcd] [152047.595650] [<ffffffffa00422b5>] usb_hcd_reset_endpoint+0x25/0x70 [usbcore] [152047.595670] [<ffffffffa0044558>] usb_reset_endpoint+0x28/0x40 [usbcore] [152047.595690] [<ffffffffa00445de>] usb_clear_halt+0x6e/0x80 [usbcore] [152047.595710] [<ffffffffa004f305>] usbdev_do_ioctl+0xba5/0x1050 [usbcore] [152047.595730] [<ffffffffa004f7de>] usbdev_ioctl+0xe/0x20 [usbcore] [152047.595741] [<ffffffff81199775>] do_vfs_ioctl+0x2e5/0x4d0 [152047.595750] [<ffffffff811999e1>] sys_ioctl+0x81/0xa0 [152047.595762] [<ffffffff814c735d>] system_call_fastpath+0x1a/0x1f [152047.595769] ---[ end trace a5c78ffe5f331d3c ]--- [152047.599593] usb 2-3.2: usbfs: process 30321 (events) did not claim interface 0 before use [152051.469939] sdb: detected capacity change from 4004511744 to 0 [152062.408991] usb 2-3.2: USB disconnect, device number 6 Here's lsusb -v: Bus 002 Device 003: ID 2109:2812 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 1 Single TT bMaxPacketSize0 64 idVendor 0x2109 idProduct 0x2812 bcdDevice 85.70 iManufacturer 0 iProduct 1 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Bus 004 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc31c Keyboard K120 for Business bcdDevice 64.00 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 3 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 90mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 2 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 65 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 2 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 159 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 255 Bus 004 Device 003: ID 047d:1020 Kensington Expert Mouse Trackball Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x047d Kensington idProduct 0x1020 Expert Mouse Trackball bcdDevice 1.00 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 52 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 10 Bus 005 Device 002: ID 09ae:2009 Tripp Lite Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x09ae Tripp Lite idProduct 0x2009 bcdDevice 0.10 iManufacturer 3 iProduct 1 iSerial 2 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 590 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 40 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 3.08 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 3.08 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 3.08 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice 3.08 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice 3.08 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice 3.08 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice 3.08 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Bus 002 Device 004: ID 2109:2812 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 1 Single TT bMaxPacketSize0 64 idVendor 0x2109 idProduct 0x2812 bcdDevice 85.70 iManufacturer 0 iProduct 1 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Bus 002 Device 005: ID 0781:5575 SanDisk Corp. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0781 SanDisk Corp. idProduct 0x5575 bcdDevice 1.26 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 200mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 I believe, based on idVendor, that the device I'm looking for is the last of these. What am I missing? Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRZ1guAAoJELJhbl/uPb4SJJgP/i+4ROaYXip28jouYeOscXJl TjCzkaIQt/Pe+Q87iuCpUy57Rw0t4olh0mvBGcQMC5Bz2w+mnb5v0UyI+SFERmF/ RipSjecrrK5FXNsTzVMSyPqcXmLQcscV7uqJWIEcFDug0C3O1g14QJESzIcn4z8y C0kT1KavDYZcd07c3o+XlM5UwurWlDiacn4wXVlxZBy75m+jzBLyJiGR4sxHGuZe S0lZ99Aci5EuJQr5fEWxedn5VYdcdsrf3YCYL5cOdru1EaIgCvjDVLFanUS4FZ9S YSsQkbERvOu6RDrUgYLm/hbptEXZgC/4erVpzpUYqIwx30u7W4bFy8A9VqN4UrSj 3AWRGkYNv57mq424PsEDuCHIIpMC6pQMaNhWTkzIeCP5AnKoZS4xVE43McFSbGoy ZK4d05oB1ySdWxOnhn5oiNGrkCT6FmM/x7bgktJCOW4fkRD7yqRaDoquJNLWo+qT 4QPszMxATh2wQV0BUPmMkb/t9AurSFR7FhCIw0BMKxknUg3wOU52ixs4QbdrNFqs iu3ABoc67CjD39JfWYipJKoab6RfjPRtj4qHFtiTZVobQKZN1wqZz73Sg+W/ZSe7 Jc4wePyoJEhZl21RFGiPWWNlEv9dcY3aY0PB6UUsLVYAX4SmPRyQT7JZcOA+GilU GMP775NbA+F1K4UBngLU =Ceq5 -----END PGP SIGNATURE-----
On Fri, Apr 12, 2013 at 2:41 AM, David Benfell <benfell@parts-unknown.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I can't believe I'm having trouble with this. I'm trying to follow the directions at https://wiki.archlinux.org/index.php/USB_Installation_Media
Specifically:
dd bs=4M if=/path/to/archlinux.iso of=/dev/sdx
Which I translate to:
sudo dd bs=4M if=Downloads/archlinux-2013.04.01-dual.iso of=/dev/sdb dd: failed to open ‘/dev/sdb’: No medium found
And you see the result. /dev/sdb does indeed exist and is writable. It's a brand new 4GB flash drive and I moved the crap that came preloaded on it somewhere else before dismounting it. Here's the dmesg snippet:
[151086.251674] usb 2-3.1.4: new high-speed USB device number 5 using ehci-pci [151087.600267] Initializing USB Mass Storage driver... [151087.600770] scsi6 : usb-storage 2-3.1.4:1.0 [151087.601106] usbcore: registered new interface driver usb-storage [151087.601112] USB Mass Storage support registered. [151088.603391] scsi 6:0:0:0: Direct-Access SanDisk Cruzer Glide 1.26 PQ: 0 ANSI: 5 [151088.606083] sd 6:0:0:0: [sdb] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB) [151088.608130] sd 6:0:0:0: [sdb] Write Protect is off [151088.608149] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 [151088.611180] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [151088.632405] sdb: sdb1 [151088.637930] sd 6:0:0:0: [sdb] Attached SCSI removable disk [151129.666614] usb 2-3.2: new high-speed USB device number 6 using ehci-pci [152047.595383] ------------[ cut here ]------------ [152047.595438] WARNING: at drivers/usb/host/ehci-hcd.c:1054 ehci_endpoint_reset+0x113/0x120 [ehci_hcd]() [152047.595444] Hardware name: p2-1120 [152047.595449] clear_halt for a busy endpoint [152047.595453] Modules linked in: usb_storage tun nls_cp437 vfat fat fuse joydev acpi_cpufreq mperf evdev kvm radeon ttm microcode drm_kms_helper pcspkr psmouse drm snd_hda_codec_realtek snd_hda_intel serio_raw sp5100_tco i2c_piix4 snd_hda_codec k10temp i2c_algo_bit snd_hwdep snd_pcm i2c_core atl1c snd_page_alloc snd_timer snd soundcore button video processor vboxnetadp(O) vboxdrv(O) ext4 crc16 jbd2 mbcache hid_generic usbhid hid sr_mod cdrom sd_mod ahci libahci ohci_hcd ehci_pci ehci_hcd libata usbcore scsi_mod usb_common [152047.595550] Pid: 30474, comm: pool Tainted: G O 3.8.6-1-ARCH #1 [152047.595556] Call Trace: [152047.595574] [<ffffffff81057190>] warn_slowpath_common+0x70/0xa0 [152047.595584] [<ffffffff8105720c>] warn_slowpath_fmt+0x4c/0x50 [152047.595612] [<ffffffffa0043645>] ? usb_control_msg+0xe5/0x130 [usbcore] [152047.595628] [<ffffffffa0178cf3>] ehci_endpoint_reset+0x113/0x120 [ehci_hcd] [152047.595650] [<ffffffffa00422b5>] usb_hcd_reset_endpoint+0x25/0x70 [usbcore] [152047.595670] [<ffffffffa0044558>] usb_reset_endpoint+0x28/0x40 [usbcore] [152047.595690] [<ffffffffa00445de>] usb_clear_halt+0x6e/0x80 [usbcore] [152047.595710] [<ffffffffa004f305>] usbdev_do_ioctl+0xba5/0x1050 [usbcore] [152047.595730] [<ffffffffa004f7de>] usbdev_ioctl+0xe/0x20 [usbcore] [152047.595741] [<ffffffff81199775>] do_vfs_ioctl+0x2e5/0x4d0 [152047.595750] [<ffffffff811999e1>] sys_ioctl+0x81/0xa0 [152047.595762] [<ffffffff814c735d>] system_call_fastpath+0x1a/0x1f [152047.595769] ---[ end trace a5c78ffe5f331d3c ]--- [152047.599593] usb 2-3.2: usbfs: process 30321 (events) did not claim interface 0 before use [152051.469939] sdb: detected capacity change from 4004511744 to 0 [152062.408991] usb 2-3.2: USB disconnect, device number 6
Googling a bit, I found this: http://ubuntuforums.org/showthread.php?t=1273928 Also looking at the SanDisk "Cruzer Glide" product page, it seems SanDisk thumbdrives often have various fancy features that rely on firmware support (the page notes that "some capacity is not available for data storage.") It's possible the drive just can't be used for anything but what SanDisk intended (and support will just tell you that "Linux is not supported by SanDisk.") Trying to manipulate the MBR or any other sector outside the main data partition immediately causes the drive to shut down, maybe to protect its functionality. At least I believe that's what I'm seeing here.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/11/2013 6:00 PM, Jan Alexander Steffens wrote:
It's possible the drive just can't be used for anything but what SanDisk intended (and support will just tell you that "Linux is not supported by SanDisk.") Trying to manipulate the MBR or any other sector outside the main data partition immediately causes the drive to shut down, maybe to protect its functionality. At least I believe that's what I'm seeing here.
This clearly falls within the range of 'gotta be something idiotic', just different from what I expected. My guess is you've nailed it. I guess I'll head back to Best Buy for a different brand. Thanks! - -- David Benfell <benfell@parts-unknown.org> <dbenfell@saybrook.edu> See https://parts-unknown.org/node/2 for GnuPG (the attachment you don't understand) information. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRZ2rCAAoJELJhbl/uPb4SVJMP/3Rd5lylXYJK+5tLYRuXv6ET qa0r28OOP2BfSsPFkhxcjCh2lLH2TcXkDhKKTHr+FQMjXSrQbRMaxOU1IdHq4mHP eITleXo5Sr/TWi8StBK1XdZxW6+HRxhnoMh5t1JN633dAgyykC1iEQ2RUl6/Tp2f uBcc6rYpaJMVlyzzzYYORe1VlsfrrjcT8EapouIbs0tFJ7nrkfJjzECWQo+RcfaR 0mEyQ9xUkmQHs8n/uc6HCFamO9R7iqnehnYTmGWmNkrCMPDIZAl3m5UqMCit8wAX 6/K46YqaU55S4WTmT67CkkEk7ois+XnUufJZ1KDr6FvQXJM9wtfc/V56DdDMQEb2 zo1oGXY+roRFs5t5J4F7xgvCSROxyqgIkuQk/xyTamGSrK5Ki7l8kp6JJgQ0P4NW 5C2axjxGnhMpTLrhN3o+JZXqvC66oWIzidj5qx6TrMjLrTmTMjtoLjt8QFNjEsw8 +Pry5oG29H6jeis5oRSFmWCUjW1C1QvrTPc4h/6OaKqcYXim/YVI45R5PYNROddA P4OAh88KMOiZv5DzK7zoIuc4taC8zfnSiQ20zPcnWvXfWT0lgVM1Hu27UmkZggvm 2XnB5Lhcy/uRtkVQYavPzfKNu1Fe6zb/RiFXaDgRY+IiIo46CejWhq2JF+HGyBGa QQ/+jInU586+bTHkfniH =9vmY -----END PGP SIGNATURE-----
On 12 April 2013 10:00, David Benfell <benfell@parts-unknown.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 4/11/2013 6:00 PM, Jan Alexander Steffens wrote:
It's possible the drive just can't be used for anything but what SanDisk intended (and support will just tell you that "Linux is not supported by SanDisk.") Trying to manipulate the MBR or any other sector outside the main data partition immediately causes the drive to shut down, maybe to protect its functionality. At least I believe that's what I'm seeing here.
This clearly falls within the range of 'gotta be something idiotic', just different from what I expected. My guess is you've nailed it.
I guess I'll head back to Best Buy for a different brand.
Hi David Before you do that, did you try using the tool mentioned in the Ubuntu thread to remove unwanted firmware partitions, if any? If not, you may want to format the entire thing with an HP legacy formatting tool.¹ I've used it successfully in the past to reclaim full functionality from such stubborn vendor-locked storage devices that won't let you manipulate them with standard tools. Worth a try, I say. ¹ http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Form... -- GPG/PGP ID: C0711BF1
On 4/12/2013 11:23 AM, Ray Rashif wrote:
Before you do that, did you try using the tool mentioned in the Ubuntu thread to remove unwanted firmware partitions, if any? If not, you may want to format the entire thing with an HP legacy formatting tool.¹ I've used it successfully in the past to reclaim full functionality from such stubborn vendor-locked storage devices that won't let you manipulate them with standard tools. Worth a try, I say. ¹ http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Form... -- GPG/PGP ID: C0711BF1 I hadn't.
The frustration on that thread is pretty intense, and apparently for good reason. The tool ran, looked for all the world like it had done something, but then when I got back to the Arch Linux wiki entry, I got the same error. Gee, this is frustrating. Is this the new thing, now, that you can't use thumb drives--apparently any thumb drives--to boot a system?
On Fri, 12 Apr 2013 03:00:28 +0200 Jan Alexander Steffens <jan.steffens@gmail.com> wrote:
On Fri, Apr 12, 2013 at 2:41 AM, David Benfell <benfell@parts-unknown.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I can't believe I'm having trouble with this. I'm trying to follow the directions at https://wiki.archlinux.org/index.php/USB_Installation_Media
Specifically:
dd bs=4M if=/path/to/archlinux.iso of=/dev/sdx
Which I translate to:
sudo dd bs=4M if=Downloads/archlinux-2013.04.01-dual.iso of=/dev/sdb dd: failed to open ‘/dev/sdb’: No medium found
And you see the result. /dev/sdb does indeed exist and is writable. It's a brand new 4GB flash drive and I moved the crap that came preloaded on it somewhere else before dismounting it. Here's the dmesg snippet:
[151086.251674] usb 2-3.1.4: new high-speed USB device number 5 using ehci-pci [151087.600267] Initializing USB Mass Storage driver... [151087.600770] scsi6 : usb-storage 2-3.1.4:1.0 [151087.601106] usbcore: registered new interface driver usb-storage [151087.601112] USB Mass Storage support registered. [151088.603391] scsi 6:0:0:0: Direct-Access SanDisk Cruzer Glide 1.26 PQ: 0 ANSI: 5 [151088.606083] sd 6:0:0:0: [sdb] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB) [151088.608130] sd 6:0:0:0: [sdb] Write Protect is off [151088.608149] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00 [151088.611180] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [151088.632405] sdb: sdb1 [151088.637930] sd 6:0:0:0: [sdb] Attached SCSI removable disk [151129.666614] usb 2-3.2: new high-speed USB device number 6 using ehci-pci [152047.595383] ------------[ cut here ]------------ [152047.595438] WARNING: at drivers/usb/host/ehci-hcd.c:1054 ehci_endpoint_reset+0x113/0x120 [ehci_hcd]() [152047.595444] Hardware name: p2-1120 [152047.595449] clear_halt for a busy endpoint [152047.595453] Modules linked in: usb_storage tun nls_cp437 vfat fat fuse joydev acpi_cpufreq mperf evdev kvm radeon ttm microcode drm_kms_helper pcspkr psmouse drm snd_hda_codec_realtek snd_hda_intel serio_raw sp5100_tco i2c_piix4 snd_hda_codec k10temp i2c_algo_bit snd_hwdep snd_pcm i2c_core atl1c snd_page_alloc snd_timer snd soundcore button video processor vboxnetadp(O) vboxdrv(O) ext4 crc16 jbd2 mbcache hid_generic usbhid hid sr_mod cdrom sd_mod ahci libahci ohci_hcd ehci_pci ehci_hcd libata usbcore scsi_mod usb_common [152047.595550] Pid: 30474, comm: pool Tainted: G O 3.8.6-1-ARCH #1 [152047.595556] Call Trace: [152047.595574] [<ffffffff81057190>] warn_slowpath_common+0x70/0xa0 [152047.595584] [<ffffffff8105720c>] warn_slowpath_fmt+0x4c/0x50 [152047.595612] [<ffffffffa0043645>] ? usb_control_msg+0xe5/0x130 [usbcore] [152047.595628] [<ffffffffa0178cf3>] ehci_endpoint_reset+0x113/0x120 [ehci_hcd] [152047.595650] [<ffffffffa00422b5>] usb_hcd_reset_endpoint+0x25/0x70 [usbcore] [152047.595670] [<ffffffffa0044558>] usb_reset_endpoint+0x28/0x40 [usbcore] [152047.595690] [<ffffffffa00445de>] usb_clear_halt+0x6e/0x80 [usbcore] [152047.595710] [<ffffffffa004f305>] usbdev_do_ioctl+0xba5/0x1050 [usbcore] [152047.595730] [<ffffffffa004f7de>] usbdev_ioctl+0xe/0x20 [usbcore] [152047.595741] [<ffffffff81199775>] do_vfs_ioctl+0x2e5/0x4d0 [152047.595750] [<ffffffff811999e1>] sys_ioctl+0x81/0xa0 [152047.595762] [<ffffffff814c735d>] system_call_fastpath+0x1a/0x1f [152047.595769] ---[ end trace a5c78ffe5f331d3c ]--- [152047.599593] usb 2-3.2: usbfs: process 30321 (events) did not claim interface 0 before use [152051.469939] sdb: detected capacity change from 4004511744 to 0 [152062.408991] usb 2-3.2: USB disconnect, device number 6
Googling a bit, I found this: http://ubuntuforums.org/showthread.php?t=1273928
Also looking at the SanDisk "Cruzer Glide" product page, it seems SanDisk thumbdrives often have various fancy features that rely on firmware support (the page notes that "some capacity is not available for data storage.")
It's possible the drive just can't be used for anything but what SanDisk intended (and support will just tell you that "Linux is not supported by SanDisk.") Trying to manipulate the MBR or any other sector outside the main data partition immediately causes the drive to shut down, maybe to protect its functionality. At least I believe that's what I'm seeing here.
Hi Those SanDisk drive are a real pain you can use them but you are going to have to fdisk it first there is stuff on there that stops Linux dead in it's tracks i have several of them the 4Gb ones (came at the right price) . I used fdisk on them then formatted them vfat for use in the car work fine now . Pete . -- Linux 7-of-9 3.8.6-1-ARCH #1 SMP PREEMPT Sat Apr 6 07:27:01 CEST 2013 x86_64 GNU/Linux
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/12/2013 12:32 AM, P .NIKOLIC wrote:
Hi
Those SanDisk drive are a real pain you can use them but you are going to have to fdisk it first there is stuff on there that stops Linux dead in it's tracks i have several of them the 4Gb ones (came at the right price) .
I used fdisk on them then formatted them vfat for use in the car work fine now .
When I saw this, I couldn't believe it. A little fdisk action? That's all this takes? Well, almost. Yes, it booted off the thumb drive. I didn't get the DOS label right. And there's obviously something I'm not understanding about how this comes up, because the shell was actually kinda familiar, which is not what I was expecting. I should explain that there's a change from when I originally posed this question. I realized--or at least the way I understood this page <https://wiki.archlinux.org/index.php/USB_Installation_Media>--I needed to use the slightly more complicated method involving the syslinux bootloader. This is a UEFI system--and I don't think it will boot anything else--so I also copied the entire extracted ISO tree onto the thumb drive, meaning especially to include EFI. But the boot fell back to the interactive prompt because /dev/disk/by-label/ARCH_201304 didn't appear. dosfslabel is my friend. Whatever problems I may yet encounter with this install, they will be different problems. Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRaPrIAAoJELJhbl/uPb4SHuMP/0BFABnUBUT42ABamfS+hPUs 8rZ34P5vePhIsmEr4e2UDEBFBu2H666GvmO9MCNvraXAIVbmszrJEjikkaFMkroJ 9+u9fooXo2BPJDub4dThop6Z4f7l4Wrxw1glgIySM8MZXbOSx0EPuiWrdOa2SzkN i9VEtR/JG0WGFrhVLcdxPEBHFdoBNwFnVDyIcoiuuvj1UgbXc86mPnEd73Pr+Xpu pQkY1NxkWYRKnjpVt8RZbyE/187OnJueFl1oIi3fOzGA6NbITxfO6vfxmhGfJHTG 8cmFfi4v541bqPvRJiduUD0JJ6s/bj9hYDICkGIFr5yiHXBnSqubfVLVAv/kyhrM 23O7YtPi0asqstKv1XSGIO0ci8GhVKKpD2JHM4eR7cDBUhvh57sVzR1RQEVjfWN/ nWzqtaSLwBaz7jT3JyJDIGOZkl2rrdYeXeptGCv1h2xKJ4H1yzQWWh1qVMCDQ58O kjQSHJqLHXL4CN35Ec9X8nt22WxJQaEBy4oUeFNoEu6w4mBUHJcVNslivRugb/iO /7bXccwddCTe0acxD6th/jv9K6xQBMMfrXoUzoaZJGCJsxWo2YUUx3nMaGidwBWz 2Z4ASZk2Bu7qPJs6sumtWPVmU8vpIaKp8J0o5ymBNijnGcwP3Wz95I3q4GzSrQEt bI+ZCERRkDBGqVlhrjFj =7kDy -----END PGP SIGNATURE-----
On 13 April 2013 14:27, David Benfell <benfell@parts-unknown.org> wrote:
On 04/12/2013 12:32 AM, P .NIKOLIC wrote:
Hi
Those SanDisk drive are a real pain you can use them but you are going to have to fdisk it first there is stuff on there that stops Linux dead in it's tracks i have several of them the 4Gb ones (came at the right price) .
I used fdisk on them then formatted them vfat for use in the car work fine now .
When I saw this, I couldn't believe it. A little fdisk action? That's all this takes?
Well, almost. Yes, it booted off the thumb drive. I didn't get the DOS label right. And there's obviously something I'm not understanding about how this comes up, because the shell was actually kinda familiar, which is not what I was expecting.
I should explain that there's a change from when I originally posed this question. I realized--or at least the way I understood this page <https://wiki.archlinux.org/index.php/USB_Installation_Media>--I needed to use the slightly more complicated method involving the syslinux bootloader. This is a UEFI system--and I don't think it will boot anything else--so I also copied the entire extracted ISO tree onto the thumb drive, meaning especially to include EFI.
But the boot fell back to the interactive prompt because /dev/disk/by-label/ARCH_201304 didn't appear.
dosfslabel is my friend.
Whatever problems I may yet encounter with this install, they will be different problems.
It looks like your thumbdrive wasn't as stubborn as was initially suspected. Recreating the partition table made it work. What you're facing now is an issue with configuration. My personal favourite UFD method is https://wiki.archlinux.org/index.php/USB_Installation_Media#Without_overwrit... -- with UUID. I dislike hardcoding label names as they are likely to change, but UUIDs are static (barring reformats). Anyway, if you choose to stick with labels, you can also use mlabel for FAT.¹ ¹ https://wiki.archlinux.org/index.php/Persistent_block_device_naming#by-label -- GPG/PGP ID: C0711BF1
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/13/2013 12:43 AM, Rashif Ray Rahman wrote:
It looks like your thumbdrive wasn't as stubborn as was initially suspected. Recreating the partition table made it work. What you're facing now is an issue with configuration.
My personal favourite UFD method is https://wiki.archlinux.org/index.php/USB_Installation_Media#Without_overwrit...
- -- with UUID. I dislike hardcoding label names as they are likely to
change, but UUIDs are static (barring reformats).
Anyway, if you choose to stick with labels, you can also use mlabel for FAT.¹
¹ https://wiki.archlinux.org/index.php/Persistent_block_device_naming#by-label
I tried mlabel. It's apparently part of the mtools package--which is an additional package--whereas I already had dosfslabel on my system. But worse, mlabel apparently failed silently, where dosfslabel griped that "There are differences between boot sector and its backup," but this was apparently unimportant, at least for my purposes. Thanks! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRaRQmAAoJELJhbl/uPb4SisEP/3Kkoyp2B7b6mu03de4rjd3D MwcOTdb4iPM9eBWMQUgfuLhNCClnL6eWra/C39nnSHckD13xW0ZAjqmDsnWOkBtc Z+yy6Fud28KWdMLauorbPppUIiwloQpL9Q+XdsLSVyxqC3F3z74hkQodob7fFYUA tmxB5bagJNhsSCxLeI78kuOylfflQUpbV1Z63OGwbaau1UhF0B6qp+SdD+KptqpB 3TF7/Afbdi6qqnQiebxXRd38LM9QiI+UT6iuU8cymsDyCL16dCAoEFJIwtfpdAzZ CcO14KdOs7drVU4wFbFh7MBHt6owg4JHiHKQKuAIXA0kOK7dJjsvLTleMrK0BVNu aSkIdHDsxINDhJxXzosxbcxTeiA2O8Yw7gHBRZPW+DEzHM7/9L1bchoSwrwbM70o Oo82RSPj18eeejPslIYkbQrWG7DFWwX7XG80PKaiM+QtdjGKxwTHvnGSk3eWfspy rI2D9OEJisSwYAfx5raMo+m/S8WKdTd0lqMdvbk8ABD8CLrEJUJhCuqjCi7t+DZM qv4t2wYdv1qJpGdKi07ys5JJt5sC2aj1kTdfo7iPfXv4DmBkPLiCkvrsVdktDdp8 XZ/8YgZ0EdWl6K64PnXsc1ViztY1jrZJIQ2yXLveGI0VO0IXnnpf9pgmznCbFGMq SzP5TxYQvC0dCcYGczIz =pXA1 -----END PGP SIGNATURE-----
According to Rashif Ray Rahman: # -- with UUID. I dislike hardcoding label names as they are likely to # change, but UUIDs are static (barring reformats). I greatly prefer labels, because they are human readable, chosen by the end user, and unless I'm totally misunderstanding how they work, only change if the end-user manually changes them. The same label can even be reused after a reformat, as long as it is specified exactly as it appeard before the old filesystem was deleted. On the other hand, UUID's are only computer readable, change on every format, and make absolutely no sense to the end user when trying to figure out what drive or partition contains what filesystem. The only problem I see with using labels is some confusion that could possibly arise if you have a thumb drive that contains a filesystem labeled archlinux inserted into a computer with a hard drive that also contains a filesystem labeled archlinux. There would indeed be a host of problems when /dev/disk/by-label/archlinux probably points to the wrong device or the system doesn't know which device to symlink. However, in that case, when creating the thumb drive and labeling its filesystem, it is better to name it archthumb or another name that is equally recognizable, but won't get confused with other filesystems on the machine. Sure I could use UUID's here, but then if I need to go back and read /etc/fstab and see something very long and unrecognizable, the chance of editing something that will make my system completely unbootable increases greatly. please correct me if I have missed something regarding automatic or scripted changes to disk labels other than end-user interactions with disk labeling tools or filesysten utilities. BTW, the first thing I do as soon as I purchase any storage device, whether it's a thumb drive, a memory card, an external hard drive or anything else, is to use a labeling tool to give the filesystem a recognizable, human readable name. There is nothing I like less than trying to move files between FE20-8ED3 and C2FD-DE3B, which are both 8GB drives, and both contain similar directory structures. It is much easier to move the same files between human readable disk labels like "OLD-PC" and "NEW-PC," although the labels I mention here are only arbitrary names. Normally I use something that describes the device on which the storage will be used most, or a brief name to indicate the files that are on the disk. ~Kyle http://kyle.tk/ -- "Kyle? ... She calls her cake, Kyle?" Out of This World, season 2 episode 21 - "The Amazing Evie"
On 14 April 2013 12:13, Kyle <kyle@gmx.ca> wrote:
According to Rashif Ray Rahman: # -- with UUID. I dislike hardcoding label names as they are likely to # change, but UUIDs are static (barring reformats).
I greatly prefer labels, because they are human readable, chosen by the end user, and unless I'm totally misunderstanding how they work, only change if the end-user manually changes them. The same label can even be reused after a reformat, as long as it is specified exactly as it appeard before the old filesystem was deleted. On the other hand, UUID's are only computer readable, change on every format, and make absolutely no sense to the end user when trying to figure out what drive or partition contains what filesystem.
Kyle, in general, I agree with you. From a usability perspective, long strings of alphanumeric characters to identify something are just a total PITA. Using UUIDs is simply a habit I incurred from having to swap disks and systems around, where I am allowed to "deploy once and forget". In my experience, it has solved more problems. But, to each her own, as every use case is different. I was just suggesting an alternative, which may or may not work well for the use case. -- GPG/PGP ID: C0711BF1
According to Rashif Ray Rahman: # Using UUIDs is simply a habit I incurred from having to swap disks and # systems around, where I am allowed to "deploy once and forget". In that use case, I can see how UUID's may possibly be useful, especially if you work with many systems and swap disks around to the point you forget what label you used. In this case, it is probably just as easy to use UUID's as labels, since upon running genfstab, you can simply use the -U option. If you never have to look at /etc/fstab or differentiate between filesystems in a human readable way, it could definitely make things somewhat simpler. ~Kyle http://kyle.tk/ -- "Kyle? ... She calls her cake, Kyle?" Out of This World, season 2 episode 21 - "The Amazing Evie"
participants (6)
-
David Benfell
-
Jan Alexander Steffens
-
Kyle
-
P .NIKOLIC
-
Rashif Ray Rahman
-
Ray Rashif