On Sunday, June 26, 2016 at 12:50:52 PM UTC+2, Marek Marczykowski-Górecki wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Sun, Jun 26, 2016 at 06:45:50AM -0400, Chris Laprise wrote: > > More info, Marek... > > > > When I try to scan the /dev/sdb device with partx, it says the device is not > > readable or not valid device. > > > > When I plug in another USB stick, the partitions are enumerated as /dev/sdc1 > > etc. but they cannot be mounted (devices are unreadable). > > > > From dmesg, these errors occur right before the /dev/root error and > > stoppage: > > > > scsi 6:0:0:0: Direct-Access Samsung Flash Drive 1100 PQ: 0 ANSI: 6 > > sd 6:0:0:0: alua: supports implicit and explicit TPGS > > sd 6:0:0:0: alua: No target port descriptors found > > sd 6:0:0:0: alua: Attach failed (-22) > > sd 6:0:0:0: Failed to add device handler: -22 > > sd 6:0:0:0: [sdb] ...several lines with drive size and flags... > > (trace dump occurs) > > > > This thread says disabling 'alua' module (scsi_dh_alua?) can resolve the > > issue: > > https://www.linuxquestions.org/questions/linux-hardware-18/corsair-flash-voyager-slider-usb-memory-stick-fails-to-attach-4175572901/ > > > > Should 'alua' even be present? AFAIK it is for large infrastructure. Fedora > > installer does not seem to enable it by default. > > Indeed looks like something unnecessary on desktop system. > Try adding this to kernel command line: > > rd.driver.blacklist=scsi_dh_alua > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJXb7OEAAoJENuP0xzK19csmkcH+QG0fPrTWpyO28RywNYMB9EW > az/7wSFS6zE5vzy3A7c2wHWNmS/51V8KsI0CfexCBOXBsghzqyGp3ZvFuzcdoPHc > QsG7Ut17HcNOtEiPHj4GkKLb6+KTYVVfWPCUgwQqhdE6SCcU65/5ofTBlvOLvv72 > GfhkC+XvBFDSByRkKV28rxS2AAVRqeLfnE3GRpe8QSZ8MXtwSXBD05YEGq8k0MGH > GYt4mWrcnS45kTfkZkguL3KwPmrzSoh5QnNBG4+633aKPUpgZKcyFtAIF6OKlgZT > Zu6LQ6oSMp5n/vJIVdXC1mM55RJ2dE61NnuqWV01mzTwTP4jWkXM+dlcDuCnAtM= > =+PXY > -----END PGP SIGNATURE-----
I am having the same problem. I am trying to apply this boot option, and test if it works. But, how do you do it? Sorry this question might be too basic. Editing the boot command in Grub shows "...placeholder qubes-verbose" and there options are not accepted. I don't see any way of editing "qubes-verbose" inside grub command line. I have been googling around and reading Grub documentation and there is no trace of such functionality. Also mounting and editing the file on the USB seems not possible because it is a read only ISO filesystem. Surely many qubes users will have to tune a boot parameter at installation time. so, there must be a simple way to do this. I fear I might have to build a patched ISO for this. Surely there must be something I am missing. how can I test this easily? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/48f2603a-4a6a-4760-9266-e83a9054d55a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
