Re: got a mdadm puzzler
On Tuesday, 15 March 2022 15:08:35 EDT Charles Curley wrote: > On Mon, 14 Mar 2022 18:47:52 -0400 > > gene heskett wrote: > > And I am beginning to think in terms of a mobo problem, the bios is > > only seeing the cpu bus a .9 something volts, and the cpu fan at 721 > > rpm, but nothing else and gkrellm isn't even seeing any of that. > > I don't know what CPU voltages are these days (the last I knew, they > were 3.2), but if that is low (see your motherboard manual to be sure), > that could be a power supply problem. Its been that low since this mobo was installed along with a 6 core i5 that has never warmed up its heat sink, even when gkrellm says all cores are flat out at 4.3 ghz, normal, just doing the kmail imap dl stuff is 800 mhz. So, I don't think thats too unusual for this board and cpu combo. And the voltages I have measured, 5 and 12 on a drive connector, are a small amount north of dead on, like the 5 volts is 5.09, and 12 volts is 12.11. So based on gut, plus I'm a CET (altho my billfold card attesting to that is now 50 years old, I sat for that in '72), I think the psu is fine yet. > -- > Does anybody read signatures any more? > > https://charlescurley.com > https://charlescurley.com/blog/ > > . 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: got a mdadm puzzler
On Mon, 14 Mar 2022 18:47:52 -0400 gene heskett wrote: > And I am beginning to think in terms of a mobo problem, the bios is > only seeing the cpu bus a .9 something volts, and the cpu fan at 721 > rpm, but nothing else and gkrellm isn't even seeing any of that. I don't know what CPU voltages are these days (the last I knew, they were 3.2), but if that is low (see your motherboard manual to be sure), that could be a power supply problem. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: got a mdadm puzzler
On Monday, 14 March 2022 17:10:10 EDT Andy Smith wrote: > Gene, > > I just don't know where to start with finding relevant bits to quote > from your text. > > I find it unlikely that several of the drives you have bought should > all be failed and dead. I'm concerned that you're prematurely > jumping to conclusions and junking them. > Plugged back in, on different cables, they are incomunicado. Smartctl sees them, and hangs the system boot when it gets no response. Only way to boot is to powerdown and remove them, them the raid10 is found and the rest of the boot is fine. And I am beginning to think in terms of a mobo problem, the bios is only seeing the cpu bus a .9 something volts, and the cpu fan at 721 rpm, but nothing else and gkrellm isn't even seeing any of that. > It's normal for the device nodes to change as you unplug and plug > drives. They will increment through the alphabet until /dev/sdz > turns into /dev/sdaa and so on. If you are referring to drives by > the device node then this will confuse you and inevitably lead to a > catastrophic error. You may be better off consistently using the > links in /dev/disk/by-id/ which will be based upon the drive serial > numbers. > > Maybe it would be best to put the 4 drives aside and try to get a > stable working system before you mess with them again. This talk of > not being able to reboot sounds like a more serious thing to get > straightened out. > > Cheers, > Andy > > -- > https://bitfolk.com/ -- No-nonsense VPS hosting > > . Thanks Andy 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: got a mdadm puzzler
Gene, I just don't know where to start with finding relevant bits to quote from your text. I find it unlikely that several of the drives you have bought should all be failed and dead. I'm concerned that you're prematurely jumping to conclusions and junking them. It's normal for the device nodes to change as you unplug and plug drives. They will increment through the alphabet until /dev/sdz turns into /dev/sdaa and so on. If you are referring to drives by the device node then this will confuse you and inevitably lead to a catastrophic error. You may be better off consistently using the links in /dev/disk/by-id/ which will be based upon the drive serial numbers. Maybe it would be best to put the 4 drives aside and try to get a stable working system before you mess with them again. This talk of not being able to reboot sounds like a more serious thing to get straightened out. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: got a mdadm puzzler
On Sunday, 13 March 2022 15:02:15 EDT Andy Smith wrote: > Hello, > > On Sat, Mar 12, 2022 at 01:06:39PM -0500, gene heskett wrote: > > On Saturday, 12 March 2022 08:50:07 EST Andy Smith wrote: > > > I think it still might be worth changing the cable and/or moving > > > the > > > drive about to see if the error follows the drive or stays with the > > > port. > > […] > > > Difficult at best. All 4 drives from the same purchase, mounted 2 to > > the 3.5" adapter, and all 4 shoved into a front panel-less drive > > cage below the floppy slot in a huge tower case about 17 yo. Rather > > than blame data cables, I'd start by changing out the power splitter > > cables, this psu doesn't have near enough sata power plugs for 7 > > drives, only 1 of which is spinning rust. And that one quit answering the phone fron smartctl yesterday afternoon. That was my backup src. So that cable will be hooked to a 1T SSD yet today which will be formatted and /home copied to it as that is a huge majority of what I need for a backup. Thats next on the agenda before I do anything else. If I casn get a sata power cable out, that might get done w/o a powerdown since that seems to be the reinstall generator. Got that done, hooked a fresh data cable up to /dev/sdc's socket on the mobo, then carefully inserted the power plug, and /dev/sdc just reported a temp change from smartctl's scan. But while I was doing that, I wrote a copy of LinuxCNC's latest buster install iso to a key, so if I can get it to boot from a key, I'll have a buster install ready to go. The raid10 is sde-f-g-h, and this drive I must have had it the raid before , and is now showing up at /dev/sdd. and on further checking, I've rebooted since disconnecting /dev/sdc, and udev has helpfully reset the drives on damned letter down, to d-e-f-g. gr. But where the hell is it, the drive I just hooked up is marked as an EVO-870 but /dev/sdc is an EVO-860 & 500gigs. /dev/sdb is a 240G ADATA 650, and /dev/sdc is reporting its a EVO-860 of 500G. Obviously fdisk is getting bogus data from some place. You'd better hope I can reboot. But first clean up / dev/sdb and reformat & copy /home to it so I might stand a chance of recovering my work. Have fun Charles cuz I sure as heck am not. > > I don't think you need to replace every cable (power and data) at > once. If you locate which drive is on ata6 now, and move it to > another port, then whether the error follows the drive or stays with > the port will provide useful information. > Its in a card cage with a big fan in front and the psu blocking the rear, It will be a powerdown to do that. But I don't have much hope, the cable I unplugged to get it off the bus was plugged in correctly. If I can get the power cable unplugged, then its drawer can be removed from the front. > Just try to only change one thing at a time so if symptoms do change > then you can tell what you did to provoke that. That would be nice, if the change was easy to do insitu. Its not. > Cheers, > Andy > > -- > https://bitfolk.com/ -- No-nonsense VPS hosting > > . 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: got a mdadm puzzler
Hello, On Sat, Mar 12, 2022 at 01:06:39PM -0500, gene heskett wrote: > On Saturday, 12 March 2022 08:50:07 EST Andy Smith wrote: > > I think it still might be worth changing the cable and/or moving the > > drive about to see if the error follows the drive or stays with the > > port. […] > Difficult at best. All 4 drives from the same purchase, mounted 2 to the > 3.5" adapter, and all 4 shoved into a front panel-less drive cage below > the floppy slot in a huge tower case about 17 yo. Rather than blame data > cables, I'd start by changing out the power splitter cables, this psu > doesn't have near enough sata power plugs for 7 drives, only 1 of which > is spinning rust. I don't think you need to replace every cable (power and data) at once. If you locate which drive is on ata6 now, and move it to another port, then whether the error follows the drive or stays with the port will provide useful information. Just try to only change one thing at a time so if symptoms do change then you can tell what you did to provoke that. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: got a mdadm puzzler
On Saturday, 12 March 2022 08:50:07 EST Andy Smith wrote: > Hello, > > On Fri, Mar 11, 2022 at 02:11:23PM -0500, gene heskett wrote: > > On Friday, 11 March 2022 13:11:14 EST Andy Smith wrote: > > > Hello, > > > > > > On Thu, Mar 10, 2022 at 07:18:56AM -0500, gene heskett wrote: > > > > 2. I've had since the last of about 20 installs of bullseye, a > > > > very > > > > early boot message about ata6 at the 10 and 20 second marks of > > > > the > > > > reboot IF it was not a full powerdown reboot. > > > > > > Did you not at any point think that letting us know what the exact > > > error message was would be useful here? > > > > IF that error message ever made it to the logs, I don't know which > > one. Its output to the screen, but I'll grep syslog for ata6. Found > > some, first instance was reboot, 2nd instance was bootup from a full > > powerdown of about 5 seconds: > > > > Mar 8 15:55:01 coyote kernel: [0.699889] ata6: SATA max UDMA/133 > > abar m2048@0xdf34b000 port 0xdf34b380 irq 126 > > Mar 8 15:55:01 coyote kernel: [6.071345] ata6: link is slow to > > respond, please be patient (ready=0) > > Mar 8 15:55:01 coyote kernel: [ 10.759342] ata6: COMRESET failed > > (errno=-16) > > Okay well this is nothing to do with your RAID, it's at a much lower > level. > > I'd suspect a faulty drive if it wasn't for the fact that you say it > doesn't happen if you boot from power off, only from a reboot. > > I think it still might be worth changing the cable and/or moving the > drive about to see if the error follows the drive or stays with the > port. > > Do you have multiple of this model of drive? If so then it would be > interesting that it only happens with one of them - again points to > hardware problem. But if you only have the one then you can't tell > that. > > > Mar 8 15:56:06 coyote kernel: [1.000270] ata6.00: ATA-9: > > ST2000DM001-1ER164, CC25, max UDMA/133 > > Hopefully that model number and serial gives you enough information > to locate the correct drive. > Difficult at best. All 4 drives from the same purchase, mounted 2 to the 3.5" adapter, and all 4 shoved into a front panel-less drive cage below the floppy slot in a huge tower case about 17 yo. Rather than blame data cables, I'd start by changing out the power splitter cables, this psu doesn't have near enough sata power plugs for 7 drives, only 1 of which is spinning rust. But I'll have to order some more as I think I've only 1 spare left from building it. But I just checked, all splitters left are old 4 pin molex's. I have enough cables to change all the data cables, black ones of course since the pretty red ones are 3 year cables, maximum. And I'm out in small town america, so I'll see what amazon has. Maybe they csn simplify the mess I have for power cabling now. 4 pack of molex to sata splitters, s/b here Monday. Thank you Andy. > Cheers, > Andy > > -- > https://bitfolk.com/ -- No-nonsense VPS hosting > > . 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: got a mdadm puzzler
Hello, On Fri, Mar 11, 2022 at 02:11:23PM -0500, gene heskett wrote: > On Friday, 11 March 2022 13:11:14 EST Andy Smith wrote: > > Hello, > > > > On Thu, Mar 10, 2022 at 07:18:56AM -0500, gene heskett wrote: > > > 2. I've had since the last of about 20 installs of bullseye, a very > > > early boot message about ata6 at the 10 and 20 second marks of the > > > reboot IF it was not a full powerdown reboot. > > > > Did you not at any point think that letting us know what the exact > > error message was would be useful here? > > > IF that error message ever made it to the logs, I don't know which one. > Its output to the screen, but I'll grep syslog for ata6. Found some, > first instance was reboot, 2nd instance was bootup from a full powerdown > of about 5 seconds: > > Mar 8 15:55:01 coyote kernel: [0.699889] ata6: SATA max UDMA/133 > abar m2048@0xdf34b000 port 0xdf34b380 irq 126 > Mar 8 15:55:01 coyote kernel: [6.071345] ata6: link is slow to > respond, please be patient (ready=0) > Mar 8 15:55:01 coyote kernel: [ 10.759342] ata6: COMRESET failed > (errno=-16) Okay well this is nothing to do with your RAID, it's at a much lower level. I'd suspect a faulty drive if it wasn't for the fact that you say it doesn't happen if you boot from power off, only from a reboot. I think it still might be worth changing the cable and/or moving the drive about to see if the error follows the drive or stays with the port. Do you have multiple of this model of drive? If so then it would be interesting that it only happens with one of them - again points to hardware problem. But if you only have the one then you can't tell that. > Mar 8 15:56:06 coyote kernel: [1.000270] ata6.00: ATA-9: > ST2000DM001-1ER164, CC25, max UDMA/133 Hopefully that model number and serial gives you enough information to locate the correct drive. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: got a mdadm puzzler
On Friday, 11 March 2022 13:11:14 EST Andy Smith wrote: > Hello, > > On Thu, Mar 10, 2022 at 07:18:56AM -0500, gene heskett wrote: > > 2. I've had since the last of about 20 installs of bullseye, a very > > early boot message about ata6 at the 10 and 20 second marks of the > > reboot IF it was not a full powerdown reboot. > > Did you not at any point think that letting us know what the exact > error message was would be useful here? > IF that error message ever made it to the logs, I don't know which one. Its output to the screen, but I'll grep syslog for ata6. Found some, first instance was reboot, 2nd instance was bootup from a full powerdown of about 5 seconds: Mar 8 15:55:01 coyote kernel: [0.699889] ata6: SATA max UDMA/133 abar m2048@0xdf34b000 port 0xdf34b380 irq 126 Mar 8 15:55:01 coyote kernel: [6.071345] ata6: link is slow to respond, please be patient (ready=0) Mar 8 15:55:01 coyote kernel: [ 10.759342] ata6: COMRESET failed (errno=-16) Mar 8 15:55:01 coyote kernel: [ 16.111352] ata6: link is slow to respond, please be patient (ready=0) Mar 8 15:55:01 coyote kernel: [ 20.791354] ata6: COMRESET failed (errno=-16) Mar 8 15:55:01 coyote kernel: [ 26.143351] ata6: link is slow to respond, please be patient (ready=0) Mar 8 15:55:01 coyote kernel: [ 55.843357] ata6: COMRESET failed (errno=-16) Mar 8 15:55:01 coyote kernel: [ 55.843417] ata6: limiting SATA link speed to 3.0 Gbps Mar 8 15:55:01 coyote kernel: [ 60.895357] ata6: COMRESET failed (errno=-16) Mar 8 15:55:01 coyote kernel: [ 60.895417] ata6: reset failed, giving up 2nd instance, after power down Mar 8 15:56:06 coyote kernel: [0.684458] ata6: SATA max UDMA/133 abar m2048@0xdf34b000 port 0xdf34b380 irq 127 Mar 8 15:56:06 coyote kernel: [0.998471] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 8 15:56:06 coyote kernel: [0.999415] ata6.00: ACPI cmd ef/ 10:06:00:00:00:00 (SET FEATURES) succeeded Mar 8 15:56:06 coyote kernel: [0.999416] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Mar 8 15:56:06 coyote kernel: [0.999417] ata6.00: ACPI cmd b1/ c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Mar 8 15:56:06 coyote kernel: [1.000270] ata6.00: ATA-9: ST2000DM001-1ER164, CC25, max UDMA/133 Mar 8 15:56:06 coyote kernel: [1.000272] ata6.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA Mar 8 15:56:06 coyote kernel: [1.001605] ata6.00: ACPI cmd ef/ 10:06:00:00:00:00 (SET FEATURES) succeeded Mar 8 15:56:06 coyote kernel: [1.001606] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Mar 8 15:56:06 coyote kernel: [1.001607] ata6.00: ACPI cmd b1/ c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Mar 8 15:56:06 coyote kernel: [1.002460] ata6.00: configured for UDMA/133 And this is the bootup I'm runniing on. > > So how do I go about querying mdadm to determine whats going south > > here? > As is so often the case with the problems you bring up, we risk > going down completely the wrong route because you do not supply > actual error messages or complete problem descriptions and just tell > us that you've decided it's a problem with XYZ subsystem. Much time > is spent looking into XYZ only to later find it was irrelevant or > the process could at least have been seriously improved by knowing > the symptoms to begin with (infamous "enabling IPv6 causes my > compile to fail" memories here). > > > The man pages are quite verbose, but I can't seem to find how to > > query > > what it has, without supplying the device names of all drives that > > s/b > > part of the array. > > > > And why do I see the ata6 error on a reboot, but not on a full > > powerdown reboot? > > So, WHAT IS "THE ATA6 ERROR"? > > Without knowing that it's very hard to speculate but I would point > out that things like "ATA" are way below the level of md which just > knows about block devices. So if you are seeing an "ata6 error" it > most likely has nothing whatsoever to do with your md setup, except > in the sense that if you are having problems with your storage > devices it's obviously going to percolate upwards and cause you RAID > grief too. > > > This is my first experience at software raid, so I am a new bee. My > > fingers are at your command. > > Then I command them to tell us useful information BEFORE you decide > where the problem lies. > > However, if you do want to know more about investigating your mdadm > setup, you already got the hint about cat /proc/mdstat. Here's some > other stuff: > > https://raid.wiki.kernel.org/index.php/Asking_for_help > > Thanks, > Andy > > -- > https://bitfolk.com/ -- No-nonsense VPS hosting > > . 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
Re: got a mdadm puzzler
Hello, On Thu, Mar 10, 2022 at 07:18:56AM -0500, gene heskett wrote: > 2. I've had since the last of about 20 installs of bullseye, a very early > boot message about ata6 at the 10 and 20 second marks of the reboot IF > it was not a full powerdown reboot. Did you not at any point think that letting us know what the exact error message was would be useful here? > So how do I go about querying mdadm to determine whats going south here? As is so often the case with the problems you bring up, we risk going down completely the wrong route because you do not supply actual error messages or complete problem descriptions and just tell us that you've decided it's a problem with XYZ subsystem. Much time is spent looking into XYZ only to later find it was irrelevant or the process could at least have been seriously improved by knowing the symptoms to begin with (infamous "enabling IPv6 causes my compile to fail" memories here). > The man pages are quite verbose, but I can't seem to find how to query > what it has, without supplying the device names of all drives that s/b > part of the array. > > And why do I see the ata6 error on a reboot, but not on a full powerdown > reboot? So, WHAT IS "THE ATA6 ERROR"? Without knowing that it's very hard to speculate but I would point out that things like "ATA" are way below the level of md which just knows about block devices. So if you are seeing an "ata6 error" it most likely has nothing whatsoever to do with your md setup, except in the sense that if you are having problems with your storage devices it's obviously going to percolate upwards and cause you RAID grief too. > This is my first experience at software raid, so I am a new bee. My > fingers are at your command. Then I command them to tell us useful information BEFORE you decide where the problem lies. However, if you do want to know more about investigating your mdadm setup, you already got the hint about cat /proc/mdstat. Here's some other stuff: https://raid.wiki.kernel.org/index.php/Asking_for_help Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: got a mdadm puzzler
On Thu, 10 Mar 2022 08:31:25 -0500 Dan Ritter wrote: > cat /proc/mdstat > > should show you all known md arrays, their types, their > constituent devices and their status. > > The line that starts "personalities" just indicates the types > that it can handle, not the types in use. Right. The entry for each raid array shows its type. E.g. mine is a RAID 5: root@hawk:~# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] md0 : active raid5 sdb1[3] sdc1[0] sdd1[1] 7813768832 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] bitmap: 9/30 pages [36KB], 65536KB chunk unused devices: root@hawk:~# -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: got a mdadm puzzler
gene heskett wrote: ... > when I power up the port the dongle is plugged into, but the new about 2 > weeks ago Acer mouse does not move the onscreen pointer, while a ratty > old logitech works fine but its long lost its bottom skid pads so it > doesn't have that "feel". some glue and bits of nylon plastic cut to shape should work ok. songbird
Re: got a mdadm puzzler
gene heskett wrote: > 3. My home partition is I believe, ata6, which is 4 Samsung EVO-870 1T > ssd's supposedly assembled as raid10, but recent reboots are mentioning a > raid6. > > So how do I go about querying mdadm to determine whats going south here? > The man pages are quite verbose, but I can't seem to find how to query > what it has, without supplying the device names of all drives that s/b > part of the array. cat /proc/mdstat should show you all known md arrays, their types, their constituent devices and their status. The line that starts "personalities" just indicates the types that it can handle, not the types in use. -dsr-
Re: got a mdadm puzzler
On Thursday, 10 March 2022 07:49:30 EST mick crane wrote: > On 2022-03-10 12:18, gene heskett wrote: > > Greetings all; > > > > I just had a bad time rebooting with 2 combined problems.. > > excuse my ignorance but you seem to have a lot of problems because of > doing stuff most haven't attempted. > Is it possible the arrangement is over complicated and that you could > more easily achieve what you want by allocating one task per PC and > communicating with them over ssh ? I actually do quite a bit it my work that way. But this is the master machine for all of it. Theres 5 other machines here that I ssh into about 99% of the time when I'm not asking them to actually move machinery that might weight a thousand pounds. This is the only comfy chair in the bunch. 4 of them are dedicated to running cnc machines, and the 5th runs cura to drive a couple 3d printers after I design what I need next in OpenSCAD on this machine. I build this stuff to use, Mick, and it would be nice if it Just Worked. Thanks Mick. > regards > > mick > -- > Key ID4BFEBB31 > > . 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: got a mdadm puzzler
On Thursday, 10 March 2022 07:24:57 EST Andrew M.A. Cater wrote: > On Thu, Mar 10, 2022 at 07:18:56AM -0500, gene heskett wrote: > > Greetings all; > > > > I just had a bad time rebooting with 2 combined problems. > > > > 1. A brand new acer wireless mouse was found of on powerups, but > > refused to move the pointer even in the bios, until that mouse was > > replaced with and older logiteh, and the cable leading to its rx > > dongle was plugged into a usb2 interface on the mobo. Its not found > > if plugged into a usb3 port. > > Probably best for any device with a USB dongle to be plugged in > directly to a socket rather than an extension cable. Range on a > wireless mouse should be maybe 20 feet. > Hi Andy, range isn't, or shouldn't be a problem as its generally 4 to 6 inches. Its about a 5 foot extension cable with a sabrant 4 port, each port power switchable hub on the end of that cable and its been working that way for long before wheezy. Working right now, with an old wireless mouse and its receiver. The log looks fine, both mice are recognized when I power up the port the dongle is plugged into, but the new about 2 weeks ago Acer mouse does not move the onscreen pointer, while a ratty old logitech works fine but its long lost its bottom skid pads so it doesn't have that "feel". > > And why do I see the ata6 error on a reboot, but not on a full > > powerdown reboot? > > Possibly because a full powerdown will flush cache and ensure writes to > disk? It's also worth checking logs and dmesg output to see what is > shown. > > This is my first experience at software raid, so I am a new bee. My > > fingers are at your command. > > > > 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 > > With every good wish, as ever, > > Andy Cater > > > > . 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: got a mdadm puzzler
On 2022-03-10 12:18, gene heskett wrote: Greetings all; I just had a bad time rebooting with 2 combined problems.. excuse my ignorance but you seem to have a lot of problems because of doing stuff most haven't attempted. Is it possible the arrangement is over complicated and that you could more easily achieve what you want by allocating one task per PC and communicating with them over ssh ? regards mick -- Key ID4BFEBB31
Re: got a mdadm puzzler
On Thu, Mar 10, 2022 at 07:18:56AM -0500, gene heskett wrote: > Greetings all; > > I just had a bad time rebooting with 2 combined problems. > > 1. A brand new acer wireless mouse was found of on powerups, but refused > to move the pointer even in the bios, until that mouse was replaced with > and older logiteh, and the cable leading to its rx dongle was plugged > into a usb2 interface on the mobo. Its not found if plugged into a usb3 > port. > Probably best for any device with a USB dongle to be plugged in directly to a socket rather than an extension cable. Range on a wireless mouse should be maybe 20 feet. > > And why do I see the ata6 error on a reboot, but not on a full powerdown > reboot? > Possibly because a full powerdown will flush cache and ensure writes to disk? It's also worth checking logs and dmesg output to see what is shown. > This is my first experience at software raid, so I am a new bee. My > fingers are at your command. > > 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 > With every good wish, as ever, Andy Cater > >
got a mdadm puzzler
Greetings all; I just had a bad time rebooting with 2 combined problems. 1. A brand new acer wireless mouse was found of on powerups, but refused to move the pointer even in the bios, until that mouse was replaced with and older logiteh, and the cable leading to its rx dongle was plugged into a usb2 interface on the mobo. Its not found if plugged into a usb3 port. 2. I've had since the last of about 20 installs of bullseye, a very early boot message about ata6 at the 10 and 20 second marks of the reboot IF it was not a full powerdown reboot. 3. My home partition is I believe, ata6, which is 4 Samsung EVO-870 1T ssd's supposedly assembled as raid10, but recent reboots are mentioning a raid6. So how do I go about querying mdadm to determine whats going south here? The man pages are quite verbose, but I can't seem to find how to query what it has, without supplying the device names of all drives that s/b part of the array. And why do I see the ata6 error on a reboot, but not on a full powerdown reboot? This is my first experience at software raid, so I am a new bee. My fingers are at your command. 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
