Raspberry pie 3B+

andre_chang

Hi janui:
I tried to do it the way you taught me. But there was still a reciprocal of 1:30.

Andre

Attachments

: 00005f47-02.png (10.09 KiB) Viewed 2125 times

: no-ext4.png (13.68 KiB) Viewed 2125 times

: PARTUUID.png (14.64 KiB) Viewed 2125 times

andre_chang

Although it can boot up, Paruuid has an error.

Attachments

: error.JPG (58.6 KiB) Viewed 2091 times

janui

Hi andre_chang,
I see that you are using the 'partuuid' which I supplied (00005f47-02). You should replace this with the value returned by this command:

blkid /dev/sda2

janui

andre_chang

janui wroteHi andre_chang,
I see that you are using the 'partuuid' which I supplied (00005f47-02). You should replace this with the value returned by this command:
blkid /dev/sda2
janui

hi janui:
That's my value. It's interesting. It's the same as yours!

Attachments

: 00005f47-02.png (10.09 KiB) Viewed 2075 times

janui

Hi andre_chang,

andre_chang wroteThat's my value. It's interesting. It's the same as yours!

Somehow using partuuid is going nowhere. I suggest you modify cmdline.txt to restore its original value of '/dev/sda2'. At least this worked without errors.
Then try this, go to the Settings UI and switch 'USB Automount' OFF. Then reboot. Do you still get the 'dev-sda1.device' message?
janui

andre_chang

janui wroteHi andre_chang,
andre_chang wroteThat's my value. It's interesting. It's the same as yours!
Somehow using partuuid is going nowhere. I suggest you modify cmdline.txt to restore its original value of '/dev/sda2'. At least this worked without errors.
Then try this, go to the Settings UI and switch 'USB Automount' OFF. Then reboot. Do you still get the 'dev-sda1.device' message?
janui

Hi janui:
Turn off'USB Automount'or have dev-sda1. device (1min 30s) messages.

janui

Hi andre_chang,

andre_chang wroteTurn off'USB Automount'or have dev-sda1. device (1min 30s) messages.

Sorry, I don't understand your answer. Do you get the 'dev-sda1.device (1min 30s)' message when 'USB automount' is switched off?
janui

cmh714

so not to throw any wrinkles in.....and I didnt want to search the thread so sorry if this was potentially addressed.....

I am curious if this is an externally powered USB or if its getting it from the Pi? because I would think it does need to be externally powered AND already powered up and spinning when the pi boots.....

just some random thoughts.....GL!!!

andre_chang

Hi janui:

I have modified cmdline. txt to: / dev / sda2
After restart: A start is running for dev-sda1. device (countdown 1 minute 30 seconds)

Then enter the UI settings. Turn off USB automount and restart!
He still appears A start is running for dev-sda1. device (countdown 1 minute 30 seconds)

Andre

andre_chang

cmh714 wroteso not to throw any wrinkles in.....and I didnt want to search the thread so sorry if this was potentially addressed.....

I am curious if this is an externally powered USB or if its getting it from the Pi? because I would think it does need to be externally powered AND already powered up and spinning when the pi boots.....

just some random thoughts.....GL!!!

Hi cmh714:
The power supply of usb-hdd is obtained from pi3b + USB port.
The power supply I supply to pi3b + is 5v/5a. Voltage and current are absolutely sufficient.
Andre

cmh714

andre_chang wrote
cmh714 wroteso not to throw any wrinkles in.....and I didnt want to search the thread so sorry if this was potentially addressed.....

I am curious if this is an externally powered USB or if its getting it from the Pi? because I would think it does need to be externally powered AND already powered up and spinning when the pi boots.....

just some random thoughts.....GL!!!
Hi cmh714:
The power supply of usb-hdd is obtained from pi3b + USB port.
The power supply I supply to pi3b + is 5v/5a. Voltage and current are absolutely sufficient.
Andre

if you think so....cheers and GL!

R101

Andre,

The power supply might be 5V, but have you checked at the Pi and the HDD? Unless the lead is very short, you are probably losing at least a volt in it.

janui

Hi R101 & cmh714,
Thanks for your posts. Didn’t give power a thought until now. It is a known issue on the 3B+, boot power peaks cause problems, this happens even when a 3B in the same configuration had no problems.
A short HDD cable is potentially a very smart and simple solution.
Lets see if we can verify/clarify what is going on. Any other suggestions are very welcome.
janui

janui

Hi andre_chang,
Lets look at the logging for sda1 and sda2. Could you post the output of

journalctl | grep sda

And also post the output of this:

systemd-analyze blame

I would recommend using a very short cable for the HDD as suggested by R101. This will improve reliability even if power is not causing the current problems.

What also is worth a try is modifying the file /boot/config.txt to increase the boot delay time. If power is the problem this modification may allow the HDD to fully start up before actually starting the boot process. This is the line to modify:

boot_delay=2

A value between 5 and 10 should be fine, a larger will have no real effect.
janui

andre_chang

Hi janui:
Modifying the value of config. txt - > boot_delay = 2 < - - - 5-10 is not helpful... Sda1. device is still wrong after restart. Penultimate 1 minute 30 seconds..

PS. These problems will not happen on moode system. He can use usb-hdd to boot normally. There are no errors.

Andre

Attachments

: analyze blame.png (40.08 KiB) Viewed 2335 times

: journalctl.png (49.51 KiB) Viewed 2335 times

andre_chang

Hi janui & cmh714 & R101:
It took me a little time to test the above questions in other ways.. The USB power supply problem of PI3B & PI3B +.

I use 3.5 inch HDD - > connect SATA to USB card... 3.5 inch hard disk fully uses a separate 12V & 5V power supply!

SATA to USB Card Connecting to PI's USB Port & PI Hardware Supplied by Another 5V/4 Amp Power Supply

This method can completely eliminate the impact of power supply shortage.

Unfortunately.. RUNE will still prompt sda1. devie to wait 1:30 seconds in the boot process.

PS. Hard disk boot in Rune 0.3bata + PI3B environment. There is no such problem!

Testing these faults over and over again is time-consuming and very hard. Please give more praise to the rune team for their hard work.

Look forward to Janui reviewing the logs of sda1 & sda2...

Andre

janui

Hi andre_chang,
I think your explanation concerning how you power the HDD plus the output of 'journalctl | grep sda' and 'systemd-analyze blame' just about eliminate the potential power problems. What I see in the output is that sda1 takes far too long mount, it should be 4 or 5 seconds. Could you post the output of:

cat /etc/fstab

And:

cat /etc/crypttab

And:

cat /etc/default/grub

And:

cat /boot/grub*.cfg

And:

dir -l /etc/udev/rules.d/

And:

dir -l /etc/grub.d/

Could be that some commands give no output, this is fine. Then finally post the output of this command:

systemd-analyze critical-chain

janui

andre_chang

Hi janui:
This is the output you need:

Andre

Attachments

: cat.png (85.92 KiB) Viewed 2247 times

cmh714

does vfat = ext4???

janui

Hi andre_chang & cmh714,

cmh714 wrotedoes vfat = ext4???

No. The first partition is vfat (DOS), This is the boot partition /boot. Files on this are editable/modifiable when the HDD (or Micro-SD card) is plugged into a Windows or Linux/Unix machine. For example, this makes it possible to modify config.txt or cmdline.txt if it will not boot. The second partition is ext4 (Linux) and this contains /root.

andre_chang wroteThis is the output you need:

Thanks for the information, but nothing wrong here. I am now interested in the output of these commands:

cat /etc/udev/rules.d/rune_usb-audio.rules
cat /etc/udev/rules.d/raspberrypi.rules
cat /etc/udev/rules.d/60-schedulers.rules
cat /etc/udev/rules.d/rune_usb-stor.rules

janui

« Previous Page Next Page »