Hello,
I changed my SSD from a 128GB M2 to a 256GB SSD to have more space for camera video files. I plugged in Live Linux and used Etcher to clone the drive. It worked dirctly on first try and I was able to start up HA again. But now I see a lot of strange messages in Host logs:
Jul 09 14:11:25 homeassistant kernel: audit: type=1334 audit(1688911885.649:289): prog-id=80 op=UNLOAD
Jul 09 14:11:25 homeassistant kernel: audit: type=1334 audit(1688911885.649:290): prog-id=79 op=UNLOAD
Jul 09 14:11:25 homeassistant kernel: audit: type=1334 audit(1688911885.649:291): prog-id=78 op=UNLOAD
Jul 09 14:13:57 homeassistant kernel: TCP: request_sock_TCP: Possible SYN flooding on port 8123. Sending cookies. Check SNMP counters.
Jul 09 14:14:10 homeassistant kernel: cifs_open_info_to_fattr: 8 callbacks suppressed
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:10 homeassistant kernel: CIFS: VFS: bogus file nlink value 0
Jul 09 14:14:42 homeassistant kernel: cifs_open_info_to_fattr: 8 callbacks suppressed
System is booting up fine and restarting without porblems, but I wonder where it comes from and how to fix it? I think it might be related of unused disk space, but as much as I was able to google, HA should automaticly expend disk space to ~256GB.
Greetings Moritz