Just an Update to this thread.
It was actually a software bug in desktop-portal (or something like that).
Once that was removed my system has been rock solid.
Thanks Dan
On Tue, Dec 10, 2024 at 3:41 AM Max Nikulin wrote:
> On 09/12/2024 00:14, Michael Stone wrote:
> > Not all drives
> > suppo
On 09/12/2024 00:14, Michael Stone wrote:
Not all drives
support 4k, and many that do get no benefit from such a configuration.
[...]
# nvme id-ns -H /dev/nvme0n1 | grep Rel
LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes -
Relative Performance: 0x2 Good (in use)
LBA Format 1
On Sun, Dec 08, 2024 at 11:26:51PM +0700, Max Nikulin wrote:
I switched this NVME drive to 4k mode. However I considered your
message as statement that internally drives still use higher erase
block size
The erase block is going to be many megabytes, it has nothing to do with
the logical bloc
On 06/12/2024 23:31, Michael Stone wrote:
On Fri, Dec 06, 2024 at 10:51:20PM +0700, Max Nikulin wrote:
Michael, thank you for the long message. Actually I wonder what is
"idle" that allows drive to perform self-maintenance. I expect that
the device should not be in some deep power saving state
On Fri, Dec 06, 2024 at 10:51:20PM +0700, Max Nikulin wrote:
Michael, thank you for the long message. Actually I wonder what is
"idle" that allows drive to perform self-maintenance. I expect that
the device should not be in some deep power saving state (I am yet to
discover available tunables t
On 06/12/2024 21:05, Jörg-Volker Peetz wrote:
As a check if the defective sectors are all mapped out I did read all
sectors of the partitions:
sudo dd if=/dev/sdaX of=/dev/null bs=8M status=progress
I am curious if "nvme device-self-test" might be more effective.
Michael, thank you for
Hi,
Michael Stone wrote on 06/12/2024 14:49:
On Fri, Dec 06, 2024 at 02:26:23PM +0100, Jörg-Volker Peetz wrote:
Should have been more clear. The drive should be idle for a longer time. This
is assured by not mounting any partition of the SSD.
I was able to "repair" unreadable sectors on a built
On Fri, Dec 06, 2024 at 02:26:23PM +0100, Jörg-Volker Peetz wrote:
Should have been more clear. The drive should be idle for a longer
time. This is assured by not mounting any partition of the SSD.
I was able to "repair" unreadable sectors on a built-in SSD of an
HP-Probook laptop. As far as I r
Hi,
Michael Stone wrote on 05/12/2024 18:41:
On Thu, Dec 05, 2024 at 10:26:18PM +0700, Max Nikulin wrote:
On 05/12/2024 16:19, Jörg-Volker Peetz wrote:
1. SSD's have some self healing capacities (discarding defect sectors) which
are performed when the drive is not mounted. Therefore, enter the
On 12/5/24 10:33, Erwan David wrote:
On Thu, Dec 05, 2024 at 04:26:18PM CET, Max Nikulin said:
On 05/12/2024 16:19, Jörg-Volker Peetz wrote:
1. SSD's have some self healing capacities (discarding defect sectors)
which are performed when the drive is not mounted. Therefore, enter the
BIOS of th
On 12/5/24 08:55, Klaus Singvogel wrote:
gene heskett wrote:
On 12/5/24 06:59, Klaus Singvogel wrote:
It can be fixed by a Firmware upgrade, and more recently charges of Samsung SSD
980 PRO are flashed/sold with a good Firmware out-of-the-box.
While I am saying that my results with earlier S
On Thu, Dec 05, 2024 at 10:26:18PM +0700, Max Nikulin wrote:
On 05/12/2024 16:19, Jörg-Volker Peetz wrote:
1. SSD's have some self healing capacities (discarding defect
sectors) which are performed when the drive is not mounted.
Therefore, enter the BIOS of the computer and let it running for c
Hi,
On Thu, Dec 05, 2024 at 04:32:30PM +0100, Erwan David wrote:
> On Thu, Dec 05, 2024 at 04:26:18PM CET, Max Nikulin
> said:
> > On 05/12/2024 16:19, Jörg-Volker Peetz wrote:
> > > 1. SSD's have some self healing capacities (discarding defect sectors)
> > > which are performed when the drive i
On Thu, Dec 5, 2024 at 12:33 PM Michael Stone wrote:
> On Thu, Dec 05, 2024 at 10:53:54AM +, Daniel Harris wrote:
> >So its not actually a crash. On the 2 occasions it has happened, I have
> been
> >away from my computer for a while, and when I return and move the mouse,
> I can
> >see messa
On Thu, Dec 05, 2024 at 04:26:18PM CET, Max Nikulin said:
> On 05/12/2024 16:19, Jörg-Volker Peetz wrote:
> > 1. SSD's have some self healing capacities (discarding defect sectors)
> > which are performed when the drive is not mounted. Therefore, enter the
> > BIOS of the computer and let it runni
On 05/12/2024 16:19, Jörg-Volker Peetz wrote:
1. SSD's have some self healing capacities (discarding defect sectors)
which are performed when the drive is not mounted. Therefore, enter the
BIOS of the computer and let it running for ca. an hour. Then restart
the computer.
I am curious which w
gene heskett wrote:
> On 12/5/24 06:59, Klaus Singvogel wrote:
> >
> > It can be fixed by a Firmware upgrade, and more recently charges of Samsung
> > SSD 980 PRO are flashed/sold with a good Firmware out-of-the-box.
> While I am saying that my results with earlier Samsung have been less than
> g
On Thu, Dec 05, 2024 at 07:32:03AM -0500, gene heskett wrote:
While I am saying that my results with earlier Samsung have been less
than glorious. triple layer nand's turning into half capacity for
instance.
There's simply no real value in looking at historic bad models as a
guide to future p
On Thu, Dec 05, 2024 at 10:53:54AM +, Daniel Harris wrote:
So its not actually a crash. On the 2 occasions it has happened, I have been
away from my computer for a while, and when I return and move the mouse, I can
see messages scrolling on a black screen (no X running). I can move to a new
On 12/5/24 06:59, Klaus Singvogel wrote:
Hi Gene,
gene heskett wrote:
interesting comments here. I've been using SSD's since 40G was the biggest.
The 256G spinning rust, now 15 years old is the only spinning rust left
here. And I've drawer full of samsung 860-870 series drives that have all
gon
Hi Gene,
gene heskett wrote:
> interesting comments here. I've been using SSD's since 40G was the biggest.
> The 256G spinning rust, now 15 years old is the only spinning rust left
> here. And I've drawer full of samsung 860-870 series drives that have all
> gone wonky but not RO yet.. I now have
On 12/5/24 02:23, Klaus Singvogel wrote:
Jeffrey Walton wrote:
On Wed, Dec 4, 2024 at 2:47 PM Klaus Singvogel wrote:
Some more details here:
https://www.pugetsystems.com/support/guides/critical-samsung-ssd-firmware-update/
That's interesting (in a morbid sort of way).
Do you know if fwupdmg
On Wed, Dec 4, 2024 at 11:43 PM Michael Stone wrote:
> On Wed, Dec 04, 2024 at 05:11:47PM +, Daniel Harris wrote:
> >Thanks for all your replies.
> >As far as I can tell there are no errors reported using fsck or smartctl
> or
> >nvme
> > and the firmware is the correct and newest version so
There are two things which could be tried with the SSD
1. SSD's have some self healing capacities (discarding defect sectors) which are
performed when the drive is not mounted. Therefore, enter the BIOS of the
computer and let it running for ca. an hour. Then restart the computer.
2. After ma
Jeffrey Walton wrote:
> On Wed, Dec 4, 2024 at 2:47 PM Klaus Singvogel wrote:
> >
> > Some more details here:
> > https://www.pugetsystems.com/support/guides/critical-samsung-ssd-firmware-update/
>
> That's interesting (in a morbid sort of way).
>
> Do you know if fwupdmgr will detect out-of-date
On Wed, Dec 04, 2024 at 05:11:47PM +, Daniel Harris wrote:
Thanks for all your replies.
As far as I can tell there are no errors reported using fsck or smartctl or
nvme
and the firmware is the correct and newest version so no problems there.
The following are the messages that appear but on
On Wed, Dec 4, 2024 at 2:47 PM Klaus Singvogel
wrote:
>
> Daniel Harris wrote:
> > Seeing the similarity especially that we are both using similar drives
> > (mine i( Samsung SSD 980 PRO 1TB) makes me think it might be a hardware
> > instead of a software issue.
>
> The referenced Samsung SSD 980
I dont suppose its related but just recently (5th October) I have been
getting thousands of these in my logs
Dec 03 18:46:36 sam xdg-desktop-por[1269]: Backend call failed: Cannot
invoke method; proxy is for the well-known name
“org.freedesktop.ScreenSaver” without an owner, and proxy was construc
On Wed, Dec 04, 2024 at 11:34:41AM -0300, Eike Lantzsch ZP5CGE / KY4PZ wrote:
> On Wednesday, 4 December 2024 09:29:17 -03 Daniel Harris wrote:
> > Hello
> >
> > I have been using the stable branch but recently it has not been so
> > stable. I have experienced some unexpected behavior Not sure if
Thanks for all your replies.
As far as I can tell there are no errors reported using fsck or smartctl or
nvme
and the firmware is the correct and newest version so no problems there.
The following are the messages that appear but only taken from my phone and
copied from the photo (lots of scrolli
On Wed, Dec 4, 2024 at 11:07 AM Daniel Harris
wrote:
>
> I have been using the stable branch but recently it has not been so stable.
> I have experienced some unexpected behavior Not sure if its related to this
> ubuntu bug ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 )
>
> Se
Daniel Harris wrote:
> Seeing the similarity especially that we are both using similar drives
> (mine i( Samsung SSD 980 PRO 1TB) makes me think it might be a hardware
> instead of a software issue.
The referenced Samsung SSD 980 PRO has a critical firmware bug.
This bug hit me too. I had to rep
On 04.12.2024 17:29, Daniel Harris wrote:
Hello
I have been using the stable branch but recently it has not been so
stable. I have experienced some unexpected behavior Not sure if its
related to this ubuntu bug (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 )
Seeing the sim
On Wednesday, 4 December 2024 09:29:17 -03 Daniel Harris wrote:
> Hello
>
> I have been using the stable branch but recently it has not been so
> stable. I have experienced some unexpected behavior Not sure if its
> related to this ubuntu bug (
> https://bugs.launchpad.net/ubuntu/+source/linux/+bu
Daniel Harris:
>
> Not sure if I can attach a picture of the error messages but some of the
> errors are
> ext4_find_entry
> ext4_journal_check_start
> ext4_setattr
> mounting filesystem read-only
Please do not send any attachments here. I suggest you just copy and
paste the log messages from jou
Hello
I have been using the stable branch but recently it has not been so
stable. I have experienced some unexpected behavior Not sure if its
related to this ubuntu bug (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 )
Seeing the similarity especially that we are both using simila
36 matches
Mail list logo
