[SOLVED] superblock something Slack is not letting me boot into it, but peppermint got it back.

BW-userx · 05-08-2018, 05:59 PM

something is wrong with my sdd hdd. Has to be. I used supergrub2 to get into peppermint 8 because its grub screwed up and slack is giving me issues with not knowing what format I am using, and asking for a password to get in as root, and I did't give it one even how that I think about it. it never asked me for one during install. hum.

anyways I am downloading another iso of slack so I can burn a fresh ios to a stick see if that works, but this is what it is saying, sorry it has to be an image.

anyone understand this issue, and how to fix it, so I can get back into slack?

in peppermint slack install on dev/sda5 and sda7

Code:

userx@userx-HP-EliteBook-8460p ~/Downloads $ sudo badblocks -v /dev/sda5 > badsectors
[sudo] password for userx: 
Checking blocks 0 to 20507647
Checking for bad blocks (read-only test): done                                                 
Pass completed, 0 bad blocks found. (0/0/0 errors)

Didier Spaier · 05-09-2018, 03:52 AM

We need more information to investigate.

Please start the Slackware installer, and as soon as logged in as root type the following command and provide its output:

Code:

lsblk -o vendor,model,name,size,fstype

You could redirect the output to a file in another mounted USB stick to ease copy/pasting it later.

Then, please tell us what the listed partitions are used for.

Be aware that all usual tools like e2fsck are available from the installer, so do check the partitions from there.

BW-userx · 05-09-2018, 09:12 AM

I'm not completely sure what happened, only I was only relaying the information the system was telling me. I got a different distro installed onto a separated partition I put back for just that, after just having gotten rid of it a short while ago. This error was shown as a result of Slackware install that to me was not going as it should. that error about the superblock is what I thought was causing it. I checked the partitions after getting the other distro installed, yet even before that Windows was booting without issues with the help of supergrub2 to cause it to boot.

this is an sdd, not that old mind you and others. so that does not fix either. I got everything, the two OS'es p/Windows installed, again, back to three OSes again. this all happened due to some stupid little quirk that I still have no idea why that cropped up. That lead me to just going to recompile and reinstall WMaker updated version, then back to the version that comes with Slack, then back to the updated version again, then back to the installed version that all did not work, so I went to reinstall OS, which happened to lead me to this.

I could not get into the system during the install to use e2fsck, it was asking for a password, that I did not give it, so I thought Slack might have some of them basic default passwords for root as most distros are doing, (the live usb Stick to installs). could not find anything on that, that's when I went and just backed up my home and wiped the Linux partitions, re-partitioned, giving myself back the partition for another OS, then went that route to get slack back on.

only this time skipping LILO install finishing the install of Slackware, then using the grub from the other disto to pick up Slackware instead.

I have not seen anything strange behavior yet, and the checks shows no errors on any of the partitions. so I am not too sure if it is even worth the investigation or not. it may have been due something in conjunction to a lilo fail install thing.

I'm marking this solved to free up time for other things to ones in here.