Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #244390

Re: smartd

From peter@easthope.ca
Newsgroups linux.debian.user
Subject Re: smartd
Date 2022-01-23 07:00 +0100
Message-ID <DIE4V-4z6-1@gated-at.bofh.it> (permalink)
References <DItjb-6Bu-11@gated-at.bofh.it> <DItVU-73X-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


    From: Andy Smith <andy@strugglers.net>
    Date: Sat, 22 Jan 2022 19:07:23 +0000
> > Two parts are available to mount /root; /root can be on /dev/sda1 or 
> > /dev/sda2.
>
> I don't understand what you mean by this statement. 

I should have referred to / rather than /root.

peter@joule:/home/peter$ lsblk --list | grep '\(N\|sda\)'
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda    8:0    0 149.1G  0 disk
sda1   8:1    0     7G  0 part
sda2   8:2    0     7G  0 part /
sda3   8:3    0     8G  0 part [SWAP]
sda4   8:4    0   127G  0 part /home

Currently / is in sda2 and sda1 is not used. If the faulty media is 
strictly in sda2, it can be avoided by shifting / to sda1.

> You are better off finding the damaged sectors and causing the drive
> to remap them by writing new content in there. Then you don't have
> to keep track yourself of which sections of the disk are unusable.

I don't understand how bad sectors are "remapped".  The process is 
internal to the drive?  Depends on Linux software? What about 
connecting the drive to another system and applying fsck to each part?
Then decide whether to scrap the drive.

> Consumer HDDs usually have a few hundred spare sectors for
> remapping.

What happens when all spare sectors are allocated?  Any indication  to 
prevent silent loss of data?

 Thanks,                    ... P.
 

-- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
   48.7693 N 123.3053 W

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

smartd peter@easthope.ca - 2022-01-22 19:30 +0100
  Re: smartd Dan Ritter <dsr@randomstring.org> - 2022-01-22 20:00 +0100
    Re: smartd peter@easthope.ca - 2022-01-23 16:50 +0100
    [SOLVED] Re: smartd peter@easthope.ca - 2022-02-04 18:20 +0100
  Re: smartd Andy Smith <andy@strugglers.net> - 2022-01-22 20:10 +0100
    Re: smartd peter@easthope.ca - 2022-01-23 07:00 +0100
      Re: smartd Andy Smith <andy@strugglers.net> - 2022-01-23 12:20 +0100
        Re: smartd Charles Curley <charlescurley@charlescurley.com> - 2022-01-23 16:20 +0100
          Re: smartd <tomas@tuxteam.de> - 2022-01-23 17:00 +0100
            Re: smartd rhkramer@gmail.com - 2022-01-24 18:20 +0100
    Re: smartd peter@easthope.ca - 2022-01-23 18:10 +0100
      Re: smartd Linux-Fan <Ma_Sys.ma@web.de> - 2022-01-23 19:20 +0100
        Re: smartd Andy Smith <andy@strugglers.net> - 2022-01-23 19:50 +0100
          Re: smartd Charles Curley <charlescurley@charlescurley.com> - 2022-01-23 22:20 +0100
        Re: smartd Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-25 10:50 +0100
    [SOLVED] Re: smartd peter@easthope.ca - 2022-02-04 19:10 +0100
  Re: smartd Charles Curley <charlescurley@charlescurley.com> - 2022-01-22 22:50 +0100

csiph-web