Dev/sdb3 contains a file system with errors

hydrurga · 01-10-2018, 08:28 PM

No worries. The 7.5GB is probably Swap, the other one perhaps a NTFS boot partition? It's 2.30am here and I'm not quite firing on all cylinders.

Anyway, just go for it and boot off the USB HDD.

Coop_012 · 01-10-2018, 09:02 PM

It works!!!! Thanks hydurga!

hydrurga · 01-10-2018, 09:21 PM

Excellent.

If you're still there, could you possibly (when booted up off the USB HDD), paste the output from the following two commands here just so I can figure out those 1st two partitions:

Code:

lsblk

sudo parted -l

Coop_012 · 01-10-2018, 09:23 PM

Could I tomorrow? I’m sorry

hydrurga · 01-10-2018, 09:31 PM

Quote:

Originally Posted by Coop_012

Could I tomorrow? I’m sorry

Of course.

Coop_012 · 01-11-2018, 09:32 AM

Okay I went to start it back up today.... and the same problem occurred, but it started up yesterday. Should I try the umount and fsck again once I get home?

hydrurga · 01-11-2018, 11:03 AM

Quote:

Originally Posted by Coop_012

Okay I went to start it back up today.... and the same problem occurred, but it started up yesterday. Should I try the umount and fsck again once I get home?

It wouldn't be good if you had to do that every time though. Have you used that particular USB HDD without problems in the past? Do you have another USB cable you could swap for the existing one? Could you try plugging it into a different USB port?

I would suggest you do indeed do the fsck again, and then try the latter two attempted fixes, one at a time, making sure first that the disk has been fsked and then, after each fix attempt, booting up again several times to see if it has made a difference.

When you are finished with the USB HDD after booting up from it, are you properly closing Mint and switching the computer off before detaching the USB HDD?

Coop_012 · 01-11-2018, 12:07 PM

I will try that, in the meantime, it has corrupted any time I’ve tried the shutdown command in the terminal, instead of using the the GUI

hydrurga · 01-11-2018, 12:09 PM

Which shutdown command are you using?

Coop_012 · 01-11-2018, 12:15 PM

Code:

shutdown

it then says it will shutdown in the next minute, but in the format of 12:13:42 or whatever. I ran this command as well like you asked

Code:

lsblk

sudo parted -l

The results were

Code:

Model: ATA TOSHIBA MK3265GS (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size    Type      File system     Flags
 1      1049kB  317GB  317GB   primary   ext4            boot
 2      317GB   320GB  3075MB  extended
 5      317GB   320GB  3075MB  logical   linux-swap(v1)


Model: WD My Passport 0820 (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                  Flags
 1      20.5kB  210MB   210MB   fat32           EFI System Partition  boot, esp
 3      211MB   300GB   300GB   ext4
 2      992GB   1000GB  7999MB  linux-swap(v1)


Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
has been opened read-only.
Error: /dev/sr0: unrecognised disk label
Model: TEAC DV-W28S-VTF (scsi)                                            
Disk /dev/sr0: 2048B
Sector size (logical/physical): 2048B/2048B
Partition Table: unknown
Disk Flags:

hydrurga · 01-11-2018, 12:45 PM

Thanks for that info. So that explains the partitions - the first is the EFI system partition, the second the Swap. All good.

Wouldn't you normally need to be root to shutdown (i.e. prefix the shutdown command with a sudo?). When you're shutting down in this way, have you completely exited X (the GUI) or do you still have the GUI running?

Coop_012 · 01-11-2018, 01:01 PM

i did not know i could leave the gui so i still have it running, it doesnt require root access to shutdown yet i cannot do it over ssh (if that helps) btw im typing this on my system!

hydrurga · 01-11-2018, 01:30 PM

Quote:

Originally Posted by Coop_012

i did not know i could leave the gui so i still have it running, it doesnt require root access to shutdown yet i cannot do it over ssh (if that helps) btw im typing this on my system!

I'm no expert, but if you have a GUI still running then I think it would be best (more orderly for the system) to shut down the system through that GUI, not through the command line.

You should test the fault by doing so and rebooting several times to see if the problem reoccurs.

Coop_012 · 01-11-2018, 01:33 PM

Thank you so much! You really stuck it out with me and replied fast! thanks for helping this newbie out

hydrurga · 01-11-2018, 01:39 PM

Quote:

Originally Posted by Coop_012

Thank you so much! You really stuck it out with me and replied fast! thanks for helping this newbie out

Let us know how it goes. It would be nice to determine why your file system is not unmounting cleanly, if that's what the problem is.