Michael Stone writes:
> As a general matter PCIe devices can/will downgrade...
Thanks for the comprehensive reply. Indeed, those single drive adapters
are dirt cheap so that's a "why not" buy.
It turns out I actually have a free x4 slot and dual SSD adapters using
ASM2812 bridges seem pretty ch
Dan Ritter writes:
> One of the tests that servethehome.com does in reviewing SSDs is the
> write speed after cache saturation: that is, once you have sent enough
> gigabytes in a row, what is the ongoing write speed?
Thanks, excellent info, I had no idea servethehome does that kind of
benchmark
Anssi Saari wrote:
> > Yes. Also not many drives can sustain a multi-gigabyte write rate
> > anyway...
>
> I have to say I was quite disappointed when I cloned a 1TB SSD to a 2TB
> one, average speed wasn't much higher than writing to an HD. I don't
> remember what the target drive was though. Si
On Wed, Dec 11, 2024 at 09:51:01AM +0200, Anssi Saari wrote:
Michael Stone writes:
On Thu, Dec 05, 2024 at 10:55:48AM -0500, e...@gmx.us wrote:
How do I tell how many lanes a given drive uses (preferably before purchase)?
It would be buried in the technical docs. I've only seen 4x drives
(b
Michael Stone writes:
> On Thu, Dec 05, 2024 at 10:55:48AM -0500, e...@gmx.us wrote:
>>How do I tell how many lanes a given drive uses (preferably before purchase)?
>
> It would be buried in the technical docs. I've only seen 4x drives
> (but I'm sure there may be some cheaper drives with fewer).
On Fri, 6 Dec 2024 18:18:27 +
"Andrew M.A. Cater" wrote:
> >
> > OK, my curiosity is up. Why make a point of moving the Windows
> > partition to the end of the drive?
> >
>
> I seem to remember that it's significantly difficult to forecast the
> likely size you'll want for a Windows syst
On Thu, Dec 05, 2024 at 03:32:10PM -0700, Charles Curley wrote:
> On Thu, 5 Dec 2024 22:03:52 +
> "Andrew M.A. Cater" wrote:
>
> > 2. Use gparted to move Windows (maybe apart from the EFI partition)
> > to the end of the drive - move the blank space to the front of the
> > drive after the EFI
On 06/12/2024 05:58, Felix Miata wrote:
Felix Miata composed on 2024-12-05 17:52 (UTC-0500):
Here ya go (Pastebinit on Bookworm refuses to accept images.):
https://paste.opensuse.org/a556a79e8015
expires in 7 days, shows DFSee menu open for "Convert an MBR disk to GPT".
Oops. My mistake. Tabl
On Thu, Dec 5, 2024 at 8:57 PM Felix Miata wrote:
>
> Michael Stone composed on 2024-12-05 16:51 (UTC-0500):
>
> > On Thu, Dec 05, 2024 at 16:16:53 -0500, Felix Miata wrote:
>
> >>At least one does. I provided URL to the one I use, for some definition of
> >>"automated", upthread @2024-12-05 12:24
On Thu 05 Dec 2024 at 16:26:45 (-0500), Felix Miata wrote:
> pocket composed on 2024-12-05 22:17 (UTC+0100):
>
> > The real issue is that the efi partition if I recall correctly has to be a
> > primary partition.
>
> The ESP filesystem must be on a GPT partition. GPT is compatible with
> legacy
On Thu 05 Dec 2024 at 22:03:52 (+), Andrew M.A. Cater wrote:
> On Thu, Dec 05, 2024 at 03:15:36PM -0600, David Wright wrote:
> > On Thu 05 Dec 2024 at 20:01:29 (+), Andrew M.A. Cater wrote:
> >
> > > Use the Microsoft tools to create a Windows .iso file
> > >
> > > Install Windows from a
On 12/5/24 17:26, Michael Stone wrote:
> On Thu, Dec 05, 2024 at 04:06:17PM -0500, e...@gmx.us wrote:
>> To find out if the motherboard imposed any limitations, I checked the
>> manual. I found these tables, which I can't see the implications of:
>>
>> M2D_32G M.2 connector
>> +-+--
Felix Miata composed on 2024-12-05 17:52 (UTC-0500):
> Michael Stone composed on 2024-12-05 16:51 (UTC-0500):
>> On Thu, Dec 05, 2024 at 16:16:53 -0500, Felix Miata wrote:
>>>At least one does. I provided URL to the one I use, for some definition of
>>>"automated", upthread @2024-12-05 12:24 (UT
Michael Stone composed on 2024-12-05 16:51 (UTC-0500):
> On Thu, Dec 05, 2024 at 16:16:53 -0500, Felix Miata wrote:
>>At least one does. I provided URL to the one I use, for some definition of
>>"automated", upthread @2024-12-05 12:24 (UTC-0500) in reply to your post 102
>>minutes earlier. :)
>
On Thu, Dec 05, 2024 at 10:03:52PM +, Andrew M.A. Cater wrote:
2. Use gparted to move Windows (maybe apart from the EFI partition) to the
end of the drive - move the blank space to the front of the drive after
the EFI partiton.
I don't understand this step--why are you moving windows? L
On Thu, Dec 05, 2024 at 04:06:17PM -0500, e...@gmx.us wrote:
To find out if the motherboard imposed any limitations, I checked the
manual. I found these tables, which I can't see the implications of:
M2D_32G M.2 connector
+-+-+-+-+-+-+-
On Thu, 5 Dec 2024 22:03:52 +
"Andrew M.A. Cater" wrote:
> 2. Use gparted to move Windows (maybe apart from the EFI partition)
> to the end of the drive - move the blank space to the front of the
> drive after the EFI partiton.
OK, my curiosity is up. Why make a point of moving the Windows
p
On Thu, Dec 05, 2024 at 03:15:36PM -0600, David Wright wrote:
> On Thu 05 Dec 2024 at 20:01:29 (+), Andrew M.A. Cater wrote:
>
> > Use the Microsoft tools to create a Windows .iso file
> >
> > Install Windows from a .iso file. Use Windows drive tools to shrink Windows
> > on the drive to make
Felix Miata (12024-12-05):
> Where else is possible?
Depends on the firmware, of course. If you try to put a GPT on the drive
of a Lenovo Miix 3-1030, it will not boot.
Regards,
--
Nicolas George
On Thu, Dec 05, 2024 at 04:16:53PM -0500, Felix Miata wrote:
At least one does. I provided URL to the one I use, for some definition of
"automated", upthread @2024-12-05 12:24 (UTC-0500) in reply to your post 102
minutes earlier. :)
Automated means something along the lines of "make this mbr di
Michael Stone composed on 2024-12-05 14:50 (UTC-0500):
> On Thu, Dec 05, 2024 at 02:15:13PM -0500, Felix Miata wrote:
>>I have more than 40 PCs with well in excess of a dozen installed distros,
>>each on
>>a partition,
> You have a unique set of requirements. Probably that has little
> releva
Nicolas George composed on 2024-12-05 22:28 (UTC+0100):
> Felix Miata:
>> The ESP filesystem must be on a GPT partition.
> Not always.
Where else is possible?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux Use
Felix Miata (12024-12-05):
> The ESP filesystem must be on a GPT partition.
Not always.
Regards,
--
Nicolas George
pocket composed on 2024-12-05 22:17 (UTC+0100):
> The real issue is that the efi partition if I recall correctly has to be a
> primary partition.
The ESP filesystem must be on a GPT partition. GPT is compatible with
legacy/BIOS
booting, but not the other way around. It exists because UEFI requi
> Sent: Thursday, December 05, 2024 at 2:24 PM
> From: "Hans"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> Hi folks,
>
> as promised I send you my experiences with cloning to NVME.
>
> So, today I got my new notebook. As I
On Thu 05 Dec 2024 at 20:01:29 (+), Andrew M.A. Cater wrote:
> Use the Microsoft tools to create a Windows .iso file
>
> Install Windows from a .iso file. Use Windows drive tools to shrink Windows
> on the drive to make some space.
>
> Then use something like gparted to move the Windows to t
On Thu 05 Dec 2024 at 20:24:05 (+0100), Hans wrote:
> So, today I got my new notebook. As I never used UEFI, I disabled UEFI in
> BIOS
> (my first mistake!), then cloned everything to the new drive.
Why did you stick with MBR partitioning rather than GPT?
> Now I am hasseling with the drive, a
On 12/5/24 13:07, Michael Stone wrote:
> On Thu, Dec 05, 2024 at 10:55:48AM -0500, e...@gmx.us wrote:
>> How do I tell how many lanes a given drive uses (preferably before purchase)?
>
> It would be buried in the technical docs. I've only seen 4x drives (but I'm
> sure there may be some cheaper dri
Aargh! I just discovered, the seller did not send the notebook as ordered. I
ordered with NVME and he sent with a SATA SSD (checked the SSD, and yes, it
has TWO nicks, which should be one (for NVME).
Tomorrow I will contact the seller and maybe return the notebook.
However, I will keep you inf
On Thu, Dec 05, 2024 at 08:24:05PM +0100, Hans wrote:
What can I do? I would like to keep the existing partitions. However, I could
shrink them. At the moment, my drive looks at this:
primary partition Windows-boot ntfs
primary partition Windows ntfs
primary partition /boot /dev/sda3 ext4
exte
On Thu, Dec 05, 2024 at 08:24:05PM +0100, Hans wrote:
> Hi folks,
>
> as promised I send you my experiences with cloning to NVME.
>
> So, today I got my new notebook. As I never used UEFI, I disabled UEFI in
> BIOS
> (my first mistake!), then cloned everything to the new drive.
>
> Firts reboo
On Thu, Dec 05, 2024 at 05:22:50PM +, Chris Green wrote:
As I understand it the slots in the M2 SSD connector can tell whether
it's SATA or NVMe or both. I have an M2 SSD which I believe will work
either with a SATA connection or with NVMe, and it has two slots in
its connector.
The M.2 dr
On Thu, Dec 05, 2024 at 02:15:13PM -0500, Felix Miata wrote:
I have more than 40 PCs with well in excess of a dozen installed distros, each
on
a partition,
You have a unique set of requirements. Probably that has little
relevance to basically anyone else.
> As I understand it the slots in the M2 SSD connector can tell whether
> it's SATA or NVMe or both. I have an M2 SSD which I believe will work
> either with a SATA connection or with NVMe, and it has two slots in
> its connector.
IIUC the M.2 slot into which you insert the SSD can support either
On Thu, Dec 5, 2024 at 2:24 PM Hans wrote:
>
> as promised I send you my experiences with cloning to NVME.
>
> So, today I got my new notebook. As I never used UEFI, I disabled UEFI in BIOS
> (my first mistake!), then cloned everything to the new drive.
>
> Firts reboot worked well, no problems. B
Hi folks,
as promised I send you my experiences with cloning to NVME.
So, today I got my new notebook. As I never used UEFI, I disabled UEFI in BIOS
(my first mistake!), then cloned everything to the new drive.
Firts reboot worked well, no problems. But then I realized, that if you want
NVME m
Michael Stone composed on 2024-12-05 13:13 (UTC-0500):
> On Thu, Dec 05, 2024 at 12:24:36PM -0500, Felix Miata wrote:
>>Clearly, because it's a seriously inept volume LABEL selection. Among the
>>following are some better, yet easy enough to remember and type, examples:
>># egrep -i 'deb11|deb 11
On Thu, Dec 05, 2024 at 12:24:36PM -0500, Felix Miata wrote:
Clearly, because it's a seriously inept volume LABEL selection. Among the
following are some better, yet easy enough to remember and type, examples:
# egrep -i 'deb11|deb 11|seye|bull|debian11|debian 11' *L*txt | grep ├─ | wc -l
26
# eg
On Thu, Dec 05, 2024 at 10:55:48AM -0500, e...@gmx.us wrote:
How do I tell how many lanes a given drive uses (preferably before purchase)?
It would be buried in the technical docs. I've only seen 4x drives (but
I'm sure there may be some cheaper drives with fewer). On the
motherboard side it'
Dan Ritter wrote:
> Stefan Monnier wrote:
> > >> That is a SATA SSD, not an NVMe.
> > > Interesting, thanks. Apparently either it was misrepresented to me, or I
> > > misremembered. That explains some stuff.
> >
> > The switch from SATA to the NVMe interface/protocol happened basically
> > at
Michael Stone composed on 2024-12-05 10:42 (UTC-0500):
>>https://wiki.debian.org/fstab#Labels
> I personally prefer UUIDs because the odds of an existing drive from a
> different system having a conflicting UUID when you put it in another
> system is near zero while the odds that another drive
>> "M.2 => NVMe" (the implication is currently true in the other
>> direction, tho, AFAIK).
> Not at all. We have many servers with U.2 and U.3 format disks,
> which look like classic 2.5" SSDs but use NVMe PCIe connections.
Aha! Thanks for setting me straight!
Stefan
Stefan Monnier wrote:
> >> That is a SATA SSD, not an NVMe.
> > Interesting, thanks. Apparently either it was misrepresented to me, or I
> > misremembered. That explains some stuff.
>
> The switch from SATA to the NVMe interface/protocol happened basically
> at the same time as the switch from
>> That is a SATA SSD, not an NVMe.
> Interesting, thanks. Apparently either it was misrepresented to me, or I
> misremembered. That explains some stuff.
The switch from SATA to the NVMe interface/protocol happened basically
at the same time as the switch from the 2.5" (and mini-pcie) to the M.2
On 12/5/24 09:59, Michael Stone wrote:
> On Thu, Dec 05, 2024 at 09:42:08AM -0500, e...@gmx.us wrote:
>> Is it different when you boot from an nvme drive? I have what I was
>> told was one and it appears as /dev/sdb or /dev/sda depending how the
>> OS feels that day. I didn't buy it new, it was g
On Mon, Dec 02, 2024 at 03:41:43PM -0300, Bruno Schneider wrote:
I would recommend changing from UUID to labels. Doing so, all you need
to worry is that the new partitions have the same labels as the old
ones.
https://wiki.debian.org/fstab#Labels
I personally prefer UUIDs because the odds of an
On Thu, Dec 05, 2024 at 09:42:08AM -0500, e...@gmx.us wrote:
Is it different when you boot from an nvme drive? I have what I was told
was one and it appears as /dev/sdb or /dev/sda depending how the OS feels
that day. I didn't buy it new, it was given to me, so I may have been
misinformed. It'
On 12/4/24 18:18, Michael Stone wrote:
> One somewhat different thing is the
> concept of NVMe namespaces: your drive will be /dev/nvme0, but you'll
> probably be using /dev/nvme0n1 except for device management. Partitions then
> look like /dev/nvme0n1p1.
Is it different when you boot from an nvm
On 12/4/24 19:39, Greg Wooledge wrote:
On Wed, Dec 04, 2024 at 19:06:40 -0500, gene heskett wrote:
On 12/3/24 14:32, Greg Wooledge wrote:
Note that pocket's system has /sbin pointing to usr/bin NOT to usr/sbin.
On Tue, Dec 03, 2024 at 09:44:32 -0500, Felix Miata wrote:
Bookworm looks to be
On Wed, Dec 04, 2024 at 19:06:40 -0500, gene heskett wrote:
> On 12/3/24 14:32, Greg Wooledge wrote:
> > Note that pocket's system has /sbin pointing to usr/bin NOT to usr/sbin.
> > On Tue, Dec 03, 2024 at 09:44:32 -0500, Felix Miata wrote:
> >
> > > Bookworm looks to be one of the last of the Mo
On 12/3/24 14:32, Greg Wooledge wrote:
On Tue, Dec 03, 2024 at 09:44:32 -0500, Felix Miata wrote:
Greg Wooledge composed on 2024-12-03 07:15 (UTC-0500):
On Tue, Dec 03, 2024 at 12:01:15 +0100, pocket wrote:
lrwxrwxrwx 1 root root 7 Nov 25 19:15 sbin -> usr/bin
That's not how Debian 1
On Mon, Dec 02, 2024 at 01:41:18PM -0500, Felix Miata wrote:
You very likely would need to add drivers to your initrds first, else have to
rescue boot to rebuild after:
This is probably the result of setting MODULES=dep in
/etc/initramfs.conf. When changing hardware I'd recommend changing that
On Tue, Dec 03, 2024 at 04:27:37PM +0100, poc...@homemail.com wrote:
The system I am running this on right now has only NVME only.
Note absence of nvme kernel modules and it boots just fine.
grep RETT /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
It has a stock kernel as I have n
> Sent: Wednesday, December 04, 2024 at 9:59 AM
> From: "Joe"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> On Wed, 4 Dec 2024 13:00:21 +0100
> poc...@homemail.com wrote:
>
> > > Sent: Tuesday, December 03, 2024 at 11:18 PM
On Wed, 4 Dec 2024 13:00:21 +0100
poc...@homemail.com wrote:
> > Sent: Tuesday, December 03, 2024 at 11:18 PM
> > From: "Felix Miata"
> > To: debian-user@lists.debian.org, "Timothy M Butterworth"
> > Subject: Re: From SSD to NVME
> >
> >
> Sent: Tuesday, December 03, 2024 at 11:18 PM
> From: "Felix Miata"
> To: debian-user@lists.debian.org, "Timothy M Butterworth"
>
> Subject: Re: From SSD to NVME
>
> Timothy M Butterworth composed on 2024-12-03 20:36 (UTC-0500):
>
> &
On Wed, Dec 4, 2024 at 12:52 AM Timothy M Butterworth
wrote:
>
> On Tue, Dec 3, 2024 at 7:47 PM Felix Miata wrote:
>>
>> Andy Smith composed on 2024-12-03 19:48 (UTC):
>>
>> > On Tue, Dec 03, 2024 at 14:31:14 -0500, Greg Wooledge wrote:
>>
>> >> pocket's system is the outlier here. It's the only
Timothy M Butterworth composed on 2024-12-03 20:36 (UTC-0500):
>> pocket composed on 2024-12-03 12:01 (UTC+0100):
>> > [alarm@alarm ~]$ ls -l /
>> > lrwxrwxrwx 1 root root 7 Nov 25 19:15 bin -> usr/bin
>> > drwxr-xr-x 3 root root 4096 Dec 31 1969 boot
>> …
The rest of what the above w
On Tue, Dec 3, 2024 at 7:47 PM Felix Miata wrote:
> Andy Smith composed on 2024-12-03 19:48 (UTC):
>
> > On Tue, Dec 03, 2024 at 14:31:14 -0500, Greg Wooledge wrote:
>
> >> pocket's system is the outlier here. It's the only one where there
> >> isn't a separate usr/sbin.
>
> > For some reason po
pocket composed on 2024-12-03 23:26 (UTC+0100):
>>> [alarm@alarm ~]$ ls -l /
>>> lrwxrwxrwx 1 root root 7 Nov 25 19:15 bin -> usr/bin
>>> drwxr-xr-x 3 root root 4096 Dec 31 1969 boot
>> …
>> What Debian puts a FAT filesystem on /boot/? Is that a systemd-boot
>
> Sent: Tuesday, December 03, 2024 at 5:10 PM
> From: "Felix Miata"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> pocket composed on 2024-12-03 22:53 (UTC+0100):
>
> >> From: "Felix Miata"
>
> >> po
> Sent: Tuesday, December 03, 2024 at 5:07 PM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> On Tue, Dec 03, 2024 at 22:50:42 +0100, poc...@homemail.com wrote:
> > Doesn't the manual/book suggest that you c
pocket composed on 2024-12-03 22:53 (UTC+0100):
>> From: "Felix Miata"
>> pocket composed on 2024-12-03 22:13 (UTC+0100):
pocket composed on 2024-12-03 12:01 (UTC+0100):
> [alarm@alarm ~]$ ls -l /
> lrwxrwxrwx 1 root root 7 Nov 25 19:15 bin -> usr/bin
> drwxr-xr-x 3 r
On Tue, Dec 03, 2024 at 22:50:42 +0100, poc...@homemail.com wrote:
> Doesn't the manual/book suggest that you can create the partition layout and
> filesystem as you would like?
Why all the double-speak and vagueness?
Did you manually create a FAT file system, and tell the installer to
mount tha
> Sent: Tuesday, December 03, 2024 at 4:31 PM
> From: "Felix Miata"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> pocket composed on 2024-12-03 22:13 (UTC+0100):
>
> >> pocket composed on 2024-12-03 12:01 (UTC+0100):
>
>
> Sent: Tuesday, December 03, 2024 at 4:27 PM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> On Tue, Dec 03, 2024 at 22:13:36 +0100, poc...@homemail.com wrote:
> > > From: "Felix Miata"
> > &
pocket composed on 2024-12-03 22:13 (UTC+0100):
>> pocket composed on 2024-12-03 12:01 (UTC+0100):
>>> [alarm@alarm ~]$ ls -l /
>>> lrwxrwxrwx 1 root root 7 Nov 25 19:15 bin -> usr/bin
>>> drwxr-xr-x 3 root root 4096 Dec 31 1969 boot
>> …
>> What Debian puts a FAT filesystem on /boot
On Tue, Dec 03, 2024 at 22:13:36 +0100, poc...@homemail.com wrote:
> > From: "Felix Miata"
> > What Debian puts a FAT filesystem on /boot/? Is that a systemd-boot
> > configuration?
>
> Mine for one...
Which version of Debian was that, when you installed?
Or was it Arch?
> The install pro
poc...@homemail.com wrote:
>"Andrew M.A. Cater" wrote:
>>
>> As someone else has put it elsewhere in the thread: new laptop means
>> new drivers, potentially moving from legacy MBR to UEFI ... easier in
>> many ways to put a clean install of Debian on from new media to start
>> with (also wiping o
> Sent: Tuesday, December 03, 2024 at 3:30 PM
> From: "Felix Miata"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> Andy Smith composed on 2024-12-03 19:48 (UTC):
>
> > On Tue, Dec 03, 2024 at 14:31:14 -0500, Greg Wooledge wrote:
&
Andy Smith composed on 2024-12-03 19:48 (UTC):
> On Tue, Dec 03, 2024 at 14:31:14 -0500, Greg Wooledge wrote:
>> pocket's system is the outlier here. It's the only one where there
>> isn't a separate usr/sbin.
> For some reason pocket keeps telling us on a Debian list things about
> their Arch
Hi,
On Tue, Dec 03, 2024 at 02:31:14PM -0500, Greg Wooledge wrote:
> pocket's system is the outlier here. It's the only one where there
> isn't a separate usr/sbin.
For some reason pocket keeps telling us on a Debian list things about
their Arch Linux system (actually).
Thanks,
Andy
--
https:
On Tue, Dec 03, 2024 at 09:44:32 -0500, Felix Miata wrote:
> Greg Wooledge composed on 2024-12-03 07:15 (UTC-0500):
> > On Tue, Dec 03, 2024 at 12:01:15 +0100, pocket wrote:
> >> lrwxrwxrwx 1 root root 7 Nov 25 19:15 sbin -> usr/bin
> > That's not how Debian 12 has it.
>
> > hobbit:~$ ls
pocket composed on 2024-12-03 09:40 (UTC-0500):
>> From: "Felix Miata"
>> pocket composed on 2024-12-03 12:01 (UTC+0100):
>>> The "drivers" are part of the kernel
>> Sort of:
>> # inxi -Sd
>> System:
>> Host: ab250 Kernel: 6.1.0-25-amd64 arch: x86_64 bits: 64
>> Console: pty pts/0 Distro: D
> Sent: Tuesday, December 03, 2024 at 10:07 AM
> From: "Felix Miata"
> To: debian-user@lists.debian.org, poc...@columbus.rr.com
> Subject: Re: From SSD to NVME
>
> pocket composed on 2024-12-03 09:40 (UTC-0500):
>
> >> From: "Felix Miata"
>
poc...@homemail.com (12024-12-03):
> [alarm@alarm ~]$ pacman -Q|grep bash
> bash 5.2.037-1
>
> dpkg -l|grep bash
> ii bash 5.2.15-2+b7
> arm64GNU Bourne Again SHell
>
> How did that happen?
I do not know, but unless you start making
Greg Wooledge composed on 2024-12-03 07:15 (UTC-0500):
> On Tue, Dec 03, 2024 at 12:01:15 +0100, pocket wrote:
>> [alarm@alarm ~]$ ls -l /
>> lrwxrwxrwx 1 root root 7 Nov 25 19:15 bin -> usr/bin
>> drwxr-xr-x 3 root root 4096 Dec 31 1969 boot
>> drwxr-xr-x 17 root root 3980 Dec 2
> Sent: Tuesday, December 03, 2024 at 9:24 AM
> From: "Felix Miata"
> To: poc...@homemail.com, debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> poc...@homemail.com composed on 2024-12-03 12:01 (UTC+0100):
>
> >> As someone else has pu
poc...@homemail.com composed on 2024-12-03 12:01 (UTC+0100):
>> As someone else has put it elsewhere in the thread: new laptop means
>> new drivers, potentially moving from legacy MBR to UEFI ... easier in
>> many ways to put a clean install of Debian on from new media to start
>> with (also wipin
> Sent: Tuesday, December 03, 2024 at 8:22 AM
> From: "Nicolas George"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> poc...@homemail.com (12024-12-03):
> > What namespace would that be
>
> I just said it: the namespace f
poc...@homemail.com (12024-12-03):
> What namespace would that be
I just said it: the namespace for completion.
--
Nicolas George
> Sent: Tuesday, December 03, 2024 at 7:50 AM
> From: "Nicolas George"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> poc...@homemail.com (12024-12-03):
> > Why hasn't debian done so?
>
> Because polluting the completion na
poc...@homemail.com (12024-12-03):
> Why hasn't debian done so?
Because polluting the completion namespace with commands useful once in
a blue moon for administrators is a stupid idea.
Regards,
--
Nicolas George
> Sent: Tuesday, December 03, 2024 at 7:15 AM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> On Tue, Dec 03, 2024 at 12:01:15 +0100, poc...@homemail.com wrote:
> > [alarm@alarm ~]$ ls -l /
> > lrwxrwxr
On Tue, Dec 03, 2024 at 12:01:15 +0100, poc...@homemail.com wrote:
> [alarm@alarm ~]$ ls -l /
> lrwxrwxrwx 1 root root 7 Nov 25 19:15 bin -> usr/bin
> drwxr-xr-x 3 root root 4096 Dec 31 1969 boot
> drwxr-xr-x 17 root root 3980 Dec 2 10:38 dev
> drwxr-xr-x 52 root root 4096 Dec 2
On Tue, Dec 03, 2024 at 12:01:15PM +0100, poc...@homemail.com wrote:
[...]
> When people state the above it really just shows they don't understand Linux.
I'd guess Andrew Cater understands Linux better than you and
me taken together, but hey. He's been contributing to Debian
since (at least) la
> Sent: Tuesday, December 03, 2024 at 3:52 AM
> From: "Andrew M.A. Cater"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> On Tue, Dec 03, 2024 at 02:55:07AM +0100, poc...@homemail.com wrote:
> >
> >
> > > It might be ea
On Tue, Dec 03, 2024 at 02:55:07AM +0100, poc...@homemail.com wrote:
>
>
> > It might be easier to produce a clean new install and then just rsync
> > data from the SSD drive to the appropriate directories on the NVME.
>
> No it is better that everything comes over all at one time
>
As someone
On Mon, Dec 02, 2024 at 09:22:05PM +, Andy Smith wrote:
> Hi,
>
> On Mon, Dec 02, 2024 at 09:47:05PM +0100, Hans wrote:
> > That, what i understand as label is the name, I give a partition. For
> > example,
> > in gparted, I can give a partition a label like I want. For example, my
> > Wind
experience when
cloning from SSD to NVME.
Thanks for a short feedback.
Best
Hans
On 12/2/24 08:59, Hans wrote:
>
> I mean clone bit by bit. The software I am using is "Clonezilla"
which depends
> on partclone and dd.
>
>
> No, not rsync. This would be an option,
experience when
cloning from SSD to NVME.
Thanks for a short feedback.
Best
Hans
If you simply clone the system from one hardware system to another, are
you confident that it will work?
I expect that the two different hardware systems would require separate
sets of drivers and configurations
On 02/12/2024 23:49, Hans wrote:
I want to clone the whole system 1 to 1 to the new NVME.
At least some NVME drives report that shipped with, 512 bytes blocks,
they would have better performance switched to 4k ones. I would not
clone partitions to a drive with different block size, it is bet
> Sent: Monday, December 02, 2024 at 2:40 PM
> From: "Andrew M.A. Cater"
> To: debian-user@lists.debian.org
> Subject: Re: From SSD to NVME
>
> On Mon, Dec 02, 2024 at 05:49:18PM +0100, Hans wrote:
> > Hi folks,
> >
> > as my old notebook died,
Hi Greg,
> Depends on what you mean by "clone". If you mean a bit-for-bit copy
> using dd or an equivalent, then you're correct. The file system UUID
> will be copied along with all the other bits of the old file system.
I mean clone bit by bit. The software I am using is "Clonezilla" which depen
Hi,
On Mon, Dec 02, 2024 at 09:47:05PM +0100, Hans wrote:
> That, what i understand as label is the name, I give a partition. For
> example,
> in gparted, I can give a partition a label like I want. For example, my
> Windows partition can get a label like "windows", "win11", "shitty_windows"
>
Am Montag, 2. Dezember 2024, 21:18:05 CET schrieb Andy Smith:
> Hi,
>
> [ Beware not making clear that you mean FILESYSTEM labels and UUIDs
> in this thread. It's been a week since we've had massive
> misunderstanding of what filesystem UUIDs are and every mention of
> UUID o
Hans composed on 2024-12-02 20:20 (UTC+0100):
> Yes, I read in other debian threads abnout Labels. What is the advantage of
> Labels to UUID? I alwaqys thought, labels can be easily changed and then at
> boot, linux would mount some other partition with the same label.
> But it will be rather d
Hi,
On Tue, Dec 03, 2024 at 01:49:12AM +0800, Bret Busby wrote:
> If you simply clone the system from one hardware system to another, are you
> confident that it will work?
You clearly aren't, but I think Hans should be, yes.
Worst cxase is that Hans ends up with something that doesn't boot, but
Hi,
[ Beware not making clear that you mean FILESYSTEM labels and UUIDs
in this thread. It's been a week since we've had massive
misunderstanding of what filesystem UUIDs are and every mention of
UUID or LABEL without that context risks invoking a very confused
person w
is clear), but if I am
using only UUID, the question:
Will the UUID change at clone, even when the partitions are not changed in a
bit of size? IMHO the UUID will not change, but I am not quite sure.
When cloning from SSD to SSD this is working, but I have no experience when
cloning from SSD
1 - 100 of 109 matches
Mail list logo
