My Octopi install (Pi3 B+) worked really well, until this morning, don't know why, I cant access it, web, ssh, ping, nothing work.
I tried to connect it on ethernet, same problem.
I can access and copyt my files, if I connect my sd card to my pc, But I cant find where my gcodes (not really important), plugins, and setup files (more important, to me)
So, Is there a way to fix my install, without erasing my previous setup and plugin?
Or a way to find a list of the plugin I installed, so I could install again to fresh install?
Copy the whole /home/pi/.octoprint folder. This will contain your octoprint configuration, uploaded gcode files, timelapses, plugin settings, though not the plugins themselves. It is better to download them again once you are back up and running.
When I plug my sd card to my pc, I only have access to the "boot" partition, is there a way to read the other one, windows can't natively, and suggest me to format.
You could try setting up an OctoPi installation on a new sd card, and use an USB cardreader to mount the old sd card to read the files you need from it.
I had problems with Ext2Fsd but Linux Reader worked flawlessly.
You access the RPi with PuTTY (SSH), login as the user pi.
You then plug your USB SD card reader into your RPi and mount the file system. On my system, the USB SD card reader is /dev/sda with two partitions, /dev/sda1 (/boot) and /dev/sda2 (/) so I type:
sudo mkdir /mnt/sda2
sudo mount /dev/sda2 /mnt/sda2
pi@octopi:~ $ sudo fdisk -l /dev/sda
Disk /dev/sda: 14.9 GiB, 15980298240 bytes, 31211520 sectors
Disk model: Storage Device
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6c586e13
Device Boot Start End Sectors Size Id Type
/dev/sda1 8192 532479 524288 256M c W95 FAT32 (LBA)
/dev/sda2 532480 31211519 30679040 14.6G 83 Linux
pi@octopi:~ $ cd /dev/sda2
-bash: cd: /dev/sda2: Not a directory
The output of fdisk looks normal. There's one more thing we can try...
sudo fsck /dev/sda2
Without a "suspect corruption" SD card, I don't know what the output should look like. If it's too big, pipe it to a file and post that (sudo fsck /dev/sda2 >fsck.log).
Another useful command for saving the output of linux commands is screen -L. This will create a log file (screenlog.0) in the current directory that contains the input and output of multiple commands until you type exit.
pi@octopi:~ $ sudo fsck /dev/sda2
[sudo] password for pi:
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
rootfs: recovering journal
fsck.ext4: unable to set superblock flags on rootfs
rootfs: ********** WARNING: Filesystem still has errors **********