You run e2fsck on the whole drive not on the partition where the filesystem lies.
Also you should note that you should use the same blocksize with badblock than the fs uses.
So to achieve what you want in a much simpler way, you can simply run:
sudo fsck -vck /dev/sdbx
This will run a filesystem check but also check for badblocks and add them to the ...
ext2, ext3, ext4 are all supported.
However, was the drive taken out of the NAS that is part of a RAID? For instance, is it part of a striped RAID (0) opposed to a RAID 1 would be a complete mirror? If it is part of a striped RAID without the parity, it may not contain data that ...
On the other hand, the windows boot normally and I can even access data on my linux partition /dev/sda6 using a third party program DiskInternals.
This is the root of your Problem. Since ubuntu bionic e2fsprogs
creates filesystem with new feature. Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent 64bit flex_bg ...
If the BIOS recognizes the SSD at boot then it will lock it. The information you posted shows the SSD is locked.
I would suggest the following:
Turn the laptop off.
Unplug the SSD.
Turn the laptop on.
Wait for system to boot to desktop.
Plug back the SSD
Try formatting it.
Best of luck.
It seems that your disk is not partitioned.
If your disk contains valuable data, first make a backup image of it using dd (-> man). Your command would be something like dd if=/dev/sdb of=/image/path bs=1M
Ensure that the media where you write the image has enough space (500GB apparently in your case).
Then, try opening it with gparted (graphical), parted (...
Lets first check your file system for errors.
For 18.04 or newer...
boot to a Ubuntu Live DVD/USB
open a terminal window
type sudo fsck -f /dev/sda6
repeat the fsck command if there were errors
Well, this was one very strange HDD problem.
Bottom line... From Windows, we deleted the Ubuntu sda6 partition, removed the Ubuntu boot ...
For newbies like me...
I want to add this
When loading the system. You can see the logo KUBUNTU.
You can press the up arrow once and then you see what the system is actually doing at the moment.
There was a line in RED
Time Timed out waiting for device /dev/sdc1
There were another in Yellow
DEPEND Dependency failed for /HDD
DEPEND Dependency failed ...
mount -o remount,rw /
If that doesn't work, touch /forcefsck and reboot. (If you didn't change stuff in your /etc/fstab this will automatically check all your filesystems automatically upon rebooting.)
It's backup time!
If you don't want to lose any of your data, stop trying to boot or change Windows and boot an Ubuntu live USB stick in Try Ubuntu mode and copy all of the data onto an external HDD. (you'll find all of your Windows disks can be mounted from said USB stick) and then:
Install Windows again (off-topic here, but on-topic there )
Restore your ...
When you are absolutely, positively, 101% sure there is nothing you want to save on the HDD, you can obliterate everything on it.
But you have to be REALLY sure, because, once it's gone, it's gone.
First, load Gparted and look at the drives. There's a spin box at upper right which will show sda or sdb
This article shows you tools you can use to analyze ...
Desktop icons work differently in 19.04, due to changes in GNOME Shell. It's still a work-in-progress.
Most individual icons no longer work. Folders do. Create a desktop folder called Work in Progress... or pseudo Desktop... and create/move your symbolic link INSIDE the new folder. It'll work there.
In UBUNTU the ssd will have nvme0n[n1]p[n2] as device name and the hdd will have sd[c1][n2] where [n1] is the hard disk number, [n2] is the partition number, [c1] is a letter indicating the hard disk number. Mind that this is related to a HP Omen. Other systems might have an older ssd version: nvme is a M.2 SSD. That is a newer type of SSD.
Info from my hp ...
You can't directly write files to /dev/sda2, it's not really a directory in the same sense as you'd think of a directory in Windows, it's more like a "special file."
You need to first mount it, and then use it as a directory.
You'll need to create a mount point, say
sudo mkdir /mnt/sda2
and then mount the partition,
sudo mount /dev/sda2 /mnt/sda2
This post may be of help to you. I would recommend keeping your /home folder on the SSD also and use the HDD for extra storage, The reason I say that is a lot of programs use the /home folder for hidden config files and if they have to get it from the HDD you'll notice a slowdown in those programs. But the choice is yours.
This has worked for me all days:
e2fsck -ff /dev/vg0/test-disk
Resize filesystem to 4G:
resize2fs /dev/vg0/test-disk 4G
Check disk again just for the sake of it (first command).
Remember to backup important files.
I think 40gb is enough for root file system. 1tb hard drive was partitioned well enough but not mounted correctly. In current scheme your personal files(aside of system files) was reside on the root partition. /dev/sda5 that mounted on /media/neil/HOME should be mounted on /home. I assume the username you're using was Neil. You should make folder on /media/...
What's wrong with 'du -sh /*' ? It will show you what root folder takes up the space, then you can go from there.
Though I agree most probably your home folder is on the wrong partition.. you could check with 'echo ~neil'
/dev/sda7 38G 35G 989M 98% /
/dev/sda4 487M 0 487M 0% /media/neil/HP_TOOLS
/dev/sda5 868G 113M 823G 1% /media/neil/HOME
/dev/sda1 200M 30M 170M 15% /media/neil/BOOT
All four volumes are on that same 1 terabyte hard drive named /dev/sda. You have a 38G root partition, but your /media/neil/HOME is 868G. ...
Create a mountpoint directory for your hdd:
sudo mkdir /media/hdd2
Run sudo blkid, get the UUID of the /dev/sdZX partition and add it to /etc/fstab (make backup of fstab befor modifying it):
Add a line to /etc/fstab
UUID="XXXXXXXXXXXX" /media/hdd2 ntfs-3g permissions,defaults 0 2
Mount it to test:
If you get an error like Failed to mount '/...
You have a quite small root partition for system files and applications, most of the disk space is in your home partition for user data.
You will either need to clean up the root partition mainly by uninstalling applications, or also removing log and cache files and such things, or you have to modify your partition layout and shrink your home and grow the ...
Errors often give valuable information and here is no exception. It helps to break it down in chunks:
Error mounting system-managed device /dev/sdb3/
Your drive located at /dev/sdb3/ cannot be mounted due to an error.
NTFS is either inconsistent, or there is a hardware fault...
There is a problem with NTFS (the file system on the drive). It may have ...
Windows fastboot is preventing you from mounting the partition because windows is in hybrid hibernate/suspend. run "mount -o ro /dev/sdb3 /path/to/mount/to" will mount an unclean ntfs file system on /path/to/mount/to if you just want to read files off the partition. if you want to read /write that partition you must boot into windows then hold shift when ...
Generally fixing a problem in a specific operating system needs to be fixed from tools that come from that operating system. Mind though that the system claims it is NOT a NTFS volume so NTFS tools will not work.
Mind the following questions:
Could it be another filesystem?
Are you sure you have the ntfs-tools istalled? Otherwise NTFS is an unknown ...
The problem is with the BitLocker being enabled for the disk in discussion. Disable the BitLocker encryption by going to:
Control Panel > System & Security > BitLocker Drive Encryption > Select - Turn Off BitLocker
In Windows, open a cmd (command) terminal with admin privs. With the drive(s) connected, type:
chkdsk /f e:
chkdsk /f f:
chkdsk /f g:
chkdsk /f H:
When using these drive(s) on Ubuntu, make sure to properly unmount the drive(s) before disconnecting them.
Go from a separate /home partition in the HDD to the default configuration where /home is a folder in /, which is in the SSD
We will do this from a Live USB running Ubuntu 18.04 so that we can work with the /home partition and mount it as /internal_home.
Step 1: Boot from a Live USB Ubuntu
Select the Try Ubuntu without Installing option as we want to run ...
You can use gdisk for partitions bigger than 2TB.
# gdisk /dev/xvdk
GPT fdisk (gdisk) version 0.8.6
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): n
Partition number (...
You need to delete Windows boot partition (EFS) to install Ubuntu, I faced the same issue during installation in Acer predator 500. If deleting only EFS (use gparted preinstalled in ubuntu Live boot partions are marked as esp under flags) does not work then you need to delete windows partition + Microsoft reserved partition + EFS this would definitely works.