(SOLVED) Samba and hostname broken suddenly RPI2

Dear All,

I don’t know what is happening but I was doing some heavy back-up on the network when suddenly I lost the samba connection and RPI2 is looping with the sad face trying to load Kodi. The version of OSMC should be the one before the last-second updating.

There are several services broken without any apparently reason and when I try to restart, or reload, them, they fail to reload properly.
I am a bit in panic because I don’t have absolutely idea of the causes and I didn’t figure out any solutions.

systemctl --failed
  UNIT                        LOAD   ACTIVE SUB    DESCRIPTION
● samba.service               loaded failed failed Samba Server
● smbd.service                loaded failed failed LSB: start Samba SMB/CIFS dae
● systemd-hostnamed.service   loaded failed failed Hostname Service
● systemd-update-utmp.service loaded failed failed Update UTMP about System Boot

The only thing I would do is scream WTF!!!

Maybe is something easy but right know I am pretty confused, thanks!

We have no idea what that means…

To get a better understanding of the problem you are experiencing we need more information, including logs from you. Our wiki contains detailed steps for providing the relevant info we need to help you.

You’re right, but I can’t get the OSMC gui, I can handle the OSMC only through ssh (fortunately) this is the version of the kernel in use, maybe that can help:

Linux osmc 4.4.27-5-osmc

There are instructions in the link for for obtaining logs by ssh…

provide the URL of grab-logs -A

Hi Guys, thanks to all.

I got a bit of blood cold and I fixed samba reconfiguring the packages samba and samba-common-bin, however the GUI won’t start. I’am trying to do a couple of test to see what happens.

Anyway thanks, thanks and thanks to all, the only the fact somebody replied to me helped a lot to recover the control! :smiley:

Thanks for trick, please find below the URL

http://paste.osmc.io/uwesasotip

I was unable to get the GUI, I haven’t figure out the issue, I am pretty sure it is something related with the samba transfer I saw blinking the thunder a lot of time during the transfer (+500G).

Thanks!

That means your powersupply/cable is not up to the job and you most likely corrupted your install.
First get a proper powersupply and than you might need to reinstall

It looks like you manually moved your root FS

# /dev/mmcblk0p2 / ext4 defaults,noatime 0 0
UUID=e16fe3fa-682c-43a9-b16c-0101e1942a87 /mnt/oldroot ext4 noauto,ro,noatime 0 0

## SISTEMA MONTATO SUL DISCO DURO
UUID=dff32edf-d65d-442c-bc07-3896f04aa6c4 / ext4 defaults,noatime 0 1
# /dev/sda5 / ext4 defaults,noatime 0 1

Did you move it to a USB disk?
I think you really need to ensure proper power supply and a working disk.

Jan 02 20:08:32 osmc systemd[1]: Mounting /boot…
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor]
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00
Jan 02 20:08:32 osmc systemd[1]: Mounted /boot.
Jan 02 20:08:32 osmc kernel: FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor]
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor]
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor]
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
Jan 02 20:08:32 osmc kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00

Yep, I have the root and the home located in an external hd with its own power supply. Unfortunately It seems I got a corrupted super block and now I must fix it manually, anyway I had better to buy an official power supply the one I have (bought within a bundle) never felt it working well.

Hi All, I solved everything.

Actually I didn’t understand what happened. Basically I believe because the undervoltage many giga of files were somehow copied inside the /media folder so suddenly I had all the root partition completely busy; this had generated all this issues: samba broken, services broken, and GUI broken.

After that I checked all the disks looking for errors and I found clean and working partitions without filesystems corruptions. I lost just few configurations on the Kodi gui, a bit annoying but easy to restore.

Anyway this experience thought the ethernet of the PI2 is not reliable for heavy files transfer, next time I will connect the OSMC hard drive to my computer when I need to copy several giga of folders between different drives.

Thanks to all for the assistance!