On 1/13/24 10:49, Andy Smith wrote:
Hi Gene,
On Fri, Jan 12, 2024 at 11:57:23PM -0500, gene heskett wrote:
On 1/12/24 21:56, Andy Smith wrote:
No it doesn't; smartctl works on drives, not mdadm arrays. mdadm
arrays are composed of block devices. Therefore any output you get
from smartd refers to a storage drive, not an mdadm array.
This appears to be true, there are 4 1t drives as a raid10, and the various
messages in that mbox file name 3 of the individual drives.
Messages you do not show us, meanwhile the rest of your report is
littered with errors, so I'm afraid I can't take you at your word
until you show me.
I repeat, smartd only works with whole drives. Those emails will
show device paths for whole drives.
But those individual drives cannot now be found by smartctl.
You have not yet demonstrated use of a single correct smartctl
command even though I literally told you what to type.
individually it names /dev/sde1, /dev/sdg1, and
/dev/sdd1.
I don't believe that you have an email from smartctl saying any of
that. So please show us. Again, it would be plausible for
these emails to mention /dev/sde etc.
As usual you have not bothered to show us what you are talking about
(the email from smartd), so we are left to guess. We should not
assume that it even says what you think it says.
copy paste from another shell:
gene@coyote:~$ sudo smartctl -i -d /dev/sde1
Here is what I said, which is quoted above, but I'll repeat it here
for emphasis:
As usual you have not bothered to show us what you are talking
about (THE EMAIL FROM SMARTD)
You then proceed to show us something that is not the email from
smartd — that is the very topic of your email — but just repeat the
output of a command that I already advised you was erroneously
formed.
blkid does not sort them in order either. And of coarse does not list whats
unmounted, forcing me to ident the drive by gparted in order to get its
device name. From that I might be able to construct another raid from the 8T
of 4 2T drives but its confusing as hell when the first of those 2T drives
is assigned /dev/sde and the next 4 on the new controller are /dev/sdi, j,
k, & l.
WHAT ON EARTH are you talking about. You start off by complaining
about an email that you don't show us, by email two you are on about
tearing your RAID apart and making a new one, all without a shred of
relevant information or the first idea of how to show the status of
anything.
You are working blind here, DO NOT DO ANYTHING until you fully
understand what is going on.
Start with your first concern which was these emails from smartd.
SHOW THEM TO US.
or, heck, get all the info at once:
# smartctl -a /dev/sde
**********************************************************************
If there is anything in that output that you have questions about,
please make sure to quote the full and unedited output back here to
the list, so we aren't left guessing what the subject of
discussion is.
**********************************************************************
Thanks,
Andy
/dev/sde1 has been formatted and mounted, what cmd line will copy every byte
including locked files in that that raid10 to it?
!?
For the love of God can someone, anyone, any intelligent entity
out there, explain to me how I could have been ANY MORE EXPLICIT
about the need for you to run a single command that I specified and
show us the output of it?
And did you do that?
No, apparently you have nuked a drive that we don't know the status
of.
Incredible.
Let's just assume for a second that we can just ignore everything
you have said previously and focus on your last question about
copying data, why would anyone even both responding given that as
demonstrated here you are prepared to ignore even the most basic
explicit advice and do something insane like nuke a whole drive?
Just what is the point?
Lost for words.
So am I Andy. Since writing that, and my urge to get rid of a 30+ second
delay on opening ANYTHING that wants write perms to this raid, I've done
this this morning:
used gparted to format to ext4 a single gpt partition on that /dev/sde
with a LABEL=homesde1 but forgot the 1 when editing /etc/fstab to
remount it on a reboot to /mnt/homesde1, which resulted in a failed
boot, look up the root pw and finally get in to fix /etc/fstab for the
missing 1 in the labelname.
but first mounted a 2t gigastone ssd to /mnt/homesde1 which is where it
showed up in an lsblk -f report.
Spent 2+ hours rsync'ing with:
sudo rsync -av /home/ /mnt/homesde1
which worked entirely within the same 6 port controller as this raid10
is running on.
reboot failed, moved the data cable to the motherboard port 5 or 6 (or
maybe 1 or 2, 6 ports, nfi which is 0 and which is 5) but its on the
mobo ports now, should be easily found at boot time.
Finally look up root pw, get in to fix /etc/fstab and get booted.
Talk about portable devicenames, that drive is now /dev/sdk1 !!! And
empty of a LABELname but now has the 360gigs of data I just rsync'd to it.
but on reboot, its now /dev/sdb1 and empty.
from a df:
gene@coyote:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 16327704 0 16327704 0% /dev
tmpfs 3272684 1888 3270796 1% /run
/dev/sda1 863983352 376505108 443516596 46% /
tmpfs 16363420 1244 16362176 1% /dev/shm
tmpfs 5120 8 5112 1% /run/lock
/dev/sda3 47749868 132 45291728 1% /tmp
/dev/md0p1 1796382580 334985304 1370072300 20% /home
/dev/sdb1 1967892164 28 1867855888 1% /mnt/homesde1
tmpfs 3272684 2544 3270140 1% /run/user/1000
gene@coyote:~$
and gparted now says that indeed, /dev/sdb is the drive with the label
"homesde1" on it. And showing 31GiB used. What for unless thats ext4
overhead. All I can see on /mnt/homesde1 is lost+found, which is empty.
So at this point I still have a home raid10, and have NDI where the he!!
the rsync line actually copied 360 Gb of stuff from home to.
smartctl -a /dev/sdb shows:
gene@coyote:~$ sudo smartctl -a /dev/sdb
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Gigastone SSD <- the devices name
Serial Number: GST02TBG221146
Firmware Version: T0917A0
User Capacity: 2,048,408,248,320 bytes [2.04 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available
Device is: Not in smartctl database 7.3/5319
ATA Version is: ACS-3 T13/2161-D revision 4
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat Jan 13 11:28:50 2024 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status: ( 0) The previous self-test routine
completed
without error or no self-test
has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection
support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 10) minutes.
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x0032 100 100 050 Old_age
Always - 0
5 Reallocated_Sector_Ct 0x0032 100 100 050 Old_age
Always - 0
9 Power_On_Hours 0x0032 100 100 050 Old_age
Always - 884
12 Power_Cycle_Count 0x0032 100 100 050 Old_age
Always - 5
160 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 0
161 Unknown_Attribute 0x0033 100 100 050 Pre-fail Always
- 100
163 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 10
164 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 46
165 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 2
166 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 0
167 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 0
168 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 1500
169 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 100
175 Program_Fail_Count_Chip 0x0032 100 100 050 Old_age Always
- 0
176 Erase_Fail_Count_Chip 0x0032 100 100 050 Old_age Always
- 0
177 Wear_Leveling_Count 0x0032 100 100 050 Old_age Always
- 0
178 Used_Rsvd_Blk_Cnt_Chip 0x0032 100 100 050 Old_age Always
- 0
181 Program_Fail_Cnt_Total 0x0032 100 100 050 Old_age Always
- 0
182 Erase_Fail_Count_Total 0x0032 100 100 050 Old_age Always
- 0
192 Power-Off_Retract_Count 0x0032 100 100 050 Old_age Always
- 4
194 Temperature_Celsius 0x0022 100 100 050 Old_age Always
- 40
195 Hardware_ECC_Recovered 0x0032 100 100 050 Old_age Always
- 0
196 Reallocated_Event_Count 0x0032 100 100 050 Old_age Always
- 0
197 Current_Pending_Sector 0x0032 100 100 050 Old_age Always
- 0
198 Offline_Uncorrectable 0x0032 100 100 050 Old_age Always
- 0
199 UDMA_CRC_Error_Count 0x0032 100 100 050 Old_age Always
- 0
232 Available_Reservd_Space 0x0032 100 100 050 Old_age Always
- 100
241 Total_LBAs_Written 0x0030 100 100 050 Old_age
Offline - 986
242 Total_LBAs_Read 0x0030 100 100 050 Old_age
Offline - 7
245 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Selective Self-tests/Logging not supported
*********
please $diety, deliver me from linux's vaporous disk naming scheme that
changes faster than the weather. Even device LABEL= does not work. I
mounted that drive by its label to /mnt/homesde1 and rsync'd /home/ to
it but that 360Gb of data went someplace else. Since the data, according
to what I see in gparted, actually went to /dev/sdk1, which is another
of the 2T gigastones, I intend to make a raid6 out of, no harm to my
data is done. My raid10 was not destroyed. But I'm burned out and
frustrated. This is hardware, not a roll of the dice per boot.
I can easily erase and restart that drive for a raid with gparted, But
howinhell do I get a stable drive detection system so I know what I am
doing??????????????????????????????????????????
Besides that, I'm running low on hair too.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
