Re: SATA drive rescan?
On 17/07/2023 19:57, ToddAndMargo via users wrote: On 7/17/23 01:06, lejeczek via users wrote: On 16/07/2023 08:27, ToddAndMargo via users wrote: Hi All, I have a removable drive sleeve that I mount SATA drives mounted in that attaches to an internal SATA port. I use it backup my system to removable drives. The mechanism works identical to USB flash drives. With one exception. A drive MUST be in the carriage when I boot up. Otherwise, if I insert a drive AFTER the system is booted up, the drive is invisible to the system. Now I have seen Clonzilla re-educating the system as to what drives are where. Is there a way to goose Fedora to do the same? Is there a way to rescan without having to reboot? Many thanks, -T Bit better, clearer description of the hardware/caddie/connection you should have started with. I thought "attaches to an internal SATA port" covered that. https://www.supermicro.com/en/products/motherboard/X11SAE-M It is attached to "I-SATA1" So, it is purely all SATA (& not! e-sata) and no bridge of any kind in-between If so, if purely SATA, I'd suggest you check - if have not done so yet- your mobo's BIOS for something like SATA devices "hot-plugging" Hot plug is enabled and is the default. ___ And to clarify - CloneZilla does the trick when boot up independently of Fedora, as a live-iso, yes? If so then it rather is - as you presumed I guess - OS/software end. Then I'd presume that your BIOS has: - AHCI and not RAID - ports Spin Up Device is "Enabled" - also there is/should be "SATA Device Type" I'd play - imagine you did too - with: 'signal-first-then-power' VS 'power-first-then-signal' Other than that Fedora, Centos. which I mostly use which is older&behind-Fedora, normally do not need much - I always try not to forget to "enable" that in BIOS -> different vendor might have different nomenclature for it: hot- plug OR swap I've only glanced at your 'poking' re/scan, I think it's rather the host/controller you want to poke. If you have not tried already: echo "- - -" > /sys/class/scsi_host/host0/scan (& port/connector might want to give/chose different)___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Possible timezone error on resume from hibernate
On Tue, 2023-07-18 at 06:09 +0100, Barry wrote: > > > > On 17 Jul 2023, at 22:15, Patrick O'Callaghan > > wrote: > > > > That would imply that either all entries are shifted, or none are, > > which is not what I observe. > > You have confirmed that the system powers on at 08:00 BST. > But the logs are for 09:00 when you view them with journalctl for > events while powering up at 08:0l? > > Later logs match the walk clock time? > > What logs do you see around when the time jumps? I've actually reported this to BZ and had some feedback: https://bugzilla.redhat.com/show_bug.cgi?id=2223383&GoAheadAndLogIn=1 poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: works fine - Re: F38 install fails on a Lenovo x120e - Failed to set new efi boot traget
On 17 Jul 2023 at 17:29, Robert Moskowitz wrote:
Date sent: Mon, 17 Jul 2023 17:29:17 -0400
Subject:works fine - Re: F38 install fails on a Lenovo x120e - Failed
to set
new efi boot traget
From: Robert Moskowitz
To: Community support for Fedora users ,
Roger Heflin
Copies to: noloa...@gmail.com
Send reply to: Community support for Fedora users
>
> I got the error again when the install got to that point. I told it to ignore
> and
> continue installing.
>
> I have a usable system.
>
> I did notice on boot an option to edit the EFI firmware. I selected that and
> got an error that cannot boot into the EFI editor.
>
> But that is ok. the system is working!
Just to note. Was able to upgrade my Lenovo R60 to Fedora 38 via
dnf upgrade. Didn't see any reference to it have UEFI in bios, but
the install did make a efi directory in /boot?? First time I ran it,
got a failed message since it said it needed an additional 3M of
space in /boot. clean up some things, and removed the rescue
image kernel. Then it went thru dnf upgrade download, and then
the reboot.
Even added memtest86+ version 6.20 to it.
Have a little script I use to download the latest files from site.
There is work being done to get an rpm to handle it but latest one
in repos is 5.31 and doesn't work. The 6.20one is suppose to work,
but is in testing.
Script is simple to download the binary files from memtest86 site,
and put them in /boot and then manually makes a 20_memtest file.
Needs to run grub2-mkconfig to have it added to grub menu.
#!/usr/bin/bash
clear
mkdir -p /tmp/memtest
cd/tmp/memtest || exit
f=$(wget -O - https://memtest.org/ 2>/dev/null | grep -m1 binaries.zip | sed -e
's/.*&2
exit 1
fi
wget -nc https://memtest.org/"$f";
echo "$f"
zip=$(echo "$f" | cut -f4 -d/)
unzip -u "$zip"
boot=$(find / -maxdepth 2 -iname loader | sed 's_/loader__')
if [ -z "$boot" ]
then
boot="/boot";
fi
echo $boot
cp memtest64.* "$boot" -p -v
ver=$(echo "$zip" | cut -b10-13);
{
printf "# \x21/bin/sh\nexec tail -n +3 \$0\n# This file provides an easy way to
add custom menu entries. Simply type
the\n";
printf "# menu entries you want to add after this comment. Be careful not to
change\n# the 'exec tail' line above.\n"
;
printf "menuentry 'Memtest Legacy' {\n echo 'Loading memtest $ver for BIOS
BOOT SYSTEM'\n linux
/memtest64.bin\n}" ;
printf "\nmenuentry 'Memtest UEFI' {\n echo 'Loading memtest $ver for UEFI
BOOT SYSTEM'\n linux
/memtest64.efi\n}\n"; } >/etc/grub.d/20_memtest86+
chmod 755 /etc/grub.d/20_memtest86+
>
> On 7/17/23 15:40, Robert Moskowitz wrote:
> I was getting ready to try again.
>
> I pulled the CD drive and tried to get into bios setup, but was not fast
> enough and it started booting F38!
>
> It got as far as a things like
>
> [Failed] Failed to start systemd-login.service - User Login
> Management.
>
> then a bunch more and hung.
>
> So I am going to do the install again, keep the drive partitions I set up
> and ignore the EFI warning and see how it goes...
>
> On 7/17/23 15:05, Roger Heflin wrote:
> Yes, some did have efi back then. i have some fm2 mbs that did.
> There will be an option in the bios to enable efi if it does. efi dates to
> early itanium systems in 2002. it was so bad it took years to make it
> to x86 systems. very little was in the classic bios menu and most
> config was in a mess of a poorly documented command line.
>
> On Mon, Jul 17, 2023, 4:02 PM Robert Moskowitz
> wrote:
> Bios ver is "current", ver 1.17 dated 11/7/2012!
>
> Did we have EFI back then?
>
> Oh, F37 live CD booted fine.
>
> On 7/17/23 13:17, Jeffrey Walton wrote:
> > On Mon, Jul 17, 2023 at 11:25 AM Robert Moskowitz
> wrote:
> >> this system had F22 on it.
> >>
> >> I just went through all the steps to blow away the old partitions
> and
> >> install F38.
> >>
> >> It tried for maybe an hour with the spindizzy on "Installing boot
> loader".
> >>
> >> If finally came back with a dialog box with an error of:
> >>
> >> The following error occurred while installing the boot loader. The
> >> system will not be bootable. Would you like to ignore this and
> continue
> >> with the installation?
> >>
> >> Failed to set new efi boot target. This is most likely a kernel or
> >> firmware bug.
> >>
> >> No|Yes
> >>
> >> What should I do at this point. It IS an old system that has had a
> >> number of ver of Fedora on it. It was booting F22 just fine, it
> seemed
> >> but now it is all gone...
> > You can check if the system provides EFI variables using fwupdmgr.
> It
> > will look something like:
> >
> > $ sudo fwupdmgr get-devices 2>&1 | grep -i -E 'UEFI|BIOS'
> > │ Summary: UEFI ESRT device
> > └─UEFI dbx:
> > Summary: UEFI revocation database
> > Vendor: UEFI:Linux Foundation
> > GUIDs: c6682ade-b5ec-57c4-b687-676351208742 ←
> >UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE
> 0D0B996E09E65D802A503
> > f8ba2887-9411-5c36-9cee-88995bb39731 ←
>
Re: wordpress problem
> Am 16.07.2023 um 20:23 schrieb Bill Cunningham : > > > I definitely want to see your doc article. > I first version is now available: Installing Wordpress (on Fedora Server Edition) https://docs.stg.fedoraproject.org/en-US/fedora-server/tutorials/wordpress-installation/ It would be really helpful to get comments, amendments, feedback, corrections! Please use the issue button using the bug symbol on the right side beyond the blue header bar or the edit button next to it. Or write your comments here on the mailing list. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@fedoraproject.org Timezone: CET (UTC+1) / CEST /UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: SATA drive rescan?
On 7/15/23 23:27, ToddAndMargo via users wrote: Hi All, I have a removable drive sleeve that I mount SATA drives mounted in that attaches to an internal SATA port. I use it backup my system to removable drives. The mechanism works identical to USB flash drives. With one exception. A drive MUST be in the carriage when I boot up. Otherwise, if I insert a drive AFTER the system is booted up, the drive is invisible to the system. Now I have seen Clonzilla re-educating the system as to what drives are where. Is there a way to goose Fedora to do the same? Is there a way to rescan without having to reboot? Many thanks, -T Follow up: Okay, now this is embarrassing. I booted into bios with the drive powered up. I went into SATA Configuration to see if there was any other setting(s) that might help. To my absolute embarrassment, Hot Swap and Spin Up were both disabled. (No idea how that happened.) Guess what is working flawlessly now... Many of you called it too. Thank you all for the help. -T Device powered off at boot: # lsscsi [2:0:0:0]cd/dvd ATAPIiHAS124 F CL9M /dev/sr0 [N:0:2:1]diskSamsung SSD 960 EVO 1TB__1 /dev/nvme0n1 Powering on the drive back on: /var/log/messages: Jul 18 15:54:12 rn6 kernel: sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Jul 18 15:54:12 rn6 kernel: sd 1:0:0:0: [sda] 4096-byte physical blocks Jul 18 15:54:12 rn6 kernel: sd 1:0:0:0: [sda] Write Protect is off Jul 18 15:54:12 rn6 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jul 18 15:54:12 rn6 kernel: sd 1:0:0:0: [sda] Preferred minimum I/O size 4096 bytes Jul 18 15:54:12 rn6 kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0 Jul 18 15:54:12 rn6 kernel: sda: sda1 Jul 18 15:54:12 rn6 kernel: sd 1:0:0:0: [sda] Attached SCSI disk Jul 18 15:54:12 rn6 Thunar[3803]: thunar-volman: Unknown block device type "disk". # lsscsi [1:0:0:0]diskATA TOSHIBA DT01ACA2 ABB0 /dev/sda [2:0:0:0]cd/dvd ATAPIiHAS124 F CL9M /dev/sr0 [N:0:2:1]diskSamsung SSD 960 EVO 1TB__1 /dev/nvme0n1 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: SATA drive rescan?
On Tue, 2023-07-18 at 17:08 -0700, ToddAndMargo via users wrote: > To my absolute embarrassment, Hot Swap and Spin Up > were both disabled. (No idea how that happened.) Had you done a BIOS reset at some stage? Accidental reset and save, rather than save and exit. Or had the CMOS battery going flat? Some people argue that if you've done any BIOS updates (this includes UEFI), or you've had a CMOS battery go/going flat, that it's a good idea to reset to defaults and then put in your settings to ensure nothing is in an unknown state. I'm a little against the reset and start-over mentality, though I've certain toggled individual settings off then back on again to iron out computer gremlins in the past. And I had one buggy BIOS where setting one particular thing made a mess of several other unrelated things. -- uname -rsvp Linux 3.10.0-1160.92.1.el7.x86_64 #1 SMP Tue Jun 20 11:48:01 UTC 2023 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: SATA drive rescan?
On 07/18/2023 11:00 PM, Tim via users wrote: Some people argue that if you've done any BIOS updates (this includes UEFI), or you've had a CMOS battery go/going flat, that it's a good idea to reset to defaults and then put in your settings to ensure nothing is in an unknown state. I don't know if it's still true, but for many years, Print Scr was active when you were in CMOS. If it is, you can use it to get an accurate record of your settings. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: SATA drive rescan?
On 7/18/23 22:00, Tim via users wrote: Had you done a BIOS reset at some stage? Accidental reset and save, rather than save and exit. Possibly. I must have done something. Maybe I hit the optimized settings by accident Or had the CMOS battery going flat? Have not noticed my date and time messed up, but ... I turn my computer hard off every night at an outlet strip. I can double check bios in the morning and see if it is back. I do change a lot of CMOS batteries for my customers. -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~ ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
