[opensuse] Why (as the only one) can not openSUSE work with large USB drive?
I have recently bought 5 TB Seagate Expansion desktop hard drive http://www.seagate.com/www-content/product-content/expansion-fam/expansion-e... Basically, it is just ordinary 3.5“ HDD connected to the computer via USB 3. openSUSE 13.2 and Leap 42.1 (tested on several computers and DEs). fdisk, gdisk, parted, YaST partition module do not see it. dmesg reports some errors about uas module. I added uas to /etc/modprobe.d/50- blacklist.conf to blacklist it and I regenerated mkinitrd, but it doesn't prevent the module from load and it doesn't work. When I unplug the drive, system crashes. I tried LIVE CDs of Ubuntu, Fedora a openSUSE 13.1 promo DVD and they worked fine. The logs: https://bugzilla.opensuse.org/attachment.cgi?id=655072 So I wonder what can be wrong on two installed systems (13.2) and one fresh install of Leap. As I saw working live CDs, sometimes uas module is loaded, sometimes not, so that I'm not sure if this really is the case... I reported bug https://bugzilla.opensuse.org/show_bug.cgi?id=954138 about that, but I'd appreciate at least some workaround to quickly fix it before there is some real solution. Any ideas what could be wrong? Thanks, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On Tue, Nov 10, 2015 at 11:47 AM, Vojtěch Zeisek <vojtech.zeisek@opensuse.org> wrote:
I have recently bought 5 TB Seagate Expansion desktop hard drive http://www.seagate.com/www-content/product-content/expansion-fam/expansion-e... Basically, it is just ordinary 3.5“ HDD connected to the computer via USB 3. openSUSE 13.2 and Leap 42.1 (tested on several computers and DEs). fdisk, gdisk, parted, YaST partition module do not see it. dmesg reports some errors about uas module. I added uas to /etc/modprobe.d/50- blacklist.conf to blacklist it and I regenerated mkinitrd, but it doesn't prevent the module from load and it doesn't work. When I unplug the drive, system crashes. I tried LIVE CDs of Ubuntu, Fedora a openSUSE 13.1 promo DVD and they worked fine.
Did you compare which kernel modules are loaded in this case? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Út 10. listopadu 2015 11:53:02, Andrei Borzenkov napsal(a):
On Tue, Nov 10, 2015 at 11:47 AM, Vojtěch Zeisek <vojtech.zeisek@opensuse.org> wrote:
I have recently bought 5 TB Seagate Expansion desktop hard drive http://www.seagate.com/www-content/product-content/expansion-fam/expansion -external/en-us/docs/expansion-desktop-hard-drive-ds1843-2-1502gb.pdf Basically, it is just ordinary 3.5“ HDD connected to the computer via USB 3. openSUSE 13.2 and Leap 42.1 (tested on several computers and DEs). fdisk, gdisk, parted, YaST partition module do not see it. dmesg reports some errors about uas module. I added uas to /etc/modprobe.d/50- blacklist.conf to blacklist it and I regenerated mkinitrd, but it doesn't prevent the module from load and it doesn't work. When I unplug the drive, system crashes. I tried LIVE CDs of Ubuntu, Fedora a openSUSE 13.1 promo DVD and they worked fine.
Did you compare which kernel modules are loaded in this case?
No, I was checking for uas as this was reported in openSUSE /Var/log/messages as the failing one. Which module should take care about this? If not uas, why should it be loaded (and fail) in this case? -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
On Tue, Nov 10, 2015 at 12:01 PM, Vojtěch Zeisek <vojtech.zeisek@opensuse.org> wrote:
Dne Út 10. listopadu 2015 11:53:02, Andrei Borzenkov napsal(a):
On Tue, Nov 10, 2015 at 11:47 AM, Vojtěch Zeisek <vojtech.zeisek@opensuse.org> wrote:
I have recently bought 5 TB Seagate Expansion desktop hard drive http://www.seagate.com/www-content/product-content/expansion-fam/expansion -external/en-us/docs/expansion-desktop-hard-drive-ds1843-2-1502gb.pdf Basically, it is just ordinary 3.5“ HDD connected to the computer via USB 3. openSUSE 13.2 and Leap 42.1 (tested on several computers and DEs). fdisk, gdisk, parted, YaST partition module do not see it. dmesg reports some errors about uas module. I added uas to /etc/modprobe.d/50- blacklist.conf to blacklist it and I regenerated mkinitrd, but it doesn't prevent the module from load and it doesn't work. When I unplug the drive, system crashes. I tried LIVE CDs of Ubuntu, Fedora a openSUSE 13.1 promo DVD and they worked fine.
Did you compare which kernel modules are loaded in this case?
No, I was checking for uas as this was reported in openSUSE /Var/log/messages as the failing one. Which module should take care about this? If not uas, why should it be loaded (and fail) in this case?
Why "fail"? You said other distributions worked; so check what module was used in this case. Then we can think about how to use the same module. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Út 10. listopadu 2015 12:10:06, Andrei Borzenkov napsal(a):
On Tue, Nov 10, 2015 at 12:01 PM, Vojtěch Zeisek <vojtech.zeisek@opensuse.org> wrote:
Dne Út 10. listopadu 2015 11:53:02, Andrei Borzenkov napsal(a):
On Tue, Nov 10, 2015 at 11:47 AM, Vojtěch Zeisek <vojtech.zeisek@opensuse.org> wrote:
I have recently bought 5 TB Seagate Expansion desktop hard drive http://www.seagate.com/www-content/product-content/expansion-fam/expans ion -external/en-us/docs/expansion-desktop-hard-drive-ds1843-2-1502gb.pdf Basically, it is just ordinary 3.5“ HDD connected to the computer via USB 3. openSUSE 13.2 and Leap 42.1 (tested on several computers and DEs). fdisk, gdisk, parted, YaST partition module do not see it. dmesg reports some errors about uas module. I added uas to /etc/modprobe.d/50- blacklist.conf to blacklist it and I regenerated mkinitrd, but it doesn't prevent the module from load and it doesn't work. When I unplug the drive, system crashes. I tried LIVE CDs of Ubuntu, Fedora a openSUSE 13.1 promo DVD and they worked fine.
Did you compare which kernel modules are loaded in this case?
No, I was checking for uas as this was reported in openSUSE /Var/log/messages as the failing one. Which module should take care about this? If not uas, why should it be loaded (and fail) in this case?
Why "fail"? You said other distributions worked; so check what module was used in this case. Then we can think about how to use the same module.
If anyone else would have same problem (in near future), solution (for me) was to add usb-storage.quirks=0x0bc2:331a:u in GRUB (press 'e' to edit the arguments and find line starting uefi). Modules loaded by some LIVE CDs are for comparison listed in https://bugzilla.suse.com/attachment.cgi?id=655500 -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
participants (2)
-
Andrei Borzenkov -
Vojtěch Zeisek