Thank you everyone that helped me with this issue.
I learned a great deal.
Namely, for my particular use case, SMR drives are sub-optimal.
It is VERY difficult to even find out if drives are SMR or CMR, because
apparently the manufacturers try to put it all out the door. As mentioned
by Mr. R
On Thu, Oct 21, 2021, 9:02 AM David wrote:
> On Thu, 21 Oct 2021 at 23:53, Gene Heskett wrote:
>
> > And what does this SMR acronym mean, Dan?
>
> Questions like this can be answered with an
> internet search engine. Search for "Seagate SMR".
> For fun you can add search terms like
> "controvers
On 21/10/2021 03:34, David Christensen wrote:
Very detailed analysis, better than mine! Much appreciated.
--
With kindest regards, Piotr.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄
On Thursday 21 October 2021 09:02:01 David wrote:
> On Thu, 21 Oct 2021 at 23:53, Gene Heskett
wrote:
> > And what does this SMR acronym mean, Dan?
>
> Questions like this can be answered with an
> internet search engine. Search for "Seagate SMR".
> For fun you can add search terms like
> "contr
On Jo, 21 oct 21, 16:02:43, Andrei POPESCU wrote:
> On Jo, 21 oct 21, 08:53:10, Gene Heskett wrote:
> > On Thursday 21 October 2021 08:13:26 Dan Ritter wrote:
> >
> > > > === START OF INFORMATION SECTION ===
> > > > Device Model: ST8000DM004-2CX188
> > >
> > > You should be able to return this
On Jo, 21 oct 21, 08:53:10, Gene Heskett wrote:
> On Thursday 21 October 2021 08:13:26 Dan Ritter wrote:
>
> > > === START OF INFORMATION SECTION ===
> > > Device Model: ST8000DM004-2CX188
> >
> > You should be able to return this drive without proving that it
> > is defective; this is one of
On Thu, 21 Oct 2021 at 23:53, Gene Heskett wrote:
> And what does this SMR acronym mean, Dan?
Questions like this can be answered with an
internet search engine. Search for "Seagate SMR".
For fun you can add search terms like
"controversy guilty dreaded bad press" etc.
On Thursday 21 October 2021 08:13:26 Dan Ritter wrote:
> > === START OF INFORMATION SECTION ===
> > Device Model: ST8000DM004-2CX188
>
> You should be able to return this drive without proving that it
> is defective; this is one of Seagates' SMR drives that they did
> not disclose were SMR.
>
Thomas Anderson wrote:
> Here are the results, of my smartctl test:
>
> I am trying to parse them myself, to see if I can learn anything. But,
> immediate glance
>
> and queries did not reveal anything that could help me determine if the
> drive is good or not.
>
>
> smartctl 6.6 2017-11-05 r4
On Jo, 21 oct 21, 02:12:25, piorunz wrote:
>
> Lastly, you should use it in RAID1 or similar mode, to ensure there is
> always backup of data this drive keeps.
RAID is meant only for uptime, backup is something else, see:
http://taobackup.com/.
> You can try Btrfs raid1 or mdadm raid1.
Mostly
Hi.
On Thu, Oct 21, 2021 at 01:45:52AM +0200, Thomas Anderson wrote:
> I am trying to parse them myself, to see if I can learn anything. But,
> immediate glance and queries did not reveal anything that could help
> me determine if the drive is good or not.
It's not. You have a Seagate, af
> On 10/18/21 6:52 PM, Reco wrote:
>>Hi.
>>
>> On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:
>>> I have been having problems with a drive (non-SSD) for a while now,
>>> but I would like to "identify" the problem specifically, so that I may
>>> perhaps be able to get the
On 21/10/2021 00:45, Thomas Anderson wrote:
Here are the results, of my smartctl test:
Five metrics from smartctl require attention:
Device ModelST8000DM004-2CX188
9 Power_On_Hours 14558
183 Runtime_Bad_Block 5
187 Reported_Uncorrect 1334
On Wednesday 20 October 2021 19:45:52 Thomas Anderson wrote:
> Here are the results, of my smartctl test:
>
This would be much easier to decode if you turned off wordwrap, and
repasted from that terminal screen.
> I am trying to parse them myself, to see if I can learn anything. But,
> immediate
Here are the results, of my smartctl test:
I am trying to parse them myself, to see if I can learn anything. But,
immediate glance
and queries did not reveal anything that could help me determine if the
drive is good or not.
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-18-amd64] (local bu
> Essentially, I have been experienced data loss, where nodes become
> unreadable, when I try to "fix it" with fdisk, it says it moves unreadable
> to the trash, basically deleting data.
"it says"? Can you clarify what is this "it"?
Drive-level errors of "unreadable data" normally lead to errors
On 10/18/21 9:25 AM, Thomas Anderson wrote:
Hello Gurus,
I have been having problems with a drive (non-SSD) for a while now, but
I would like to "identify" the problem specifically, so that I may
perhaps be able to get the drive replaced.
Essentially, I have been experienced data loss, where
Have a look at "smartctl". It will print some info about the drive and
can also "test" your drive known as S.M.A.R.T-test.
First of all i would have a look what "smartctl -a /dev/sdX" will say.
Am 18.10.21 um 18:25 schrieb Thomas Anderson:
> Hello Gurus,
>
> I have been having problems with a dr
Cool, thanks Reco!
Will post again tomorrow =) Takes 987 minutes apparently.
On 10/18/21 6:52 PM, Reco wrote:
Hi.
On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:
I have been having problems with a drive (non-SSD) for a while now,
but I would like to "identify" the pro
Hi.
On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:
> I have been having problems with a drive (non-SSD) for a while now,
> but I would like to "identify" the problem specifically, so that I may
> perhaps be able to get the drive replaced.
Assuming it's SATA/IDE drive, al
Thomas Anderson composed on 2021-10-18 18:25 (UTC+0200):
> I have been having problems with a drive (non-SSD) for a while now, but
> I would like to "identify" the problem specifically, so that I may
> perhaps be able to get the drive replaced.
> Essentially, I have been experienced data loss,
Hello Gurus,
I have been having problems with a drive (non-SSD) for a while now, but
I would like to "identify" the problem specifically, so that I may
perhaps be able to get the drive replaced.
Essentially, I have been experienced data loss, where nodes become
unreadable, when I try to "fix
22 matches
Mail list logo