Data Loss Problems

trurl · January 30, 2021

Please attach directly to your post instead of linking to external sites.

I did look at that .png and I don't understand your question. Maybe you could explain further.

stingray060 · January 30, 2021

vault-diagnostics-20210129-2309.zip

When i press mount it just goes grey for a couple of seconds, then returns to "mount"

JorgeB · January 30, 2021

You're having controller or power/connections problems, that disk ended up dropping offline:

Jan 29 16:06:27 Vault kernel: ata12.00: revalidation failed (errno=-2)
Jan 29 16:06:32 Vault kernel: ata12: hard resetting link
Jan 29 16:06:32 Vault kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 29 16:06:32 Vault kernel: ata12.00: both IDENTIFYs aborted, assuming NODEV
Jan 29 16:06:32 Vault kernel: ata12.00: revalidation failed (errno=-2)
Jan 29 16:06:32 Vault kernel: ata12.00: disabled
Jan 29 16:06:32 Vault kernel: ata12: EH complete
Jan 29 16:06:32 Vault kernel: sd 12:0:0:0: [sdf] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Jan 29 16:06:32 Vault kernel: sd 12:0:0:0: [sdf] tag#7 CDB: opcode=0x28 28 00 03 ee 37 60 00 00 20 00
Jan 29 16:06:32 Vault kernel: print_req_error: I/O error, dev sdf, sector 65943392
Jan 29 16:06:32 Vault kernel: XFS (sdf1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x3ee3720 len 32 error 5
Jan 29 16:06:32 Vault kernel: XFS (sdf1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5.

Note that the issues are not limited to that disk:

Jan 29 15:47:31 Vault kernel: ata2.00: status: { DRDY }
Jan 29 15:47:31 Vault kernel: ata2.00: failed command: READ FPDMA QUEUED
Jan 29 15:47:31 Vault kernel: ata2.00: cmd 60/88:90:80:90:e0/00:00:e8:00:00/40 tag 18 ncq dma 69632 in
Jan 29 15:47:31 Vault kernel:         res 40/00:60:98:ff:08/00:00:77:00:00/40 Emask 0x52 (ATA bus error)
Jan 29 15:47:31 Vault kernel: ata2.00: status: { DRDY }
Jan 29 15:47:31 Vault kernel: ata2: hard resetting link
Jan 29 15:47:32 Vault kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 29 15:47:32 Vault kernel: ata11.00: configured for UDMA/33
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#27 Sense Key : 0x5 [current]
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#27 ASC=0x21 ASCQ=0x4
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#27 CDB: opcode=0x28 28 00 20 88 e0 b0 00 02 00 00
Jan 29 15:47:32 Vault kernel: print_req_error: I/O error, dev sde, sector 545841328
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#28 Sense Key : 0x5 [current]
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#28 ASC=0x21 ASCQ=0x4
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#28 CDB: opcode=0x28 28 00 20 88 e2 b0 00 02 00 00
Jan 29 15:47:32 Vault kernel: print_req_error: I/O error, dev sde, sector 545841840
Jan 29 15:47:32 Vault kernel: ata11: EH complete
Jan 29 15:47:33 Vault kernel: ata11.00: exception Emask 0x10 SAct 0x80 SErr 0x90300 action 0xe frozen
Jan 29 15:47:33 Vault kernel: ata11.00: irq_stat 0x00400000, PHY RDY changed
Jan 29 15:47:33 Vault kernel: ata11: SError: { UnrecovData Persist PHYRdyChg 10B8B }
Jan 29 15:47:33 Vault kernel: ata11.00: failed command: READ FPDMA QUEUED
Jan 29 15:47:33 Vault kernel: ata11.00: cmd 60/00:38:a8:0d:89/02:00:20:00:00/40 tag 7 ncq dma 262144 in
Jan 29 15:47:33 Vault kernel:         res 40/00:38:a8:0d:89/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
Jan 29 15:47:33 Vault kernel: ata11.00: status: { DRDY }
Jan 29 15:47:33 Vault kernel: ata11: hard resetting link
Jan 29 15:47:37 Vault kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 29 15:47:37 Vault kernel: ata11.00: configured for UDMA/33
Jan 29 15:47:37 Vault kernel: sd 11:0:0:0: [sde] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 29 15:47:37 Vault kernel: sd 11:0:0:0: [sde] tag#7 Sense Key : 0x5 [current]
Jan 29 15:47:37 Vault kernel: sd 11:0:0:0: [sde] tag#7 ASC=0x21 ASCQ=0x4
Jan 29 15:47:37 Vault kernel: sd 11:0:0:0: [sde] tag#7 CDB: opcode=0x28 28 00 20 89 0d a8 00 02 00 00
Jan 29 15:47:37 Vault kernel: print_req_error: I/O error, dev sde, sector 545852840
Jan 29 15:47:37 Vault kernel: ata11: EH complete
Jan 29 15:47:39 Vault kernel: ata11.00: exception Emask 0x10 SAct 0xc SErr 0x90300 action 0xe frozen
Jan 29 15:47:39 Vault kernel: ata11.00: irq_stat 0x00400000, PHY RDY changed
Jan 29 15:47:39 Vault kernel: ata11: SError: { UnrecovData Persist PHYRdyChg 10B8B }
Jan 29 15:47:39 Vault kernel: ata11.00: failed command: READ FPDMA QUEUED
Jan 29 15:47:39 Vault kernel: ata11.00: cmd 60/00:10:e8:00:0f/02:00:3b:00:00/40 tag 2 ncq dma 262144 in
Jan 29 15:47:39 Vault kernel:         res 40/00:10:e8:00:0f/00:00:3b:00:00/40 Emask 0x10 (ATA bus error)
Jan 29 15:47:39 Vault kernel: ata11.00: status: { DRDY }
Jan 29 15:47:39 Vault kernel: ata11.00: failed command: READ FPDMA QUEUED
Jan 29 15:47:39 Vault kernel: ata11.00: cmd 60/00:18:e8:02:0f/02:00:3b:00:00/40 tag 3 ncq dma 262144 in
Jan 29 15:47:39 Vault kernel:         res 40/00:10:e8:00:0f/00:00:3b:00:00/40 Emask 0x10 (ATA bus error)
Jan 29 15:47:39 Vault kernel: ata11.00: status: { DRDY }
Jan 29 15:47:39 Vault kernel: ata11: hard resetting link
Jan 29 15:47:41 Vault kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 29 15:47:41 Vault kernel: ata2.00: configured for UDMA/33
Jan 29 15:47:41 Vault kernel: ata2: EH complete
Jan 29 15:47:42 Vault kernel: ata1.00: exception Emask 0x50 SAct 0xffffe00 SErr 0x30802 action 0xe frozen
Jan 29 15:47:42 Vault kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed
Jan 29 15:47:42 Vault kernel: ata1: SError: { RecovComm HostInt PHYRdyChg PHYInt }
Jan 29 15:47:42 Vault kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 29 15:47:42 Vault kernel: ata1.00: cmd 61/08:48:40:91:e0/00:00:e8:00:00/40 tag 9 ncq dma 4096 out
Jan 29 15:47:42 Vault kernel:         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error)
Jan 29 15:47:42 Vault kernel: ata1.00: status: { DRDY }
Jan 29 15:47:42 Vault kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 29 15:47:42 Vault kernel: ata1.00: cmd 61/08:50:48:91:e0/00:00:e8:00:00/40 tag 10 ncq dma 4096 out
Jan 29 15:47:42 Vault kernel:         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error)
Jan 29 15:47:42 Vault kernel: ata1.00: status: { DRDY }
Jan 29 15:47:42 Vault kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 29 15:47:42 Vault kernel: ata1.00: cmd 61/08:58:50:91:e0/00:00:e8:00:00/40 tag 11 ncq dma 4096 out
Jan 29 15:47:42 Vault kernel:         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error)
Jan 29 15:47:42 Vault kernel: ata1.00: status: { DRDY }
Jan 29 15:47:42 Vault kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 29 15:47:42 Vault kernel: ata1.00: cmd 61/20:60:00:0e:09/02:00:77:00:00/40 tag 12 ncq dma 278528 out
Jan 29 15:47:42 Vault kernel:         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error)
Jan 29 15:47:42 Vault kernel: ata1.00: status: { DRDY }

Check all cables and/or try a different power supply.

stingray060 · January 30, 2021

12 minutes ago, JorgeB said:

You're having controller or power/connections problems, that disk ended up dropping offline:


Jan 29 16:06:27 Vault kernel: ata12.00: revalidation failed (errno=-2)
Jan 29 16:06:32 Vault kernel: ata12: hard resetting link
Jan 29 16:06:32 Vault kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 29 16:06:32 Vault kernel: ata12.00: both IDENTIFYs aborted, assuming NODEV
Jan 29 16:06:32 Vault kernel: ata12.00: revalidation failed (errno=-2)
Jan 29 16:06:32 Vault kernel: ata12.00: disabled
Jan 29 16:06:32 Vault kernel: ata12: EH complete
Jan 29 16:06:32 Vault kernel: sd 12:0:0:0: [sdf] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Jan 29 16:06:32 Vault kernel: sd 12:0:0:0: [sdf] tag#7 CDB: opcode=0x28 28 00 03 ee 37 60 00 00 20 00
Jan 29 16:06:32 Vault kernel: print_req_error: I/O error, dev sdf, sector 65943392
Jan 29 16:06:32 Vault kernel: XFS (sdf1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x3ee3720 len 32 error 5
Jan 29 16:06:32 Vault kernel: XFS (sdf1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5.

Note that the issues are not limited to that disk:


Jan 29 15:47:31 Vault kernel: ata2.00: status: { DRDY }
Jan 29 15:47:31 Vault kernel: ata2.00: failed command: READ FPDMA QUEUED
Jan 29 15:47:31 Vault kernel: ata2.00: cmd 60/88:90:80:90:e0/00:00:e8:00:00/40 tag 18 ncq dma 69632 in
Jan 29 15:47:31 Vault kernel:         res 40/00:60:98:ff:08/00:00:77:00:00/40 Emask 0x52 (ATA bus error)
Jan 29 15:47:31 Vault kernel: ata2.00: status: { DRDY }
Jan 29 15:47:31 Vault kernel: ata2: hard resetting link
Jan 29 15:47:32 Vault kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 29 15:47:32 Vault kernel: ata11.00: configured for UDMA/33
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#27 Sense Key : 0x5 [current]
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#27 ASC=0x21 ASCQ=0x4
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#27 CDB: opcode=0x28 28 00 20 88 e0 b0 00 02 00 00
Jan 29 15:47:32 Vault kernel: print_req_error: I/O error, dev sde, sector 545841328
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#28 Sense Key : 0x5 [current]
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#28 ASC=0x21 ASCQ=0x4
Jan 29 15:47:32 Vault kernel: sd 11:0:0:0: [sde] tag#28 CDB: opcode=0x28 28 00 20 88 e2 b0 00 02 00 00
Jan 29 15:47:32 Vault kernel: print_req_error: I/O error, dev sde, sector 545841840
Jan 29 15:47:32 Vault kernel: ata11: EH complete
Jan 29 15:47:33 Vault kernel: ata11.00: exception Emask 0x10 SAct 0x80 SErr 0x90300 action 0xe frozen
Jan 29 15:47:33 Vault kernel: ata11.00: irq_stat 0x00400000, PHY RDY changed
Jan 29 15:47:33 Vault kernel: ata11: SError: { UnrecovData Persist PHYRdyChg 10B8B }
Jan 29 15:47:33 Vault kernel: ata11.00: failed command: READ FPDMA QUEUED
Jan 29 15:47:33 Vault kernel: ata11.00: cmd 60/00:38:a8:0d:89/02:00:20:00:00/40 tag 7 ncq dma 262144 in
Jan 29 15:47:33 Vault kernel:         res 40/00:38:a8:0d:89/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
Jan 29 15:47:33 Vault kernel: ata11.00: status: { DRDY }
Jan 29 15:47:33 Vault kernel: ata11: hard resetting link
Jan 29 15:47:37 Vault kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 29 15:47:37 Vault kernel: ata11.00: configured for UDMA/33
Jan 29 15:47:37 Vault kernel: sd 11:0:0:0: [sde] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 29 15:47:37 Vault kernel: sd 11:0:0:0: [sde] tag#7 Sense Key : 0x5 [current]
Jan 29 15:47:37 Vault kernel: sd 11:0:0:0: [sde] tag#7 ASC=0x21 ASCQ=0x4
Jan 29 15:47:37 Vault kernel: sd 11:0:0:0: [sde] tag#7 CDB: opcode=0x28 28 00 20 89 0d a8 00 02 00 00
Jan 29 15:47:37 Vault kernel: print_req_error: I/O error, dev sde, sector 545852840
Jan 29 15:47:37 Vault kernel: ata11: EH complete
Jan 29 15:47:39 Vault kernel: ata11.00: exception Emask 0x10 SAct 0xc SErr 0x90300 action 0xe frozen
Jan 29 15:47:39 Vault kernel: ata11.00: irq_stat 0x00400000, PHY RDY changed
Jan 29 15:47:39 Vault kernel: ata11: SError: { UnrecovData Persist PHYRdyChg 10B8B }
Jan 29 15:47:39 Vault kernel: ata11.00: failed command: READ FPDMA QUEUED
Jan 29 15:47:39 Vault kernel: ata11.00: cmd 60/00:10:e8:00:0f/02:00:3b:00:00/40 tag 2 ncq dma 262144 in
Jan 29 15:47:39 Vault kernel:         res 40/00:10:e8:00:0f/00:00:3b:00:00/40 Emask 0x10 (ATA bus error)
Jan 29 15:47:39 Vault kernel: ata11.00: status: { DRDY }
Jan 29 15:47:39 Vault kernel: ata11.00: failed command: READ FPDMA QUEUED
Jan 29 15:47:39 Vault kernel: ata11.00: cmd 60/00:18:e8:02:0f/02:00:3b:00:00/40 tag 3 ncq dma 262144 in
Jan 29 15:47:39 Vault kernel:         res 40/00:10:e8:00:0f/00:00:3b:00:00/40 Emask 0x10 (ATA bus error)
Jan 29 15:47:39 Vault kernel: ata11.00: status: { DRDY }
Jan 29 15:47:39 Vault kernel: ata11: hard resetting link
Jan 29 15:47:41 Vault kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 29 15:47:41 Vault kernel: ata2.00: configured for UDMA/33
Jan 29 15:47:41 Vault kernel: ata2: EH complete
Jan 29 15:47:42 Vault kernel: ata1.00: exception Emask 0x50 SAct 0xffffe00 SErr 0x30802 action 0xe frozen
Jan 29 15:47:42 Vault kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed
Jan 29 15:47:42 Vault kernel: ata1: SError: { RecovComm HostInt PHYRdyChg PHYInt }
Jan 29 15:47:42 Vault kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 29 15:47:42 Vault kernel: ata1.00: cmd 61/08:48:40:91:e0/00:00:e8:00:00/40 tag 9 ncq dma 4096 out
Jan 29 15:47:42 Vault kernel:         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error)
Jan 29 15:47:42 Vault kernel: ata1.00: status: { DRDY }
Jan 29 15:47:42 Vault kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 29 15:47:42 Vault kernel: ata1.00: cmd 61/08:50:48:91:e0/00:00:e8:00:00/40 tag 10 ncq dma 4096 out
Jan 29 15:47:42 Vault kernel:         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error)
Jan 29 15:47:42 Vault kernel: ata1.00: status: { DRDY }
Jan 29 15:47:42 Vault kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 29 15:47:42 Vault kernel: ata1.00: cmd 61/08:58:50:91:e0/00:00:e8:00:00/40 tag 11 ncq dma 4096 out
Jan 29 15:47:42 Vault kernel:         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error)
Jan 29 15:47:42 Vault kernel: ata1.00: status: { DRDY }
Jan 29 15:47:42 Vault kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jan 29 15:47:42 Vault kernel: ata1.00: cmd 61/20:60:00:0e:09/02:00:77:00:00/40 tag 12 ncq dma 278528 out
Jan 29 15:47:42 Vault kernel:         res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error)
Jan 29 15:47:42 Vault kernel: ata1.00: status: { DRDY }

Check all cables and/or try a different power supply.

I will, these disks are old, and tired, making a lot of noise, could it be the disks?

it let me transfer a couple gb then stopped, is that usual?

JorgeB · January 30, 2021

1 hour ago, stingray060 said:

could it be the disks?

It could, it could also be a power problem, and it's more likely that if it's affecting multiple disks.

1 hour ago, stingray060 said:

it let me transfer a couple gb then stopped, is that usual?

Don't try to transfer anything else until you fix those issues.

stingray060 · January 30, 2021

34 minutes ago, JorgeB said:

It could, it could also be a power problem, and it's more likely that if it's affecting multiple disks.

Don't try to transfer anything else until you fix those issues.

I’m using the silver stone cs380 I think it’s called, it had hot swappable bays at the front, my first 2 drives are my parity and data drive, both 4TB. They connect to The same back board as the drives that aren’t working, which is powered by a single molex, and have their own individual data cables.

stingray060 · January 30, 2021

Ok, Reconfigured the drive data connections through a LSI card i had lined up to go in, all brand new parts.

Mounted the drive no issues, when attempting to copy data from the drive to the array, this is the error I get.

JorgeB · January 30, 2021

Check filesystem on disk1.

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

stingray060 · January 30, 2021

My drives were formatted yesterday, and are almost empty, bar 20GB.

Could it be they weren't formatted correctly?

or loosing the drive yesterday, has caused another corruption?

stingray060 · January 30, 2021

1 hour ago, JorgeB said:

Check filesystem on disk1.

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

I had a new drive on order to come today, so i swapped my data drive with a brand new one, i think the old one may need a preclear?? as it was last used, and got corrupted, not sure how you fix a corruption.

I seem to be writing into the array fine, but parity is not happy. Any ideas?

trurl · January 30, 2021

31 minutes ago, stingray060 said:

how you fix a corruption.

That is exactly what the link you quoted is about.

32 minutes ago, stingray060 said:

parity is not happy.

Diagnostics?

stingray060 · January 30, 2021

Would i not need to use the preclear application to clear it properly? Would that be the cause of the issues then? the lack of me clearing it before trying to use it again..!?

vault-diagnostics-20210130-1456.zip

itimpi · January 30, 2021

33 minutes ago, stingray060 said:

Would i not need to use the preclear application to clear it properly? Would that be the cause of the issues then? the lack of me clearing it before trying to use it again..!?

PreClear has nothing to do with clearing corruption - it is primarily about testing whether a disk is faulty. Simply formatting a disk again will create a new empty (valid) file system. It if you Continue to get corruption either the disk is faulty or there is an external factor (e.g. cables, PSU, RAM) causing the corruption.

stingray060 · January 30, 2021

1 minute ago, itimpi said:

PreClear has nothing to do with clearing corruption - it is primarily about testing whether a disk is faulty. Simply formatting a disk again will create a new empty file system.

Gotcha, I re-formatted my drive yesterday after it broke, by changing the file type to btrfs then back to xfs.

Didn't do anything to the parity, but when attempted to move files, kicked up a fuss. Only thing I changed was swapped the drive for a brand new one. Which has fixed the issue, 400GB into transferring files now.

Edited January 30, 2021 by stingray060

trurl · January 30, 2021

Looks like you rebooted before getting those diagnostics so can't see what might have happened to disable parity. You will have to rebuild it of course.

Run an extended SMART test on parity.

stingray060 · January 30, 2021

1 minute ago, trurl said:

Looks like you rebooted before getting those diagnostics so can't see what might have happened to disable parity. You will have to rebuild it of course.

Run an extended SMART test on parity.

It says unable due to disk not spun up.

stingray060 · January 30, 2021

@HoopsterHow would you recommend starting and stopping a unraid server, from another unraid server on the same LAN?

stingray060 · January 30, 2021

tower-diagnostics-20111231-1654.zipIn another note, this is the diagnostics from my second server, which we cant get to connect to the lan, it is plugged in and showing transfer.

Hoopster · January 30, 2021

4 hours ago, stingray060 said:

@HoopsterHow would you recommend starting and stopping a unraid server, from another unraid server on the same LAN?

What's your use case for this? Knowing what you want to do and why may be helpful.

stingray060 · January 30, 2021

Just now, Hoopster said:

What's your use case for this? Knowing what you want to do and why may be helpful.

Like you have, to setup a daily or weekly backup, automated.

I have worked out the ssh stuff, just not sure what to do about the starting/stopping of the server.

I have been browsing for a IPMI board, which is tempting. Just fairly pricey.

Hoopster · January 30, 2021

1 minute ago, stingray060 said:

Like you have, to setup a daily or weekly backup, automated.

Before I had an IMPI capable motherboard in the backup server, I was using wake/sleep functions instead of IPMI power on/off.

Sleep and wake is highly dependent on the motherboard and NIC combo and some work much better than others. The one I had a few years ago happened to work very well, but it can be hit and miss. It is hard to know which motherboards/NICs will work well unless you get some advice from fellow unRAID users. There have been a few discussions about that in these forums.

Instead of the ipmitool commands in my script, I just had a wake command sent to the NIC to wake up the server for backup and, when finished, the script sent it a sleep command. This worked great until I decided I wanted IPMI power on/off instead.

For non-IPMI boards, some have made Raspberry Pi BMC/KVM setups to power their servers on/off. See this thread.

The low-tech way of doing it is to manually turn the server on before backup happens or to just leave it always on.

At the end of the day, IPMI is the easiest, most reliable way to do it, but, yes such boards are more expensive. My current MB cost me about $280 but can be found for $240 now here in the US. I don't know what availability or cost is for IPMI boards in your area.

stingray060 · January 30, 2021

5 minutes ago, Hoopster said:

Before I had an IMPI capable motherboard in the backup server, I was using wake/sleep functions instead of IPMI power on/off.

Sleep and wake is highly dependent on the motherboard and NIC combo and some work much better than others. The one I had a few years ago happened to work very well, but it can be hit and miss. It is hard to know which motherboards/NICs will work well unless you get some advice from fellow unRAID users. There have been a few discussions about that in these forums.

Instead of the ipmitool commands in my script, I just had a wake command sent to the NIC to wake up the server for backup and, when finished, the script sent it a sleep command. This worked great until I decided I wanted IPMI power on/off instead.

For non-IPMI boards, some have made Raspberry Pi BMC/KVM setups to power their servers on/off. See this thread.

The low-tech way of doing it is to manually turn the server on before backup happens or to just leave it always on.

At the end of the day, IPMI is the easiest, most reliable way to do it, but, yes such boards are more expensive. My current MB cost me about $280 but can be found for $240 now here in the US. I don't know what availability or cost is for IPMI boards in your area.

It seems availability for IPMI over here is limited, and i always get conscious when buying second hand, or refurbished parts. I have always used conventional computer parts, currently my main unraid uses a "gaming" asus motherboard and a AMD Ryzen CPU.

I have never considered the move to "server" components as, i dont really understand them, i have no idea if it is better or not. I suppose the clue is in the name, and they are quite literally designed for server use.

The motherboard i currently have sat here that i was attempting to launch unraid on, A) Refuses to launch unraid and B) Doesn't support Wake on Lan anyway. I think as a budget fix, my best option would be to buy a replacement Motherboard for this CPU. Or buy a CPU and Motherboard.

Just as a note, this servers use is to simply ONLY backup Data, no other functionality.

My Knowledge is limited, if you have any recommendations would be very useful.

Data Loss Problems

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation