> The BIOS of any machine old enough to be using FAT-style MBR cannot cope with
> anything newer, so if you have one, you're stuck with it.
The BIOS does not care about partitions at all: it just loads and
executes whatever is on the first sector of the disk.
As long as you are using a bootloade
Then there was something mentioned about namespaces, which should
be allocated smaller than the physical drive
Is this really needed - just to boot from this SSD?
NVMe namespaces are an abstraction layer that allows a controller to
present its connected storage as a number of independent volume
On 07/04/20 11:32, tu...@posteo.de wrote:
When I boot this setup, grub starts and displays:
booting Linux 5051500-64-RT ...
and freezes. I have to powercycle the whole thing.
If you're getting there, your firmware was successful in loading GRUB
from your system partition, so you can pr
> rc.log stops here:
>
> * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh
> /etc/init.d/local start
> * Starting local ...
> [ ok ]
So apparently it's booting all the way...
Looking at my working config (asus x370 prime, ryzen 7 1700, UEFI boot
from an NVMe SSD), you might want
I've bitten by this too... the problem is that portage does not follow a
particular order when rebuilding subslot deps, so when upgrading
dev-libs/libffi (in this case from 0/7 to 0/8) it can schedule lots of other
packages between when the new libffi is installed and when python is rebuilt.
Hi,
> ~ # parted /dev/sde print
> Model: WD My Book 1230 (scsi)
> Disk /dev/sde: 6001GB
> Sector size (logical/physical): 4096B/4096B
[...]
> AFAICS this partition works fine, fsck does not report any problem. The
> funny thing is, it should not have been possible, because of the 2GB limit
> o
> My SSD (NVme/M2) is ext4 formatted and I found articles on the
> internet, that it is neither a good idea to activate the "discard"
> option at mount time nor to do a fstrim either at each file deletion
> no triggered by a cron job.
I have no desire to enter the whole performance/lifetime deba
Have your backup cron job call fstrim once everything is safely backed up?
Well, yes, but that's beside the point.
What I really wanted to stress was that mounting an SSD-backed
filesystem with "discard" has effects on the ability to recover deleted
data.
Normally it's not a problem, but
Hi,
CONFIG_PARTITION_ADVANCED=y
CONFIG_MSDOS_PARTITION=y
CONFIG_EFI_PARTITION=y
That's all you need.
This could be the key. Sector sizes have been changing from 512 to 4096
over many years. If your kernel has been updated to expect/use 4096 byte
sectors, it might not be able to read the disk
> Since the disk was only ever accessed through an operating system that knew
> solely about MBR, the GPT data meant nothing to it. It happily wrote data
> past the MBR headers. Because the protective MBR is positioned before GPT
> information, the primary GPT header was destroyed and most likel
does my posting from this morning reached you ?
...I did not received anything back from the mailinglist...
Nope. Just this night's response to Wol.
A very *#BIG THANK YOU#* for all the great help, the research and
the solution. I myself am back in "normal mode" :)
You're welcome!
What is the most reasonable setup here:
GPT without any hybrid magic and ext4 because it is so common?
I would go with MBR and a single ext4 partition. GPT is
> I think, I feel better if I repartitioning/reformat both drives,
> though.
It's not necessary, but if it makes you feel better by all means do so.
> *GPT/MBR
> From a discussion based on a "GPT or MBR for my system drive" in
> conjunction with UEFI it was said, that GPT is more modern and
> sav
Hello,
The i219 is a completely different (and much older) chip; the right driver for
the i211 is definitely igb.
That said, I think the OP should first make sure the onboard LAN is enabled in the BIOS
and then post the output of "lspci -tv".
andrea
On 17/11/20 00:59, Adam Carter wrote:
On
Hello,
I don't want to use EFI.
Then you probably should not be attempting to boot off an NVMe drive, as that
is only possible if the drive has an onboard BIOS-mode boot ROM; AFAIK those
are only found on some of the earliest NVMe drives.
Moreover...
grub-install /dev/nvme0n1p2
Installing
101 - 115 of 115 matches
Mail list logo
