Quote

Low memory detected, aborting ...

Your system is running out of RAM.

 

It seems something is filling your rootfs.

Quote

Filesystem        1K-blocks        Used   Available Use% Mounted on
rootfs             32784104    27564256     5219848  85% /

 

1 hour ago, fschris said:

Any ideas why my pre clear is failing on 2 new drives?

1 hour ago, Kilrah said:

It seems something is filling your rootfs.

Quote

Filesystem        1K-blocks        Used   Available Use% Mounted on
rootfs             32784104    27564256     5219848  85% /

 

The usual reason for filling rootfs is something, for example a container host volume, specifying a path to something that doesn't actually exist, such as a pool that got renamed or is missing.

On 3/8/2025 at 11:56 AM, daithi said:

Trying to update the plugin, getting the following error:
 

6.12.15, Unraid Patch installed and latest patches applied.
@NoBigCat further up in the thread has suggested updating to 7.0.0 and then 7.0.1, anyone else having this issue and found any other solutions? A little gun shy updating to 7.

This actually looks like it was caused by an error on an older version of Connect when it got updated.   Not related at all to 7.0.1.  Easiest solution is a reboot and you're good to go

2 hours ago, trurl said:

The usual reason for filling rootfs is something, for example a container host volume, specifying a path to something that doesn't actually exist, such as a pool that got renamed or is missing.

I just did that command -  and attached the output . I have 128G of Ram and my Cache pool Is a 1TB m.2 drive

 

I am running plex but the dockers are on my cache drive...

 

Can you see anything weird from the images i attached?

 

 

 

Edited March 12, 20251 yr by fschris

1 hour ago, fschris said:

attached the output . I have 128G of Ram and my Cache pool Is a 1TB m.2 drive

 

I am running plex but the dockers are on my cache drive...

 

Can you see anything weird from the images i attached?

 

 

 

The OS runs in RAM (in rootfs). A certain amount of your RAM is reserved for this.

That shows rootfs is no longer full. Did you reboot?

4 hours ago, trurl said:

The OS runs in RAM (in rootfs). A certain amount of your RAM is reserved for this.

That shows rootfs is no longer full. Did you reboot?

I did not reboot or anything weird like that. 

If you have plex or similar set to transcode to ram it probably had a bunch of leftover stuff in its transcode dir that got cleaned up in the meantime.

On 3/12/2025 at 8:18 AM, Squid said:

This actually looks like it was caused by an error on an older version of Connect when it got updated.   Not related at all to 7.0.1.  Easiest solution is a reboot and you're good to go

This worked

On 3/13/2025 at 7:32 PM, Kilrah said:

If you have plex or similar set to transcode to ram it probably had a bunch of leftover stuff in its transcode dir that got cleaned up in the meantime.

it ran through the preclear just fine now! Thanks everyone. I also learned a few things - appreciate it.

Hi,

 

I'm hoping someone can help me out ?

 

I've started to pre-clear two new 20TB WD element drives beofre I shuck them.

 

Both failed (But i think this is because they Overheated, they got to 52c).

 

I've tried to preclear again one at a time, but preclear is stuck on "Starting", I've tried rebooting the server and using different USB ports (They only work on the ports I first used, the others cant see the drives).

 

Any help would be great as I'm fresh out of ideas.

 

Thanks

 

D.

 

Added the preclear logs, but they dont say much

NEO-unassigned.devices.preclear-20250403-1210.zip

OK, uninstalled and reinstalled the plugin and it seems to be working now.

 

I'm going to have to do 1 disk at a time to be on the safe side.

 

I'll let you know how I get on.

 

If this was already posted, my apologies, but I searched and did not find it.

 

It looks like the PreClear status no longer shows up on the Main tab page under the Unassaigned Disk listing.  Pretty sure it used to display the status here.  Or am I crazy?

 

unRAID version 7.0.1  

 

 

Edited April 4, 20251 yr by jimeez
additional info

Got removed some time ago, see footer bar or tools->preclear.

14 hours ago, Kilrah said:

Got removed some time ago, see footer bar or tools->preclear.

Hmmm...must have missed that one.  Thanks for the info.  Wish they hadn't done that though.

 

It also does NOT show up in my footer bar, but can successfully see it on the actual PreClear page. 

 

Thanks again.

Hi guys, just finished setting up my server (first time using Unraid) and built my array with parity (3x 12tb factory re-certified ST12000VN0007). I missed the recommendation to do a preclear before building the array. I haven't added any data yet that isn't already backed up, can/should I go back and try to perform a preclear on these? If so, what's the best way to go about this?

 

I am running 7.0.1 for reference.

1 hour ago, Aquarius4510 said:

(3x 12tb factory re-certified ST12000VN0007)

Do an extended self-test on each and post the report.

10 hours ago, trurl said:

Do an extended self-test on each and post the report.

I triggered these while the array was being built.

ST12000VN0007-2GS116_ZJV2ANAZ-20250410-1935.txt ST12000VN0007-2GS116_ZJV3D8G8-20250410-1937.txt ST12000VN0007-2GS116_ZJV1FSAB-20250410-1936.txt

Looks good!

Hi!

i got myself a new drive but directly when i start doing a preclean it FLOODS errors in the logs.

Jul 2 22:37:32 unRAID kernel: sd 4:0:0:0: [sdc] tag#538 CDB: opcode=0x88 88 00 00 00 00 00 03 fc 70 60 00 00 08 00 00 00

Jul 2 22:37:32 unRAID kernel: I/O error, dev sdc, sector 66867264 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:32 unRAID kernel: I/O error, dev sdc, sector 66875488 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:32 unRAID kernel: sd 4:0:0:0: [sdc] tag#426 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:32 unRAID kernel: sd 4:0:0:0: [sdc] tag#426 CDB: opcode=0x88 88 00 00 00 00 00 03 fc e4 a8 00 00 04 00 00 00

Jul 2 22:37:32 unRAID kernel: I/O error, dev sdc, sector 66905256 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:32 unRAID kernel: sd 4:0:0:0: [sdc] tag#407 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:32 unRAID kernel: sd 4:0:0:0: [sdc] tag#407 CDB: opcode=0x88 88 00 00 00 00 00 03 fc d4 40 00 00 04 00 00 00

Jul 2 22:37:32 unRAID kernel: I/O error, dev sdc, sector 66901056 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:32 unRAID kernel: I/O error, dev sdc, sector 66900032 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:32 unRAID kernel: I/O error, dev sdc, sector 66896960 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#428 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#424 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#424 CDB: opcode=0x88 88 00 00 00 00 00 04 43 ce b0 00 00 07 38 00 00

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71552688 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#415 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#423 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#415 CDB: opcode=0x88 88 00 00 00 00 00 04 43 a7 f0 00 00 04 00 00 00

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71542768 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#423 CDB: opcode=0x88 88 00 00 00 00 00 04 43 c8 80 00 00 06 30 00 00

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71551104 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#414 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#414 CDB: opcode=0x88 88 00 00 00 00 00 04 43 a3 f0 00 00 04 00 00 00

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71541744 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#428 CDB: opcode=0x88 88 00 00 00 00 00 04 43 ff 68 00 00 12 20 00 00

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71565160 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#421 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#421 CDB: opcode=0x88 88 00 00 00 00 00 04 43 c0 00 00 00 08 80 00 00

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71548928 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#413 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#413 CDB: opcode=0x88 88 00 00 00 00 00 04 43 9f f0 00 00 04 00 00 00

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#427 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#420 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71540720 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#420 CDB: opcode=0x88 88 00 00 00 00 00 04 43 bc 00 00 00 04 00 00 00

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#427 CDB: opcode=0x88 88 00 00 00 00 00 04 43 ef 68 00 00 10 00 00 00

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71561064 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71547904 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#412 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:41 unRAID kernel: sd 4:0:0:0: [sdc] tag#412 CDB: opcode=0x88 88 00 00 00 00 00 04 43 9b d0 00 00 04 20 00 00

Jul 2 22:37:41 unRAID kernel: I/O error, dev sdc, sector 71539664 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#775 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#775 CDB: opcode=0x88 88 00 00 00 00 00 04 64 27 88 00 00 08 10 00 00

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#786 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73672584 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#786 CDB: opcode=0x88 88 00 00 00 00 00 04 64 99 c0 00 00 04 00 00 00

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73701824 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#887 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#887 CDB: opcode=0x88 88 00 00 00 00 00 04 63 fd d0 00 00 04 00 00 00

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73661904 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#774 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#774 CDB: opcode=0x88 88 00 00 00 00 00 04 64 1f 88 00 00 08 00 00 00

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73670536 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#886 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#787 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#886 CDB: opcode=0x88 88 00 00 00 00 00 04 63 f9 d0 00 00 04 00 00 00

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#787 CDB: opcode=0x88 88 00 00 00 00 00 04 64 9d c0 00 00 04 00 00 00

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73660880 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73702848 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#807 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#807 CDB: opcode=0x88 88 00 00 00 00 00 04 64 ad c0 00 00 04 00 00 00

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73706944 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#784 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#784 CDB: opcode=0x88 88 00 00 00 00 00 04 64 82 88 00 00 10 00 00 00

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73695880 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#806 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#773 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#806 CDB: opcode=0x88 88 00 00 00 00 00 04 64 a9 c0 00 00 04 00 00 00

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73659856 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 3

Jul 2 22:37:47 unRAID kernel: sd 4:0:0:0: [sdc] tag#773 CDB: opcode=0x88 88 00 00 00 00 00 04 64 17 88 00 00 08 00 00 00

Jul 2 22:37:47 unRAID kernel: I/O error, dev sdc, sector 73705920 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3

What can be done to fix this? i already have the same model of drive since before. This is the only drive that has errors in the logs.

Stop it and run a SMART test. Seems like the drive is probably failing.

On 7/2/2025 at 11:14 PM, Kilrah said:

Stop it and run a SMART test. Seems like the drive is probably failing.

Did not work. Tried it two times and it states abort by host. or something like that.. Did a RMA on that drive and just now got a new one and i get the same errors.

Then time to check or replace SATA/power cables for that drive. What is it connected to? Motherboard or an HBA? If the latter is it properly cooled?

1 hour ago, Kilrah said:

Then time to check or replace SATA/power cables for that drive. What is it connected to? Motherboard or an HBA? If the latter is it properly cooled?

It's connected to a Gooxi RMC4124-BPE-12G backplane and from it two "SFF-8643 -> SFF-8643" cables to a Supermicro 3008 HBA with latest firmware. I did however change the cables less then a year ago. My suspicion right now is "power draw" so i will try to add extra Molex cables and see if that helps..

3 hours ago, Kilrah said:

Then time to check or replace SATA/power cables for that drive. What is it connected to? Motherboard or an HBA? If the latter is it properly cooled?

Cleaned the chassi and added two more power cables for the backplane. This did nothing. Same errors. So either my

1. HBA is going bad

2. my HBA don't like the drives

3. The cables are going bad yet again after just a year..

4. The motherboard is going bad. It's 11 years old..

   But I really don't think it's none of that.. The rest of the drives work fine over the same cables and same backplane.

What else can it be? Incompatibility?

I've been running the script on 2 new drives simultaneously and saw this in the log for one of them:

Jul 16 20:40:24 preclear_disk_ZR5*: Zeroing: zeroing the disk started 1 of 5 retries...

Jul 16 20:40:24 preclear_disk_ZR5*: Zeroing: emptying the MBR.

Jul 17 01:11:58 preclear_disk_ZR5*: Zeroing: progress - 25% zeroed @ 239 MB/s

Jul 17 06:04:57 preclear_disk_ZR5*: Zeroing: progress - 50% zeroed @ 217 MB/s

Jul 17 11:38:18 preclear_disk_ZR5*: Zeroing: progress - 75% zeroed @ 181 MB/s

Jul 17 19:04:08 preclear_disk_ZR5*: killing smartctl with pid 1024462 - probably stalled ...

Jul 17 19:04:08 preclear_disk_ZR5*: Pause (smartctl run time: 35s)

Jul 17 19:04:10 preclear_disk_ZR5*: Paused

Jul 17 19:04:30 preclear_disk_ZR5*: Resumed

Jul 17 19:04:33 preclear_disk_ZR5*: Zeroing: zeroing the disk completed!

After some searching I'm unable to find much about this, was just curious if anyone knows if could mean there's something up with the drive or if a stall in smartctl is something that can just happen. Sadly I can't look in the system log for when it happened because some other script was seemingly executing smartctl --scan every 8 seconds that I've since killed.

Edited July 18, 2025Jul 18 by Mayonaise