On 19/10/2020 12:33, Peter Humphrey wrote:
Mystery solved. It was a disk failure: a 256GB NVMe drive. It was 4.5 years
old, which doesn't seem a long life to me.
Doesn't sound old, but if it breaks in the fault-tolerance-management
area, then you're stuffed. Bit like old MFM (pre-IDE) drives
On Thursday, 17 September 2020 09:34:04 -00 Peter Humphrey wrote:
> On Monday, 14 September 2020 09:38:10 BST antlists wrote:
> > On 14/09/2020 08:48, Peter Humphrey wrote:
> > > Just before this started, I booted Win-10 on /dev/sdb and ran its update
> > > process. I don't use it for anything at
On Monday, 14 September 2020 09:38:10 BST antlists wrote:
> On 14/09/2020 08:48, Peter Humphrey wrote:
> > Just before this started, I booted Win-10 on /dev/sdb and ran its update
> > process. I don't use it for anything at the moment, just keeping it up to
> > date in case I ever do. I do this
On 14/09/2020 08:48, Peter Humphrey wrote:
Just before this started, I booted Win-10 on /dev/sdb and ran its update
process. I don't use it for anything at the moment, just keeping it up to date
in case I ever do. I do this most weeks, but is it possible that Win-10
tampered in some way that it
On Monday, 14 September 2020 09:04:04 BST J. Roeleveld wrote:
> On Monday, September 14, 2020 9:48:07 AM CEST Peter Humphrey wrote:
> > On Sunday, 13 September 2020 17:05:22 BST Wols Lists wrote:
> > > On 13/09/20 13:26, Peter Humphrey wrote:
> > Just before this started, I booted Win-10 on
On Monday, September 14, 2020 9:48:07 AM CEST Peter Humphrey wrote:
> On Sunday, 13 September 2020 17:05:22 BST Wols Lists wrote:
> > On 13/09/20 13:26, Peter Humphrey wrote:
> Just before this started, I booted Win-10 on /dev/sdb and ran its update
> process.
>
> I don't use it for anything at
On Sunday, 13 September 2020 17:05:22 BST Wols Lists wrote:
> On 13/09/20 13:26, Peter Humphrey wrote:
> > So I'm still left wondering what to do. I'm happy that the hardware isn't
> > on the blink, anyway.
>
> Can you use gdisk to create a new partition in some empty space on the
> disk, delete
I'm backing up my partitions maps to avoid such problems, I've had them before
on spinning rust. Also backing up the headers of luks partitions, loose those
and your' really sunk!
--"Fascism begins the moment a ruling class, fearing the people may use their
political democracy to gain
On Sun, Sep 13, 2020 at 8:17 PM Peter Humphrey
wrote:
> Morning all,
>
> My ~amd64 system uses partitions 1 to 18 on /dev/nvme0n1, and it has two
> SATA
> disks as well, for various purposes. Today, after I'd taken the system
> down
> for its weekly backup (I tar all the partitions to a USB
On 13/09/20 13:26, Peter Humphrey wrote:
> So I'm still left wondering what to do. I'm happy that the hardware isn't on
> the blink, anyway.
Can you use gdisk to create a new partition in some empty space on the
disk, delete it again, and write a partition table? Basically anything
to get gdisk
On Sunday, 13 September 2020 12:40:47 BST antlists wrote:
> You're using the wrong tool to try and fix it. There's clearly something
> wrong with your partition TABLE, and you're using a tool that fixes the
> partition CONTENTS.
Yes, I was clutching at straws, rather.
> Use gparted (or gdisk)
On 13/09/2020 11:17, Peter Humphrey wrote:
Morning all,
My ~amd64 system uses partitions 1 to 18 on /dev/nvme0n1, and it has two SATA
disks as well, for various purposes. Today, after I'd taken the system down
for its weekly backup (I tar all the partitions to a USB disk) and started up
again,
Morning all,
My ~amd64 system uses partitions 1 to 18 on /dev/nvme0n1, and it has two SATA
disks as well, for various purposes. Today, after I'd taken the system down
for its weekly backup (I tar all the partitions to a USB disk) and started up
again, invoking gparted to look around, libparted
13 matches
Mail list logo
