Slackware - ARM This forum is for the discussion of Slackware ARM. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
04-13-2023, 04:09 AM
|
#1
|
Member
Registered: Jan 2020
Distribution: Slackware
Posts: 171
Rep: 
|
No USB storage detected on boot
I use RockPro64, trying to do a clean Slackware -current install. If I boot the installer with a Samsung/Kingston SSD drive plugged in via a USB-A 3.0 adapter, `lsblk` does not list my storage block device, or lists it as a 0 byte size. The installer kernel version is 6.1.22.
The problem solves if I re-plug the USB storage after I have booted the installer. If I install the OS having re-plugged the drive, and then boot it, then Slackware complains about missing `/sbin/init` on root device.
All the hardware is genuine, it worked for me when I tried to install Slackware a few months ago.
I followed https://docs.slackware.com/slackware...3399_rockpro64 top-down, including SPI flash.
|
|
|
04-13-2023, 12:39 PM
|
#2
|
Member
Registered: Jan 2020
Distribution: Slackware
Posts: 171
Original Poster
Rep: 
|
Alright, there has to be something wrong about the USB 3.0 to SATA adapter. I tried plugging in a USB 3.0 to sdcard adapter with an SD card in it, and it gets detected at boot.
Last edited by unInstance; 04-13-2023 at 12:46 PM.
|
|
|
04-13-2023, 12:57 PM
|
#3
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,624
|
Quote:
Originally Posted by unInstance
Alright, there has to be something wrong about the USB 3.0 to SATA adapter. I tried plugging in a USB 3.0 to sdcard adapter with an SD card in it, and it gets detected at boot.
|
Some of the adapters aren't particularly robust. I've had at least three of the same type break, and another 4 or so still working.
I've since switched to these separately-powered adapters - this is the one referenced in the install guide.
Btw if you have any issues with waiting for the device to come online (which isn't your issue here, but it may happen in the future as it's happened to me a couple of times):
If you edit the boot loader config:
Code:
/boot/extlinux/extlinux.conf
There's an option 'awaitrootdev' that you can add to the Kernel cmdline. It's all documented in there: the initrd will keep waiting for the storage to come online before proceeding with the boot.
There's a note there that it has no effect if the file system is labeled: it works fine with labels. Fixed for next batch.
Last edited by drmozes; 04-13-2023 at 01:01 PM.
|
|
|
04-14-2023, 02:14 AM
|
#4
|
Member
Registered: Jan 2020
Distribution: Slackware
Posts: 171
Original Poster
Rep: 
|
Quote:
Originally Posted by drmozes
Some of the adapters aren't particularly robust. I've had at least three of the same type break, and another 4 or so still working.
I've since switched to these separately-powered adapters - this is the one referenced in the install guide.
Btw if you have any issues with waiting for the device to come online (which isn't your issue here, but it may happen in the future as it's happened to me a couple of times):
If you edit the boot loader config:
Code:
/boot/extlinux/extlinux.conf
There's an option 'awaitrootdev' that you can add to the Kernel cmdline. It's all documented in there: the initrd will keep waiting for the storage to come online before proceeding with the boot.
There's a note there that it has no effect if the file system is labeled: it works fine with labels. Fixed for next batch.
|
Look, this is me connecting my SSD drive via the USB 3.0 adapter to my amd64 PC:
Code:
[ 539.750454] sd 6:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK
[ 539.750457] sd 6:0:0:0: [sdc] Sense not available.
[ 539.750461] sd 6:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK
[ 539.750463] sd 6:0:0:0: [sdc] Sense not available.
[ 539.750466] sd 6:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
[ 539.750468] sd 6:0:0:0: [sdc] 0-byte physical blocks
[ 539.750471] sd 6:0:0:0: [sdc] Write Protect is off
[ 539.750472] sd 6:0:0:0: [sdc] Mode Sense: 00 00 00 00
[ 539.750475] sd 6:0:0:0: [sdc] Asking for cache data failed
[ 539.750476] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 539.750478] sd 6:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes)
[ 539.750480] sd 6:0:0:0: [sdc] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
[ 539.750774] sd 6:0:0:0: [sdc] Attached SCSI disk
[ 539.907615] udevd[3958]: inotify_add_watch(6, /dev/sdc, 10) failed: No such file or directory
[ 542.833411] usb 2-4: new SuperSpeed USB device number 7 using xhci_hcd
[ 542.851037] usb 2-4: New USB device found, idVendor=152d, idProduct=0567, bcdDevice= 2.23
[ 542.851042] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 542.851044] usb 2-4: Product: AXAGON USB to SATA adapter
[ 542.851045] usb 2-4: Manufacturer: AXAGON
[ 542.851046] usb 2-4: SerialNumber: 0000AB12352E
[ 542.893319] scsi host6: uas
[ 542.893766] scsi 6:0:0:0: Direct-Access Samsung SSD 870 EVO 250G 0223 PQ: 0 ANSI: 6
[ 542.895976] sd 6:0:0:0: [sdc] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[ 542.895979] sd 6:0:0:0: [sdc] 4096-byte physical blocks
[ 542.896132] sd 6:0:0:0: [sdc] Write Protect is off
[ 542.896133] sd 6:0:0:0: [sdc] Mode Sense: 53 00 00 08
[ 542.896422] sd 6:0:0:0: [sdc] Disabling FUA
[ 542.896423] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 542.896424] sd 6:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes
[ 542.896425] sd 6:0:0:0: [sdc] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
[ 542.901421] sdc: sdc1 sdc2
[ 542.901487] sd 6:0:0:0: [sdc] Attached SCSI disk
And the following is full kernel log (dmesg) of my RockPro64:
http://termbin.com/po3he - too long to post it here.
Does it help you in any way to either solve it within Slackware or give advice?
|
|
|
04-14-2023, 03:01 AM
|
#5
|
Member
Registered: Jan 2020
Distribution: Slackware
Posts: 171
Original Poster
Rep: 
|
I have added this line to the bootloader config, but it does not seem to wait for /dev/sda1
Code:
APPEND earlyprintk awaitdev=sda1 root=/dev/ram rw kbd=us nic=auto:eth0:dhcp
.
|
|
|
04-14-2023, 05:26 AM
|
#6
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,624
|
Quote:
Originally Posted by unInstance
Does it help you in any way to either solve it within Slackware or give advice?
|
You can see the resets there so there's possibly a hardware problem or the driver in the 6.1 Kernel has issues with that interface. This type of error may also be caused by insuffcient power to the drive. Try disconnecting everything other than the USB SATA controller - you seem to have a gaming controller connected.
Try a different self-powered adapter as the last resort.
|
|
|
04-14-2023, 06:09 AM
|
#7
|
Member
Registered: Jan 2020
Distribution: Slackware
Posts: 171
Original Poster
Rep: 
|
I have rebooted my amd64 tower, no any errors/resets anymore. But aarch64 Slackware is still unable to recognize the storage device at boot, with everything except the USB adapter and HDMI disconnected, even though it worked a few months ago. I suspect this may be 6.1 kernel issue.
|
|
|
04-14-2023, 09:30 PM
|
#8
|
Senior Member
Registered: Dec 2002
Distribution: slackware!
Posts: 1,398
|
Two of my rockpro64 6.1.23-armv8, ssd connected to usb 3.0 port using this startech adapter and have no problems.
I'm pretty sure my new aarch64 rpi4 install has same parts without any issues.
Last edited by glorsplitz; 04-14-2023 at 09:35 PM.
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 08:24 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|