Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

[Jochen Spieker]

Alexander V. Makartsev:
> On 19.03.2021 21:23, Jochen Spieker wrote:
>>> Note : Linux installed on sdb (ext4) and sda is a NTFS file system and
>>> 
>>> I don't want my SSD or HDD died suddenly
>> But I am afraid that is exactly what is happening.
> 
> You can't be so sure, not until OP reports back with testing results.

?

There are pending sectors, there were filesystem errors. One of the
disks is obviously damaged.

You are right that the disk could still be useful for quite some time
without additional damage. But unless you are tight on money, my advice
would still be to shell out the €50-100 for a new drive to avoid the
risk and effort to deal with more damage. Especially if the OP is like
many/most people and does /not/ have a proper backup.

J.
-- 
When you put a gun to my head you aren't fooling anyone.
[Agree]   [Disagree]
 


signature.asc
Description: PGP signature

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

[Jochen Spieker]

Robbi Nespu:
> 
> I worried I might missing some package for hdd and sdd maintainance (coz I
> doing minimal install previously)

There is no maintenance that needs to be done for hard disks or solid
state disks to increase longevity. It often makes sense to setup
smartmontools which can monitor things like bad blocks for you, but this
can only inform you about potential problems, not prevent them.

> Note : Linux installed on sdb (ext4) and sda is a NTFS file system and
> 
> I don't want my SSD or HDD died suddenly

But I am afraid that is exactly what is happening.

I would not worry about the alignment issues at all. The problem is that
one of your disks is having bad sectors which still need to be
reallocated. That means you may already have data loss. Chances are that
the number of bad sectors is going to increase over time which is going
to lead to more data loss.

My personal advice would be to replace the failing disk with a new one
and restore from a known-good backup. If you lack money, you can try to
find a used disk, but I would only pay for something which I have
checked with smartcl beforehand. If you lack a backup, you can only hope
that you have lost nothing of value and get a new disk as fast as
possible.

J.
-- 
Quite often I wonder why I am not more famous and/or more wealthy.
[Agree]   [Disagree]
 


signature.asc
Description: PGP signature

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

[Alexander V. Makartsev]

On 19.03.2021 21:23, Jochen Spieker wrote:

Note : Linux installed on sdb (ext4) and sda is a NTFS file system and

I don't want my SSD or HDD died suddenly

But I am afraid that is exactly what is happening.

You can't be so sure, not until OP reports back with testing results.


I would not worry about the alignment issues at all. The problem is that
one of your disks is having bad sectors which still need to be
reallocated. That means you may already have data loss. Chances are that
the number of bad sectors is going to increase over time which is going
to lead to more data loss.

My personal advice would be to replace the failing disk with a new one
and restore from a known-good backup. If you lack money, you can try to
find a used disk, but I would only pay for something which I have
checked with smartcl beforehand. If you lack a backup, you can only hope
that you have lost nothing of value and get a new disk as fast as
possible.
Personally, I don't think it is wise to throw away any HDD as soon as it 
gets a few pending bad blocks for whatever reason.
I had a drive with remapped bad blocks in SMART and that amount stayed 
the same for years, despite its workload and periodical full surface scan.
I mean platter surface with the modern sector density is not perfect. It 
simply can't be.
Even brand new drives are shipped with information about factory 
remapped sectors in special section inside their firmware, to cover up 
platter imperfections.
10 sectors are nothing compared to billions of them on a multi-terrabyte 
drive, if they don't grow in numbers over time, because say platter 
contamination,
and the drive is not failing mechanically, so each case should be 
examined carefully.
This is why performing regular backups and validating them is better, I 
mean you do it all anyway, than replacing drives as soon as they get a 
few bad sectors.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Components to sale | KALIS

[Kaly Wang]

Hello purchasing dept., 
Good day. How do you do?
This Kaly Wang from Kalis Electronics Ltd., our company is a professional 
Electronics Parts exporter. So we want to avail ourselves of opportunity 
establishing business relation with you. 



Our advantage:
1. Do our best to Meet your TP
2. Shorter lead time, Newer Date Code
3. Free samples
4. We will provide testing report if you need
The more comparison,the more chance.

By the way, f-r-e-e sample are available. 

Thank you in advance! 
Best wishes！ 
Kaly Wang 

Company Name: Kalis Electronics Co., Ltd.
Tel: +86 0755 28263297

Address: 32C, AnLiangRoad Long Gang Dist, ShenZhen , China, 518112

screen blank watching Netflix

[Russell Coker]

Until recently I could watch Netflix with Chrome on Debian/Testing with no 
problems.  Some recent update (maybe of Chrome, maybe of Debian) broke this, 
now the screen blanker will enable during play.  I don't know which update as 
I have a long screen lock time (the laptop for Netflix isn't used for anything 
important and is in a secure location) and I don't often watch it for long 
enough without pausing to have it blank.  I considered setting a blank time of 
1 hour (longer than an episode of a Netflix show) as a work around.

I'm running KDE with sddm for logging in and the login session often runs 
nothing other than Chrome.  Any suggestions on where I could start looking for 
the cause of this?

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

[Alexander V. Makartsev]

On 19.03.2021 07:07, Robbi Nespu wrote:
On Thu, 18 Mar 2021 23:06:31 +0500 "Alexander V. Makartsev" 
 wrote:
Partitions mounted with 'errors=remount-ro' option will be remounted 
as read-only automatically, if a kernel detects an error.
I suggest you to dig a little deeper, because there is a possibility 
a hardware problem is the source of inconsistency error.
You need to provide us with more information about your OS setup and 
hardware.

Output from these commands should be a good start:
    $ cat /etc/fstab
    $ sudo blkid
    $ sudo smartctl -iHA /dev/sda
    $ sudo smartctl -iHA /dev/sdb

"smartctl" is a tool from "smartmontools" package.
The output will be long, so you can post it at 
"https://paste.debian.net/"; with reasonable expiration date and send 
us just a link to it.


OK here comes the output:
https://paste.debian.net/1189948/


==
  5 Reallocated_Sector_Ct   0x0033   200 200   140    Pre-fail  
Always   -   0

==
197 Current_Pending_Sector  0x0032   200   200   000    Old_age 
Always   -   10

==
Raw values of these two SMART attributes should always be a 0 on a 100% 
healthy drive.

Currently there are 10 sectors marked as faulty by drive's firmware.
There is a possibility there are more, but not marked, since they were 
not accessed yet by the drive.
You can scan whole surface of a drive to be sure there are only those 10 
and they won't increase over time.
Scanning process could be destructive to a data on the drive, so before 
you perform surface scans make sure you've backed up all valuable data 
and stored it on another drive.


To perform surface scans you can use SMART short and long scans, and 
also a program called "badblocks" from the package "e2fsprogs".

Be sure to unmount "/dev/sda1" before performing the scans.
Short scan (a minute or so):
    $ sudo smartctl --test=short /dev/sda
Long scan (could take hours):
    $ sudo smartctl --test=long /dev/sda
To get status and results:
    $ sudo smartctl --log=selftest /dev/sda
Both tests should finish with "Completed without error" result.

Check out man page for "badblocks" for more information.
There are 3 options, read-only test, non-destructive read-write test and 
destructive write test.

Usualy a non-destructive read-only test is sufficient:
    $ sudo badblocks -s /dev/sda
A non-destructive read-write test will be checking both read and write 
operations on scanned sectors, so it is more risky to the data on the drive:

    $ sudo badblocks -n -s /dev/sda

If a bad sector is encountered during testing a drive could "freeze" to 
redo reading on a faulty sector, give it a time to recover and continue.
Once again, make sure you've backed up all valuable data and stored it 
on another drive before testing and tell us how it went.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄