My finger is pointed at the backup disk, because the machine did not have any problem before adding it.
> sd2 at scsibus2 targ 2 lun 0: <ATA, Samsung SSD 870, SVQ0> > naa.5002538f4362cc7c > sd2: 7630885MB, 512 bytes/sector, 15628053168 sectors, thin fsck on the disk was due, because of the crash. I run this weekly on all disks: dd if=/dev/rsd2c of=/dev/null bs=1m This is the last result for the backup: Checking the disk /sd2 ... 7630885+1 records in 7630885+1 records out 8001563222016 bytes transferred in 40227.230 secs (198910264 bytes/sec) The SMART test is good. In any case, I am through with SATA. It is time to move on. I am looking for a reliable IOC with 4x [M2|E1|E2]. On Friday, December 12th, 2025 at 11:25 AM, Dan <[email protected]> wrote: > Hello, > > I had the same problem with rdiff-backup some days ago. > I remain with my stalled backups a bit of time. > As you know in my case was an fs problem. > I suggest you to launch an fsck on the disk and see, nada else.. > > Dan > > ------ > Blog: http://bsd.gaoxio.com - Repo: https://code.5mode.com > > Please reply to the mailing-list, leveraging technical stuff. > > Dec 12, 2025 09:57:21 otto.cooper [email protected]: > > > It happened again. > > > > ipmi says voltages are ok. > > > > I suspect the problem is related to a new sata disk, because the server > > freezed during rsync backup. Hard to pin down the detail for me. > > > > -------- Original Message -------- > > On Thursday, 11/06/25 at 19:00 otto.cooper [email protected] wrote: > > A supermicro server froze last night. The console, via ipmi, did not return > > any information: there was a login prompt, no debug infos, and it was > > frozen. I had to reboot. I hate not knowing what went wrong, not even a log > > trace, nada.
