HomeSearchPrevious dayNext day

00:40:13jacobk joins
01:02:48BlueMaxima_ joins
01:03:38BlueMaxima quits [Remote host closed the connection]
01:10:48Arcorann (Arcorann) joins
01:12:28sonick quits [Client Quit]
03:16:45pabs quits [Ping timeout: 276 seconds]
03:26:47pabs (pabs) joins
03:27:20Lord_Nightmare2 (Lord_Nightmare) joins
03:27:42jacobk quits [Client Quit]
03:27:42Lord_Nightmare quits [Remote host closed the connection]
03:27:43Lord_Nightmare2 is now known as Lord_Nightmare
03:28:23jacobk joins
03:36:13<@JAA>TIL MS Paint IDE is a thing. I miss 5 minutes ago when I didn't know that existed. https://ms-paint-i.de/
03:38:11<ivan>I thought this was a child LARPing
03:38:27<ivan>https://yarr.is/ he's 20 but maybe it came out earlier
03:38:57<ivan>https://web.archive.org/web/20180416224156/https://ms-paint-i.de/ so age 15 or so
03:39:14<@JAA>Initial commit is from December 2017, most work in 2018/19.
04:11:04AnotherIki joins
04:15:11Iki1 quits [Ping timeout: 268 seconds]
04:33:37BlueMaxima_ quits [Client Quit]
04:43:08Pichu0102 joins
04:52:10Pichu0102 quits [Remote host closed the connection]
04:52:28Pichu0102 joins
04:53:08Pichu0102 quits [Remote host closed the connection]
04:53:40Pichu0102 joins
04:53:47atphoenix_ is now known as atphoenix
05:07:46Iki1 joins
05:11:48AnotherIki quits [Ping timeout: 276 seconds]
05:18:18pabs quits [Ping timeout: 276 seconds]
05:20:31pabs (pabs) joins
05:26:32AnotherIki joins
05:29:37Iki1 quits [Ping timeout: 265 seconds]
05:46:38AnotherIki quits [Remote host closed the connection]
05:46:48AnotherIki joins
05:57:01Iki1 joins
05:59:11AnotherIki quits [Remote host closed the connection]
05:59:11jacobk quits [Client Quit]
06:00:05jacobk joins
06:32:46qwertyasdfuiopghjkl joins
08:29:56qwertyasdfuiopghjkl quits [Client Quit]
08:37:12Meli quits [Ping timeout: 276 seconds]
08:38:30tzt quits [Ping timeout: 268 seconds]
08:43:31Meli (Meli) joins
08:45:07qwertyasdfuiopghjkl joins
09:37:34Meli quits [Ping timeout: 265 seconds]
09:42:45Meli (Meli) joins
10:40:49qwertyasdfuiopghjkl quits [Remote host closed the connection]
10:47:39Meli quits [Client Quit]
10:47:53Meli (Meli) joins
10:52:34tech_exorcist (tech_exorcist) joins
10:56:21tech_exorcist quits [Remote host closed the connection]
10:57:12tech_exorcist (tech_exorcist) joins
11:01:38tech_exorcist quits [Read error: Connection reset by peer]
11:01:59tech_exorcist (tech_exorcist) joins
11:14:11<ivan>has anyone observed idle_c mode on Seagate Exos X16 16TB / SN04 drives causing the drive to spin down completely, as if it were going into standby_z despite that being disabled
11:14:41<ivan>started happening after a year of being totally fine
11:33:18tech_exorcist quits [Ping timeout: 255 seconds]
11:36:02tech_exorcist (tech_exorcist) joins
11:41:12tech_exorcist quits [Remote host closed the connection]
11:46:14qwertyasdfuiopghjkl joins
12:22:43tech_exorcist (tech_exorcist) joins
12:29:20tech_exorcist quits [Remote host closed the connection]
12:29:38tech_exorcist (tech_exorcist) joins
12:56:43qwertyasdfuiopghjkl quits [Remote host closed the connection]
13:15:28tech_exorcist quits [Remote host closed the connection]
13:16:21tech_exorcist (tech_exorcist) joins
13:21:31tech_exorcist quits [Remote host closed the connection]
13:22:09tech_exorcist (tech_exorcist) joins
13:23:12Arcorann quits [Ping timeout: 276 seconds]
13:30:33qwertyasdfuiopghjkl joins
13:31:29Larsenv quits [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
13:41:24pabs quits [Ping timeout: 276 seconds]
13:44:08pabs (pabs) joins
13:51:40tech_exorcist quits [Remote host closed the connection]
13:52:14tech_exorcist (tech_exorcist) joins
14:36:07sonick (sonick) joins
14:48:42<atphoenix>ivan, seems that would be a firmware thing, so unless the firmware changed...or maybe the OS libraries that talk to the firmware changed...I'm not sure what would explain a difference in behavior
14:53:22<atphoenix>it might be a case of a (new) OS library bug...or even a bug fix ('fixing the glitch'), that changed the behavior. I know that such things have happened in the past, where software relied on certain undocumented or unintended behavior of other software, and then that behavior changed, thus breaking the software.
14:53:26yawkat` quits [Ping timeout: 268 seconds]
15:19:07tech_exorcist quits [Client Quit]
15:29:57jacobk quits [Ping timeout: 276 seconds]
15:29:59yawkat (yawkat) joins
15:35:14Meli quits [Ping timeout: 265 seconds]
15:39:58tech_exorcist (tech_exorcist) joins
15:42:37Meli (Meli) joins
15:59:53tech_exorcist quits [Client Quit]
16:09:10tech_exorcist (tech_exorcist) joins
16:12:16tech_exorcist quits [Remote host closed the connection]
16:13:14tech_exorcist (tech_exorcist) joins
16:25:33tech_exorcist quits [Client Quit]
16:26:21tech_exorcist (tech_exorcist) joins
16:32:31<schwarzkatz|m>I have 2 of these drives and they always spin down. Is that not normal behavior?
16:36:54Meli quits [Ping timeout: 276 seconds]
16:44:41Meli (Meli) joins
16:48:10HP_Archivist (HP_Archivist) joins
17:26:53holbrooke quits [Ping timeout: 265 seconds]
17:38:08tech_exorcist quits [Client Quit]
17:40:04tech_exorcist (tech_exorcist) joins
17:40:40HP_Archivist quits [Client Quit]
18:07:15<ivan>they’re not supposed to fully spin down unless standby_z is enabled which is not, by default
18:20:57<schwarzkatz|m>Hm... I read somewhere that spinning them up/down is the main cause for failure. And since these are server hdds, it would be a better idea to just leave them running, right? Should I use a tool like KeepAliveHD to do that, what do you think?
18:29:27tech_exorcist quits [Client Quit]
18:30:40tzt (tzt) joins
18:37:48Meli quits [Ping timeout: 276 seconds]
18:42:02Meli (Meli) joins
18:55:39Larsenv_ (Larsenv) joins
21:07:21BlueMaxima joins
22:24:28Arcorann (Arcorann) joins
22:37:51katocala quits [Remote host closed the connection]

HomeSearchPrevious dayNext day