On 7/27/2022 1:51 PM, Erik Mathis wrote:
> I would look at the UEFI vs BIOS boot options in the "backup" server and
> compare it to the "broken" server and make sure they are the same. Also check
> for BIOS updates and such.
>
>
> -Erik-
>
>
> On Wed, Jul 27, 2022 at 7:59 AM tony wrote:
>
>
On 2022-08-02 05:17, David wrote:
And then use something like this:
https://www.newegg.com/sabrent-ec-dflt-dock/p/N82E16817366069
to connect disk "A" to machine "B".
StarTech external caddies/connectors seem OK.
mick
The second disk would need to be connected to the running linux in some
way either by a disk dock or a disk caddy such that the running linux
could find the second disk using lsblk and blkid. Once located, parted -a
optimal /dev/xxx and then print to show the partition table then quit on
/dev/xxx
On Tue, 2 Aug 2022 at 13:25, David Wright wrote:
> On Thu 28 Jul 2022 at 14:29:32 (+0100), tony van der Hoff wrote:
> > On 27/07/2022 16:07, Jude DaShiell wrote:
> > Thanks for your help. Sadly, I'm not getting very far with this. I
> > guess I'm not understanding your instructions too well:
> >
On Thu 28 Jul 2022 at 14:29:32 (+0100), tony van der Hoff wrote:
> Thanks for your help. Sadly, I'm not getting very far with this. I
> guess I'm not understanding your instructions too well:
>
> On 27/07/2022 16:07, Jude DaShiell wrote:
> > Have the running linux system on the machine. Run lsblk
On Fri, 29 Jul 2022 at 02:32, Jude DaShiell wrote:
>
> Then your new /etc/fstab record should
> look like:
> The email program split that line all
> of that should be on one line
> space-separated. hth.
> 3fe30767-f7d7-4e6d-b48e-f80eef2d4b71
> /dev/sda9 ext4 defaults,nofail 1 2
Although it does
Then your new /etc/fstab record should
look like:
The email program split that line all
of that should be on one line
space-separated. hth.
3fe30767-f7d7-4e6d-b48e-f80eef2d4b71
/dev/sda9 ext4 defaults,nofail 1 2
On Thu, 28 Jul 2022, tony van der Hoff wrote:
> Thanks for your help. Sadly, I'm not
On Wed Jul 27 10:30:05 2022 tony wrote:
> I turned on my main home server after a few weeks absence, and got
> smoke from its power supply. Fortunately, I have a backup system,
> which does work; both are running Debian 10, so I swapped use to that
> machine. and am able to work with that, but
I would look at the UEFI vs BIOS boot options in the "backup" server and
compare it to the "broken" server and make sure they are the same. Also
check for BIOS updates and such.
-Erik-
On Wed, Jul 27, 2022 at 7:59 AM tony wrote:
> Hi,
>
> I turned on my main home server after a few weeks abse
tony composed on 2022-07-27 12:37 (UTC+0100):
> I turned on my main home server after a few weeks absence, and got
> smoke from its power supply. Fortunately, I have a backup system, which
> does work; both are running Debian 10, so I swapped use to that machine.
> and am able to work with that,
On 7/27/22 04:37, tony wrote:
Hi,
I turned on my main home server after a few weeks absence, and got
smoke from its power supply. Fortunately, I have a backup system, which
does work; both are running Debian 10, so I swapped use to that machine.
and am able to work with that, but some of the fi
On 7/27/22 08:02, tony wrote:
Hi,
I turned on my main home server after a few weeks absence, and got
smoke from its power supply. Fortunately, I have a backup system, which
does work; both are running Debian 10, so I swapped use to that machine.
and am able to work with that, but some of the fi
Have the running linux system on the machine. Run lsblk to locate the
name of the boot partition. Once you have the name run blkid and copy the
uuid for use in the end of /etc/fstab and put in the path to the boot
device, the disk format ext4, defaults,nofail 1 2 on an fstab entry.
Next, run upda
13 matches
Mail list logo
