خرید بک لینک

As of my most recent updates, one of my 7 exteal drives is now mounting as a Partition only, and not as a full drive. Maybe I'm mis-explaining the issue, but this is leading to the drive not getting caught by FSTAB, and I can't find a way to access the drive.

/dev/sdc1 is the issue:

Code:

andre@NAS:~$ sudo blkid
[sudo] password for andre: 
/dev/sda1: UUID="51AB-2663" TYPE="vfat" PARTUUID="c712dc64-a7d7-4ad3-a5dc-e07490a705d3"
/dev/sda2: UUID="e1abd730-7d20-4120-90d2-d71282a96d87" TYPE="ext4" PARTUUID="50cfa454-3cf7-4182-a210-e2fe1882ba4f"
/dev/sda3: UUID="412337ba-019b-45a7-8376-2a9236201a2e" TYPE="swap" PARTUUID="6385f4ee-8cd8-4540-9fb7-62587471f4d4"
/dev/sdb1: LABEL="4TB_2" UUID="affca0f6-7ae8-45f5-9e59-92170c3c437a" TYPE="ext4" PARTUUID="7ed95559-df56-4ae3-84b3-ffb9f98a4db0"
/dev/sdc1: PARTUUID="d2a98f7e-1857-474b-9973-b2676d2302f0"
/dev/sdd1: LABEL="2TB_2" UUID="deb41754-7157-42f0-8129-d1545f10ace4" TYPE="ext4" PARTUUID="7acc80f1-01"
/dev/sde1: LABEL="5TB_1" UUID="c9fd552c-921c-4ddb-bb46-fe557943d311" TYPE="ext4" PARTUUID="3bed9e0c-b45e-4518-9af5-eadcd3a97cc1"
/dev/sdf1: LABEL="4TB_1" UUID="f90279d3-7127-4fdb-845c-7c7f60fd6eec" TYPE="ext4" PARTUUID="4a9a71ca-7c1e-42a0-865e-199de4f8b47c"
/dev/sdg1: LABEL="5TB_2" UUID="2b1fcea7-8183-43d4-8a1a-43c54d9e8e5d" TYPE="ext4"
/dev/sdh1: LABEL="2TB" UUID="f238352a-805e-40e8-a676-c62f0b6b0acb" TYPE="ext4" PARTUUID="5b349937-b657-4c5a-a4e1-1f8eaad3382c"
And here is my FSTAB file (the drive should be 4TB_3:

Code:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=e1abd730-7d20-4120-90d2-d71282a96d87 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=51AB-2663  /boot/efi       vfat    defaults        0       1
# swap was on /dev/sda3 during installation
UUID=412337ba-019b-45a7-8376-2a9236201a2e none            swap    sw              0       0
#
#
#
#### MOUNT POINTS ####
# 2TB_1
UUID=f238352a-805e-40e8-a676-c62f0b6b0acb  /mnt/2TB_1   ext4 defaults,nobootwait,noatime 0 2
# 2TB_2
UUID=deb41754-7157-42f0-8129-d1545f10ace4  /mnt/2TB_2   ext4 defaults,nobootwait,noatime 0 2
# 4TB_1
UUID=f90279d3-7127-4fdb-845c-7c7f60fd6eec  /mnt/4TB_1   ext4 defaults,nobootwait,noatime 0 2
# 4TB_2
UUID=affca0f6-7ae8-45f5-9e59-92170c3c437a  /mnt/4TB_2   ext4 defaults,nobootwait,noatime 0 2
# 4TB_3
UUID=3b7c225a-2602-4224-8a80-dc59d13cc1a4  /mnt/4TB_3   ext4 defaults,nobootwait,noatime 0 2
# 5TB_1
UUID=c9fd552c-921c-4ddb-bb46-fe557943d311  /mnt/5TB_1   ext4 defaults,nobootwait,noatime 0 2
# 5TB_2
UUID=2b1fcea7-8183-43d4-8a1a-43c54d9e8e5d  /mnt/5TB_2   ext4 defaults,nobootwait,noatime 0 2
#

I do recall lubuntu performing a filesystem check on a drive during a recent reboot, but it didn't throw any errors at me.

I'm having other issues with the system booting (I usually need to boot the system from GRUB using an UPSTART keel - the splash screen always seems to freeze). Also, I have way more keels installed than I think I'm supposed to - I believe the system is only suppsed to hold on to a few, and I have 6 or 7 keels still installed.

My top conce is getting the drive working again, but just trying to provide information.

برچسب: نویسنده: استخدام کار تاريخ: شنبه 21 فروردين 1395 ساعت: 10:29

صفحه بندی