From: Patrick Wade <pwade@netassets.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Debian guests losing track of drive sequence?
Date: Tue, 8 Mar 2022 19:01:02 +0000 [thread overview]
Message-ID: <DM6PR18MB37872919F393CE88A3B49455AE099@DM6PR18MB3787.namprd18.prod.outlook.com> (raw)
In-Reply-To: <d57d6010-5ff1-84c5-dddf-71e8f1e4070a@web.de>
Thanks!
--
Patrick R. Wade
-----Original Message-----
From: Roland <devzero@web.de>
Sent: Tuesday, March 8, 2022 11:00
To: Proxmox VE user list <pve-user@lists.proxmox.com>; Patrick Wade <pwade@netassets.com>
Subject: Re: [PVE-User] Debian guests losing track of drive sequence?
that's not a proxmox issue but general linux issue.
solution:
use persistent device names
https://unix.stackexchange.com/questions/530517/persistent-disk-name-dev-sdx-changing-with-almost-every-reboot
there is lot's of more info on that on the net...
roland
Am 08.03.22 um 19:12 schrieb Patrick Wade:
> I have a PVE 7.1-10 environment with several Debian 11 guests; in some of these guests, I have added a second, scsi1 virtual hard disk in addition to the scsi0 boot virtual disk. I have referenced these as /dev/sda and /dev/sdb in /etc/fstab in the guest.
>
> From time to time, when rebooting the guest, the drives are mounted in the wrong order; the content that was in /dev/sdb1 is mounted as the root partition, as if it were /dev/sda1.
>
> What am I missing that I need to do to ensure the guest mounts its virtual disks in the correct manner?
>
> --
> Patrick R. Wade
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
next prev parent reply other threads:[~2022-03-08 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 18:12 Patrick Wade
2022-03-08 19:00 ` Roland
2022-03-08 19:01 ` Patrick Wade [this message]
[not found] ` <mailman.529.1646767174.456.pve-user@lists.proxmox.com>
2022-03-08 19:33 ` M. Lyakhovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM6PR18MB37872919F393CE88A3B49455AE099@DM6PR18MB3787.namprd18.prod.outlook.com \
--to=pwade@netassets.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox