Re: voltage monitoring Q
On Tuesday, 15 March 2022 02:43:59 EDT Richard Hector wrote: > On 13/03/22 21:15, gene heskett wrote: > > they are the last seacrate drives I'll own... Ever. > > Lots of brands seem to go through bad patches. Even just bad batches. > > For stuff I care about, I use RAID1 (mdraid), on NAS drives, from mixed > manufacturers. So I'll have a pair consisting of a Seagate IronWolf > and a WD Red. That way, if one dies, it's less likely that the other > will immediately follow suit. > > Except if I'm buying a 'server' from the local shop - they insist that > mixing drives will be less reliable, but don't give reasons or > evidence. I insisted for my home backup server, with a Supermicro > server board, but they put 'Custom Workstation' on the invoice - I > don't think they were prepared to call it a server. > > Richard I like that way of thinking Richard. For long term data retention it sounds more reliable to get rid of the cloned twins with the same disease problem. Thanks. 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
Re: voltage monitoring Q
On 13/03/22 21:15, gene heskett wrote: they are the last seacrate drives I'll own... Ever. Lots of brands seem to go through bad patches. Even just bad batches. For stuff I care about, I use RAID1 (mdraid), on NAS drives, from mixed manufacturers. So I'll have a pair consisting of a Seagate IronWolf and a WD Red. That way, if one dies, it's less likely that the other will immediately follow suit. Except if I'm buying a 'server' from the local shop - they insist that mixing drives will be less reliable, but don't give reasons or evidence. I insisted for my home backup server, with a Supermicro server board, but they put 'Custom Workstation' on the invoice - I don't think they were prepared to call it a server. Richard
Re: voltage monitoring Q
On Sunday, 13 March 2022 10:19:13 EDT Andrew M.A. Cater wrote: > On Sun, Mar 13, 2022 at 09:56:38AM -0400, gene heskett wrote: > > On Sunday, 13 March 2022 07:19:39 EDT piorunz wrote: > > > Hi, > > > > > > Let me just tackle on your HDD issue, as I can't help really with > > > fans > > > and voltage. > > > > > > On 13/03/2022 08:15, gene heskett wrote: > > > > All of this did work on stretch, on this mobo. But now its > > > > running > > > > bullseye, and the last 2T seagate drive committed suicide last > > > > night > > > > so I have no backup facilities left, I assume it was a "shingled" > > > > drive, and they are the last seacrate drives I'll own... Ever. > > > > And no one would tell me how to disable or remove them despite my > > repeated queries, So I have now found out how to send that bs to > > /dev/ null, but a reboot is still a reinstall as theres no way to > > prevent the automatic install of those two facilities in the > > installer, and there is no way to reboot w/o does a full powerdown, > > with this lashup needlessly power cycling the drives. Various other > > things have since occured, each of which has led to a re-install. > > Wash rinse and repeat about 25 times since early october. Frustrated > > at the lack of help with my problem because all the recommendations > > are to unplug ALL the usb stuff during an install, but I have only 1 > > keyboard/mouse kit thats wired, and even that is usb2, not ps2. So > > how the hell do I install without a keyboard and mouse? > > Gene, > > Several people have told you - including me off-list in response to > your messages. If you remove USB-serial - esp. FTDI converters and > similar, this will work for the period of the install. Keyboards and > mice do NOT trigger brltty / espeak - or you'd never be able to > install at all. Likewise Logitech and similar dongles for wifi > keyboards / mice. Random serial leads, maybe. > > And last evening about dark, the 2nd drive of those twins went > > offline > > even though it wasn't mounted, causing smartctl to block kmails > > ability to queue a new message. Seemingly unrelated to /dev/sdc > > going offline, but thats what happened. So I tried to reboot. and > > found my wireless keyboard and mouse were no longer found by the > > bios despite my finding earlier that they had to be plugged into the > > bottom accessory breakout for usb2 only stuff. Grub finds them just > > fine. After two or so minutes of the bios waiting to find a > > keyboard and giving up. > > Try plugging the dongle into a USB port rather than onto a cable. USB 2 > or USB 3 shouldn't matter. > > > And you folks are giving me hell for getting frustrated? Something is > > going to hell in this system and I'm trying to find it. The psu is > > plenty big enough at 400 watts, nothing is overheating, I've got > > gkrellm watching about 11 temps and the highest is 31C. It did find > > the cpu fan before this reboot, but 4 more reboots since last > > evening, during the first of which I did get to the bios but only > > the mouse actually worked, but the bios does find all those sensors, > > showing them normal in every detail. > > Not giving you hell for getting frustrated - frustration is only too > human and we all get there - but perhaps for not separating issues and > helping us to help you with data. Venting in the list will help ease > your frustration but doesn't do anything for us to help you. > > There's a bunch of devices listed there: 2 x USB hubs / plug in USB > cards? No, but this mobo comes with lots of ports and breakout panels to fill empty back panel slots. two usb3's, 2 usb2's on the rear panel tower, and headers on the mobo for 4 more of each speed. the keyboard and mouse dongles are plugged into a hub on a 5 foot cable to get them close to the keyboard and mouse. I could probably plug the dongles in directly, haven't tried until I just moved the keyboard and it still works. And so does the mouse. They are now plugged into he back panel of the tower case and facing me. Maybe the bios can find them again if it doesn't have to go thru a hub. > If you don't _need_ firewire there: strip out the card. Make > life simpler. I have a Sony handicam, uses 8mm metal tapes at about 4 times the resolution of vhs. I shoot weddings for friends and such with it, and make them into semi hidef cd or dvd copies to keep. firewire and kino work really well for that. The camera is in fact plugged in to keep its battery charged. > Strip down to minimal, check, checklist as you put stuff back in. > > If you're not sure about your Seagate drives - > they may still be OK - use smartctl and check what they're doing. They are now both dead to smartctl. Not answering the phone so to speak. And apparently smartctl can block everything else. I pulled its data cable which seems to have stopped that hang. > > I am a CET, and I don't think my psu is doing funnies, I just took a > > dvm and checked the 5 volts on the back of a
Re: voltage monitoring Q
On 13/03/2022 21:48, gene heskett wrote: Ok, so you got it replaced under warranty, right? no, not no but hell no, i and done with seagate, Both of them were out of warranty when you bought them, or you just decided to not get free warranty replacement on the second one because *they are all so sh*te*? The first to fail, last october is a 2TB Barracuda ST2000DM006, SN Z4XAWQ6V, PN 2DM164-302 and it been sitting in somebody's warehouse since 9MAR2018 SO ITS WELL OUT OF WARRANTY. And what is the second one? Ha! I have 4 of them, EXACTLY the same drives, running in my server currently. They are not shingled. MY stats so far: Device Model: ST2000DM006-2DM164 (4096 bytes sector) Power On: 23571 hours Power Cycles: 1127 (20 hours/cycle) Temperature: 28 °C Total Written: 1098 TiB Device Model: ST2000DM006-2DM164 (4096 bytes sector) Power On: 26957 hours Power Cycles: 708 (38 hours/cycle) Temperature: 29 °C Total Written: 1387 TiB Device Model: ST2000DM006-2DM164 (4096 bytes sector) Power On: 26973 hours Power Cycles: 708 (38 hours/cycle) Temperature: 30 °C Total Written: 912 TiB Device Model: ST2000DM006-2DM164 (4096 bytes sector) Power On: 23570 hours Power Cycles: 1133 (20 hours/cycle) Temperature: 29 °C Runtime Bad Blocks: 2 Total Written: 455 TiB Totally fine for me... 25 thousand hours on each in average, running perfectly fine 24/7 doing constant heavy server load. That means Seagate is not so s**te after all?! How come? Your "evidence-based testing" proved that all present and future Seagates are totally worthless forever, no? -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: Seagate HDDs (was: voltage monitoring Q)
gene heskett composed on 2022-03-13 17:48 (UTC-0400): > The first to fail, last october is a 2TB Barracuda ST2000DM006, SN > Z4XAWQ6V, PN 2DM164-302 > and it been sitting in somebody's warehouse since 9MAR2018 SO ITS WELL > OUT OF WARRANTY. My ST2000DM006 Z4Z7NKTD was made 2017-02-08, about 4 months before I bought it. No trouble so far, thought the STB it's in hasn't been powered up 24/7 since nearly 2 years ago. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: voltage monitoring Q
On Sunday, 13 March 2022 17:07:00 EDT piorunz wrote: > On 13/03/2022 13:56, gene heskett wrote: > > Thats debatable. I had 2 of them purchased last summer to replace a > > couple of 1T's that were getting too small. > > Still under warranty then. Get them replaced by Seagate. > > > I was put into he boot > > position in August from backups, the other was put in as amandatapes > > when that install was running stretch ok. The first one disappeaed > > in the middle of the night in early october, > > Ok, so you got it replaced under warranty, right? no, not no but hell no, i and done with seagate, I'll be all SSD's before the day is over. Money doesn't count when there is no dependability. Thts what I thought I was buying when I skiped over the cheaper WD's. > > > (...) So how the hell do I install without a keyboard and > > mouse? (...) > keyboard and mouse were no longer found by the bios > > (...)> > > Something is > > going to hell in this system and I'm trying to find it. (...) > > All this is totally irrelevant, I cut it out, won't be commenting or > replying to your adventure stories > > > And you folks are giving me hell for getting frustrated? > > Who it giving you hell? Which folks? You replying to me here in this > post. I simply suggested that you SHOULD determine is Seagate drive was > shingled or not, before saying something like "all Seagate is bad > forever". Don't imply or assume. VERIFY. > > > That drive that failed last night is the second of two I bought less > > than a year back. Older seagates were bulletproof, I've one laying > > around here someplace with 70,000 spinning hours on it, was still ok > > when I took it out as it was my amanda drive and 93% full. 25 > > reallocated sectors at about 1000 hours, still 25 reallocated > > sectors 70,000 spinning hours later. Seagate did make good drives, > > once upon a time. > > 1. Get your Seagate replaced under warranty, > 2. Check if it's shingled or not, in time you spend writing irrelevant > side-story in your post you would find that info already. > 3. Share model here someone I am sure will find this info for you if > you don't know how/not willing to. The first to fail, last october is a 2TB Barracuda ST2000DM006, SN Z4XAWQ6V, PN 2DM164-302 and it been sitting in somebody's warehouse since 9MAR2018 SO ITS WELL OUT OF WARRANTY. So I'm going to copy /home to a 240g that I was using for amanda's dump buffer, hoping it will fit, and reboot if it will. Then, just maybe catting /proc/mdstat might make some sense. Right now drive(0) is not the first drive in the array. Or, while I'm doing that, maybe some one can tell me how to refresh that to match what I in fact actually have. > -- > With kindest regards, Piotr. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ > ⠈⠳⣄ > > . 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
Re: voltage monitoring Q
On 13/03/2022 13:56, gene heskett wrote: Thats debatable. I had 2 of them purchased last summer to replace a couple of 1T's that were getting too small. Still under warranty then. Get them replaced by Seagate. I was put into he boot position in August from backups, the other was put in as amandatapes when that install was running stretch ok. The first one disappeaed in the middle of the night in early october, Ok, so you got it replaced under warranty, right? (...) So how the hell do I install without a keyboard and mouse? (...) > keyboard and mouse were no longer found by the bios (...) > Something is > going to hell in this system and I'm trying to find it. (...) All this is totally irrelevant, I cut it out, won't be commenting or replying to your adventure stories And you folks are giving me hell for getting frustrated? Who it giving you hell? Which folks? You replying to me here in this post. I simply suggested that you SHOULD determine is Seagate drive was shingled or not, before saying something like "all Seagate is bad forever". Don't imply or assume. VERIFY. That drive that failed last night is the second of two I bought less than a year back. Older seagates were bulletproof, I've one laying around here someplace with 70,000 spinning hours on it, was still ok when I took it out as it was my amanda drive and 93% full. 25 reallocated sectors at about 1000 hours, still 25 reallocated sectors 70,000 spinning hours later. Seagate did make good drives, once upon a time. 1. Get your Seagate replaced under warranty, 2. Check if it's shingled or not, in time you spend writing irrelevant side-story in your post you would find that info already. 3. Share model here someone I am sure will find this info for you if you don't know how/not willing to. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: voltage monitoring Q
On Sunday, 13 March 2022 12:59:40 EDT Charles Curley wrote: > On Sun, 13 Mar 2022 04:15:38 -0400 > > gene heskett wrote: > > What do I install into a bullseye system, that will monitor the fans > > and psu voltages on this mobo? lm-sensors, mbmon and friends from the > > bullseye repos have been installed but apparently theres still a > > missing link. What might it be? > > Did you run sensors-detect successfully? As a matter of fact, yes, had it re-write the modprobe stuff, restarted kmod, gkrellm etc. No luck. Still no fans or voltages in gkrellm. > -- > Does anybody read signatures any more? > > https://charlescurley.com > https://charlescurley.com/blog/ > > . TAke care Charles, and stay well. 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
Re: voltage monitoring Q
On Sun, 13 Mar 2022 04:15:38 -0400 gene heskett wrote: > What do I install into a bullseye system, that will monitor the fans > and psu voltages on this mobo? lm-sensors, mbmon and friends from the > bullseye repos have been installed but apparently theres still a > missing link. What might it be? Did you run sensors-detect successfully? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: voltage monitoring Q
On 2022-03-13 08:15, gene heskett wrote: Greetings all; This mobo is an ASUS Z370-AII, and I'd like to use gkrellm to monitor psu voltages and those fans that have tachs. But those are not detected by gkrellm, or any of the usual culprits. Temps are working fine. All of this did work on stretch, on this mobo. But now its running bullseye, and the last 2T seagate drive committed suicide last night so I have no backup facilities left, I assume it was a "shingled" drive, and they are the last seacrate drives I'll own... Ever. What do I install into a bullseye system, that will monitor the fans and psu voltages on this mobo? lm-sensors, mbmon and friends from the bullseye repos have been installed but apparently theres still a missing link. What might it be? with a quick look. sensor viewer that came along with default bullseye installation of Xfce looks to be xfce4-sensors. The GUI has temperatures but the tachometers tab is empty. "man Xfce4-sensors" doesn't really say how to get tachometer information. mick -- Key ID4BFEBB31
Re: voltage monitoring Q
On Sun, Mar 13, 2022 at 09:56:38AM -0400, gene heskett wrote: > On Sunday, 13 March 2022 07:19:39 EDT piorunz wrote: > > Hi, > > > > Let me just tackle on your HDD issue, as I can't help really with fans > > and voltage. > > > > On 13/03/2022 08:15, gene heskett wrote: > > > All of this did work on stretch, on this mobo. But now its running > > > bullseye, and the last 2T seagate drive committed suicide last night > > > so I have no backup facilities left, I assume it was a "shingled" > > > drive, and they are the last seacrate drives I'll own... Ever. > > > > And no one would tell me how to disable or remove them despite my > repeated queries, So I have now found out how to send that bs to /dev/ > null, but a reboot is still a reinstall as theres no way to prevent the > automatic install of those two facilities in the installer, and there is > no way to reboot w/o does a full powerdown, with this lashup needlessly > power cycling the drives. Various other things have since occured, each > of which has led to a re-install. Wash rinse and repeat about 25 times > since early october. Frustrated at the lack of help with my problem > because all the recommendations are to unplug ALL the usb stuff during an > install, but I have only 1 keyboard/mouse kit thats wired, and even that > is usb2, not ps2. So how the hell do I install without a keyboard and > mouse? > Gene, Several people have told you - including me off-list in response to your messages. If you remove USB-serial - esp. FTDI converters and similar, this will work for the period of the install. Keyboards and mice do NOT trigger brltty / espeak - or you'd never be able to install at all. Likewise Logitech and similar dongles for wifi keyboards / mice. Random serial leads, maybe. > And last evening about dark, the 2nd drive of those twins went offline > even though it wasn't mounted, causing smartctl to block kmails ability > to queue a new message. Seemingly unrelated to /dev/sdc going offline, > but thats what happened. So I tried to reboot. and found my wireless > keyboard and mouse were no longer found by the bios despite my finding > earlier that they had to be plugged into the bottom accessory breakout > for usb2 only stuff. Grub finds them just fine. After two or so minutes > of the bios waiting to find a keyboard and giving up. > Try plugging the dongle into a USB port rather than onto a cable. USB 2 or USB 3 shouldn't matter. > And you folks are giving me hell for getting frustrated? Something is > going to hell in this system and I'm trying to find it. The psu is plenty > big enough at 400 watts, nothing is overheating, I've got gkrellm > watching about 11 temps and the highest is 31C. It did find the cpu fan > before this reboot, but 4 more reboots since last evening, during the > first of which I did get to the bios but only the mouse actually worked, > but the bios does find all those sensors, showing them normal in every > detail. > Not giving you hell for getting frustrated - frustration is only too human and we all get there - but perhaps for not separating issues and helping us to help you with data. Venting in the list will help ease your frustration but doesn't do anything for us to help you. There's a bunch of devices listed there: 2 x USB hubs / plug in USB cards? If you don't _need_ firewire there: strip out the card. Make life simpler. Strip down to minimal, check, checklist as you put stuff back in. If you're not sure about your Seagate drives - they may still be OK - use smartctl and check what they're doing. > I am a CET, and I don't think my psu is doing funnies, I just took a dvm > and checked the 5 volts on the back of a drive connector at 5.08 steady, > and the 12 volts at the same connector at 12.09 to 12.10 volts. So until > proved different, the psu is good. > > And as sudo, I was unable to write a file from lshw to /lshw.out. no > permission? But I was able to write it to /tmp/lshw.out so its attached. > > I don't see anything glaringly wrong, but theres 35kb of it, maybe you > guys can. I can fix anything you find except my empty coffee cup, the pot > is empty too, so thats next. > > That drive that failed last night is the second of two I bought less than > a year back. Older seagates were bulletproof, I've one laying around here > someplace with 70,000 spinning hours on it, was still ok when I took it > out as it was my amanda drive and 93% full. 25 reallocated sectors at > about 1000 hours, still 25 reallocated sectors 70,000 spinning hours > later. Seagate did make good drives, once upon a time. > > -- > > With kindest regards, Piotr. > > > > ⢀⣴⠾⠻⢶⣦⠀ > > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ > > ⠈⠳⣄ > > > > . > Thanks all, please stay well. > > Cheers, Gene Heskett. > -- With every good wish, as ever, Andy Cater > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and am
Re: voltage monitoring Q
On Sunday, 13 March 2022 07:19:39 EDT piorunz wrote: > Hi, > > Let me just tackle on your HDD issue, as I can't help really with fans > and voltage. > > On 13/03/2022 08:15, gene heskett wrote: > > All of this did work on stretch, on this mobo. But now its running > > bullseye, and the last 2T seagate drive committed suicide last night > > so I have no backup facilities left, I assume it was a "shingled" > > drive, and they are the last seacrate drives I'll own... Ever. > > Drives die. That's normal. Don't assume if was a shingled drive so it > must have died because of that. Check it thoroughly by model and > specifications. You decided to "ban" Seagate by mere assumption, that's > wrong. Thats debatable. I had 2 of them purchased last summer to replace a couple of 1T's that were getting too small. I was put into he boot position in August from backups, the other was put in as amandatapes when that install was running stretch ok. The first one disappeaed in the middle of the night in early october, which began the reboot=reinstall nightmare I've been subjected to since, necause somebody has decreed that if a usb to serial adapter was found during the unstall, it absolutely HAD to be a braille interface, so brltty and orca just had to be installed, but because brltty couldn't find an actual braille interface, it blasted the syslogs every 20 seconds with its error messages, making the log file so big the machine became slugish to the point of unusability in about 3 days. each 20 interval was about 17 lines of errors being logged. And no one would tell me how to disable or remove them despite my repeated queries, So I have now found out how to send that bs to /dev/ null, but a reboot is still a reinstall as theres no way to prevent the automatic install of those two facilities in the installer, and there is no way to reboot w/o does a full powerdown, with this lashup needlessly power cycling the drives. Various other things have since occured, each of which has led to a re-install. Wash rinse and repeat about 25 times since early october. Frustrated at the lack of help with my problem because all the recommendations are to unplug ALL the usb stuff during an install, but I have only 1 keyboard/mouse kit thats wired, and even that is usb2, not ps2. So how the hell do I install without a keyboard and mouse? And last evening about dark, the 2nd drive of those twins went offline even though it wasn't mounted, causing smartctl to block kmails ability to queue a new message. Seemingly unrelated to /dev/sdc going offline, but thats what happened. So I tried to reboot. and found my wireless keyboard and mouse were no longer found by the bios despite my finding earlier that they had to be plugged into the bottom accessory breakout for usb2 only stuff. Grub finds them just fine. After two or so minutes of the bios waiting to find a keyboard and giving up. And you folks are giving me hell for getting frustrated? Something is going to hell in this system and I'm trying to find it. The psu is plenty big enough at 400 watts, nothing is overheating, I've got gkrellm watching about 11 temps and the highest is 31C. It did find the cpu fan before this reboot, but 4 more reboots since last evening, during the first of which I did get to the bios but only the mouse actually worked, but the bios does find all those sensors, showing them normal in every detail. I am a CET, and I don't think my psu is doing funnies, I just took a dvm and checked the 5 volts on the back of a drive connector at 5.08 steady, and the 12 volts at the same connector at 12.09 to 12.10 volts. So until proved different, the psu is good. And as sudo, I was unable to write a file from lshw to /lshw.out. no permission? But I was able to write it to /tmp/lshw.out so its attached. I don't see anything glaringly wrong, but theres 35kb of it, maybe you guys can. I can fix anything you find except my empty coffee cup, the pot is empty too, so thats next. That drive that failed last night is the second of two I bought less than a year back. Older seagates were bulletproof, I've one laying around here someplace with 70,000 spinning hours on it, was still ok when I took it out as it was my amanda drive and 93% full. 25 reallocated sectors at about 1000 hours, still 25 reallocated sectors 70,000 spinning hours later. Seagate did make good drives, once upon a time. > -- > With kindest regards, Piotr. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ > ⠈⠳⣄ > > . Thanks all, please stay well. 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 coyote description: Desktop Computer product: System Product Name (SKU) vendor: System manufact
Re: voltage monitoring Q
Hi, Let me just tackle on your HDD issue, as I can't help really with fans and voltage. On 13/03/2022 08:15, gene heskett wrote: All of this did work on stretch, on this mobo. But now its running bullseye, and the last 2T seagate drive committed suicide last night so I have no backup facilities left, I assume it was a "shingled" drive, and they are the last seacrate drives I'll own... Ever. Drives die. That's normal. Don't assume if was a shingled drive so it must have died because of that. Check it thoroughly by model and specifications. You decided to "ban" Seagate by mere assumption, that's wrong. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
voltage monitoring Q
Greetings all; This mobo is an ASUS Z370-AII, and I'd like to use gkrellm to monitor psu voltages and those fans that have tachs. But those are not detected by gkrellm, or any of the usual culprits. Temps are working fine. All of this did work on stretch, on this mobo. But now its running bullseye, and the last 2T seagate drive committed suicide last night so I have no backup facilities left, I assume it was a "shingled" drive, and they are the last seacrate drives I'll own... Ever. What do I install into a bullseye system, that will monitor the fans and psu voltages on this mobo? lm-sensors, mbmon and friends from the bullseye repos have been installed but apparently theres still a missing link. What might it be? Thank you. 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
