not sure what you mean by repaired it. if your system is booting, the the outcome of running the boot record modification tool fdisk has not contributed to any of the issues youre seeing.
then my bet would be that you edited /etc/fstab is a slightly wrong way with regards to the extra storage disk you are auto-mounting. Because the other option is you edited the rootfs mountpoint wrong, or the proc, boot mountpoints wrong.
If it was an edit corrupting rootfs, boot partition mountpoints, the system wont start. Whereas if you edited the extra storage mountpoint wrong in fstab, then at next restart your system will hang before starting up for up to 5 minutes looking for ways to mount the drive over the network.
i dont see any issues in that guide besides the static /dev/sda1 /mnt/storagenode ext4 defaults 0 2 example theyre giving. the drive letter in your case might very well be different. e.g. /dev/sda2. furthermore, it makes more sense to mount drives with their label, which you can obtain by doing ls -la /dev/disk/by-uuid/ and then looking up the syntax in /etc/fstab of how the rootfs is mounted with a uuid label
Thanks for the help. I noticed that my external drive is “/dev/sda1 256 976746239 976745984 3,7T 7 HPFS/NTFS/exFAT” and i used “/dev/sda1 /mnt/storagenode ext4 defaults 0 2” from the guide. So maybe it works if i change ext to ntfs?
yeah, so you have an ntfs partition on that drive. i would like to say it is highly unrecommended to run ntfs. the forum is littered with issues around ntfs drives. otherwise youre correct. the quick and dirty way of mounting it in fstab would be /dev/sda1 /mnt/XXX ntfs defaults 0 0
notice the 0 0 at the end instead of the 0 2. and again, this is a quick and dirty way. the ntfs filesystem is highly undesirable for high throughput disk ops under linux. a better way to mount it would be to specify a bit more options that make it play nicer with linux
UUID=0AC4D607C4D5F543 /mnt/volume ntfs-3g async,big_writes,noatime,nodiratime,nofail,uid=1000 [OPTIONAL U NEED TO LOOKUP USER IDs],gid=1000 [OPTIONAL U NEED TO LOOKUP GROUP IDs],umask=007 0 0
most importantly, u really need to add the async,big_writes,noatime,nodiratime options to the mountpoint