Newbie: Dual booting with WIN 10, but don't see Windows drives

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

Hi, I'm new to LInux, though I used it briefly many years ago in a dual boot for a while.

I have set up Mint 18.1 KDE to dual boot with Windows 10 and they are booting fine with GRUB, but several things seem to not be there from the old days and I can't seem to find an answer to the following question:

I have 5 drives on this system, the dual boot is from a single SSD with partitions so that Windows and Mint can coexist/dual boot. In Dophin, Mint shows the SSD/boot up drive just fine, but doesn't show my other drives, which are 4 hard drives and I cannot seem to find a way to perma mount them or access them.

I also cannot find an option to run screen savers.

I don't find answers to these questions even after trying different terms for search.

Can someone help me. Are there GUI solutions or are there Terminal done solutions?
I'm just a student, your guidance is appreciated.
odtech
Level 3
Level 3
Posts: 104
Joined: Sat Jan 21, 2017 9:25 am

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by odtech »

wutsinterweb wrote:Hi, I'm new to LInux, though I used it briefly many years ago in a dual boot for a while.

I have set up Mint 18.1 KDE to dual boot with Windows 10 and they are booting fine with GRUB, but several things seem to not be there from the old days and I can't seem to find an answer to the following question:

I have 5 drives on this system, the dual boot is from a single SSD with partitions so that Windows and Mint can coexist/dual boot. In Dophin, Mint shows the SSD/boot up drive just fine, but doesn't show my other drives, which are 4 hard drives and I cannot seem to find a way to perma mount them or access them.

I also cannot find an option to run screen savers.

I don't find answers to these questions even after trying different terms for search.

Can someone help me. Are there GUI solutions or are there Terminal done solutions?
Hello.

I'm no expect in how windows 10 handles hard drives/filesystems but by default even doing a clean shutdown LInux mint reports that the ntfs disk is in an unsafe state when trying to mount it. I'm assuming though it has something to do with hibernation or hybrid sleep, try turning those off.
But before messing around with windows let's first see if Mint is at all aware of your hard drives.

Open the terminal and simply type.

Code: Select all

sudo fdisk -l 
The output is a bit messy but you can usualy identify your drives by the size and partition layout.
Each drive is identified by /dev/sdn, n being replaced by a unique letter from a to z for each physical disk.
Partitions are identified by /dev/sdnx, x being replaced by a unique number for each partition from number 1 and up to however many partitions the disk has.

If you feel more comfortable you can use a GUI tool. I prefer gparted but it is not installed by default. You can find it in the package manager or just directly install it from terminal

Code: Select all

sudo apt-get update && sudo apt-get install gparted
Once installed you can find it in the menu as Gparted.
It will prompt for your user password when opening it.
Here you can check which drives Mint is aware of by checking the dropdown menu in the top right corner.
Assuming you see the disk you want mounted simply select it then right click on a partition in the list and select mount.
If you get an error message then post it here and we can take it further.

Here is something to consider though. It used to be very hit and miss but with more recent hardware is has gained alot of traction and there are more success stories than failures.
viewtopic.php?f=231&t=212692
My desk has 2 seats with 2 sets of input devices and 3 monitors and only 1 physical pc. Dual monitor setup for Mint and the third monitor is for my gaming virtual machine. Any data that needs to be shared is done by networking. You need 2 gpu's in the physcial machine to make it work though, 1 for the host and 1 for the guest. If you run intel you can use the intel onboard gpu for the host and a amd or nvidia gpu for the guest.

Some other folks has a similar setup to mine but they only have one set of input devices with 2 or more screens. A program called synergy is used to seamlessly move the mouse between windows and Mint as if you were working on a normal multi display pc. Networking is again used to share data between OS's.
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

I did that first one and it sees the drives just fine, last night.

I just did gparted and it sees the drives but mount is greyed out

Also, now in dolphin, devices is gone in the left side.
I'm just a student, your guidance is appreciated.
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

Ok, for those drives, it shows zfs for the file system, they are 3 TB drives with a gpt partition table. Does that affect this?
I'm just a student, your guidance is appreciated.
odtech
Level 3
Level 3
Posts: 104
Joined: Sat Jan 21, 2017 9:25 am

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by odtech »

wutsinterweb wrote:Ok, for those drives, it shows zfs for the file system, they are 3 TB drives with a gpt partition table. Does that affect this?
That sounds a bit odd, as far as i know zfs filesystem is not available to windows.
Are some of those windows disks of yours part of raid array perhaps?
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

No, no RAID
I'm just a student, your guidance is appreciated.
odtech
Level 3
Level 3
Posts: 104
Joined: Sat Jan 21, 2017 9:25 am

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by odtech »

wutsinterweb wrote:No, no RAID
Can you do fdisk -l again and post the full result here?
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

Will do that, just a moment!
I'm just a student, your guidance is appreciated.
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

signmeuptoo@signmeuptoo-All-SeriesMint ~ $ sudo fdisk -l [sudo] password for signmeuptoo:
- Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes - Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes - Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
- Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes

- Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xb8b896aa Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1026047 1024000 500M 7 HPFS/NTFS/exFAT
/dev/sda2 1026048 691019775 689993728 329G 7 HPFS/NTFS/exFAT
/dev/sda3 691019776 691941375 921600 450M 27 Hidden NTFS WinRE
/dev/sda4 691943422 937701375 245757954 117.2G 5 Extended
/dev/sda5 925149184 937701375 12552192 6G 82 Linux swap / Solaris
/dev/sda6 691943424 925149183 233205760 111.2G 83 Linux Partition table entries are not in disk order.

- Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xa45c0796 Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 206847 204800 100M 27 Hidden NTFS WinRE
/dev/sdb2 206848 1338200063 1337993216 638G 7 HPFS/NTFS/exFAT
/dev/sdb3 1338200064 1952602111 614402048 293G f W95 Ext'd (LBA)
/dev/sdb4 1952602112 1953521663 919552 449M 27 Hidden NTFS WinRE
/dev/sdb5 1338202112 1952602111 614400000 293G 7 HPFS/NTFS/exFAT Partition table entries are not in disk order.

- Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8BD48D6-A536-B541-AC3D-22B66D4F4146 Device Start End Sectors Size Type
/dev/sdc1 2048 5860532223 5860530176 2.7T Microsoft basic data

- Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 4D13AF4B-FB62-B74B-A3FE-E4AE5BF3A3AB Device Start End Sectors Size Type
/dev/sdd1 2048 5860532223 5860530176 2.7T Microsoft basic data

- Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 58A69147-6ECC-E14F-983A-E554BD67200D Device Start End Sectors Size Type
/dev/sde1 2048 5860532223 5860530176 2.7T Microsoft basic data signmeuptoo@signmeuptoo-All-SeriesMint ~ $
Last edited by Pierre on Tue Feb 28, 2017 10:34 pm, edited 1 time in total.
Reason: Heavily edited post, for easeir reading.
I'm just a student, your guidance is appreciated.
odtech
Level 3
Level 3
Posts: 104
Joined: Sat Jan 21, 2017 9:25 am

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by odtech »

wutsinterweb wrote:signmeuptoo@signmeuptoo-All-SeriesMint ~ $ sudo fdisk -l [sudo] password for signmeuptoo: Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xb8b896aa Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 1026047 1024000 500M 7 HPFS/NTFS/exFAT /dev/sda2 1026048 691019775 689993728 329G 7 HPFS/NTFS/exFAT /dev/sda3 691019776 691941375 921600 450M 27 Hidden NTFS WinRE /dev/sda4 691943422 937701375 245757954 117.2G 5 Extended /dev/sda5 925149184 937701375 12552192 6G 82 Linux swap / Solaris /dev/sda6 691943424 925149183 233205760 111.2G 83 Linux Partition table entries are not in disk order. Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xa45c0796 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 206847 204800 100M 27 Hidden NTFS WinRE /dev/sdb2 206848 1338200063 1337993216 638G 7 HPFS/NTFS/exFAT /dev/sdb3 1338200064 1952602111 614402048 293G f W95 Ext'd (LBA) /dev/sdb4 1952602112 1953521663 919552 449M 27 Hidden NTFS WinRE /dev/sdb5 1338202112 1952602111 614400000 293G 7 HPFS/NTFS/exFAT Partition table entries are not in disk order. Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8BD48D6-A536-B541-AC3D-22B66D4F4146 Device Start End Sectors Size Type /dev/sdc1 2048 5860532223 5860530176 2.7T Microsoft basic data Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 4D13AF4B-FB62-B74B-A3FE-E4AE5BF3A3AB Device Start End Sectors Size Type /dev/sdd1 2048 5860532223 5860530176 2.7T Microsoft basic data Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 58A69147-6ECC-E14F-983A-E554BD67200D Device Start End Sectors Size Type /dev/sde1 2048 5860532223 5860530176 2.7T Microsoft basic data signmeuptoo@signmeuptoo-All-SeriesMint ~ $
That's a little annoying to read without the formating but i don't see any zfs partitions like you said earlier. They look like windows ntfs partitions.
Let's try to mount one to see what happens.
First create a mount point, using the terminal again.

Code: Select all

sudo mkdir /mnt/windisk1

Code: Select all

sudo mount -t ntfs /dev/sdc1 /mnt/windisk1
If you get an error post it back here. If you got no error message then it mounted successfully and you can access the drive by going through nemo to "File System -- > mnt --> windisk1"
Mounting in /mnt does not automaticaly add a shorcut to your desktop but i just drag the icon to the side bar when in the /mnt folder. Desktop is less cluttered that way too. Once they are linked in the sidebar you can rename it so that it's more familiar.

You other data drives seem to be /dev/sdd1 and /dev/sde1. You can just rinse and repeat above commands to mount them for testing. Remember to give each disk a unique mount point under /mnt
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

Great, no errors! Let me check mnt and see. Why didn't gparted allow these and why did it show them to be zfs?

I want to add something I didn't think to tell you, these drives came out of some sort of server or something, they are enterprise drives, was that a factor?

Thank you!

Now I have to learn those commands and their structure, the mount and the make dir.

Joy!

The command line is just the only way sometimes I guess!
I'm just a student, your guidance is appreciated.
odtech
Level 3
Level 3
Posts: 104
Joined: Sat Jan 21, 2017 9:25 am

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by odtech »

wutsinterweb wrote:Great, no errors! Let me check mnt and see. Why didn't gparted allow these and why did it show them to be zfs?

I want to add something I didn't think to tell you, these drives came out of some sort of server or something, they are enterprise drives, was that a factor?

Thank you!

Now I have to learn those commands and their structure, the mount and the make dir.

Joy!

The command line is just the only way sometimes I guess!
I don't know why gparted didn't accurately show your drives. I guess there's a reason it's not installed by default. My best guess is that it is missing a helper program.
Enterprise drives just means they are built to handle a heavier work load than normal desktop drives.

If you want the disks to be auto mounted at bootup you can add some entries to the fstab file.
First you need the uuid of each partition you would like mounted.

Code: Select all

blkid
Now you should see a list of all partitions with their uuid.
Open a second terminal and open the fstab file.

Code: Select all

sudo nano /etc/fstab
Below is an example of what the line looks like that you need to add. Just change the UUID to the correct one for your system. Rinse and repeat for each partition and remember to change the mount points for each one.

Code: Select all

UUID=f54bbe8e-d593-4f0c-a972-b0cc5a117b34 /mnt/windisk1 ntfs defaults 0 2
"Ctrl x" "y" "enter" to quit nano once you're done editing.
Now reboot and test.

You can use the builtin manual system to read op on these topic or just google fstab or mount to find articles on them.

Code: Select all

man fstab
and

Code: Select all

man mount
press q to exit man.
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

Thank you for that help! I now have a drive I want to format to ntfs while IN Linux Mint KDE, is this the command syntax:

sudo fdisk -t ntfs /dev/(name)

?

I get an unsupported disk label. I did partition the drive using KDE partition Manager, but don't see a way to format the drive using a GUI.
I'm just a student, your guidance is appreciated.
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

Code: Select all

signmeuptoo@signmeuptoo-All-SeriesMint ~ $ blkid
/dev/sda1: LABEL="System Reserved" UUID="7ECE760DCE75BE49" TYPE="ntfs" PARTUUID="b8b896aa-01"
/dev/sda2: UUID="D6868E2E868E0F65" TYPE="ntfs" PARTUUID="b8b896aa-02"
/dev/sda3: UUID="0EE4FE08E4FDF1B7" TYPE="ntfs" PARTUUID="b8b896aa-03"
/dev/sda5: UUID="b26dfdb5-5486-4b4b-bce1-7c1a3f8a6d72" TYPE="swap" PARTUUID="b8b896aa-05"
/dev/sda6: UUID="e0f9ffc8-0099-472d-a5ff-b773cf90fc36" TYPE="ext4" PARTUUID="b8b896aa-06"
/dev/sdb1: LABEL="System Reserved" UUID="386C85686C85222C" TYPE="ntfs" PARTUUID="a45c0796-01"
/dev/sdb2: LABEL="WindowPrograms" UUID="B2202B34202AFF4B" TYPE="ntfs" PARTUUID="a45c0796-02"
/dev/sdb4: UUID="88A20806A207F788" TYPE="ntfs" PARTUUID="a45c0796-04"
/dev/sdb5: LABEL="LinuxMediaStore" UUID="66EC8773EC873BF5" TYPE="ntfs" PARTUUID="a45c0796-05"
/dev/sdc1: TYPE="zfs_member" PARTLABEL="Basic data partition" PARTUUID="e0180d80-cc52-4194-a1a8-cb1f046c5a24"
/dev/sdd1: TYPE="zfs_member" PARTLABEL="Basic data partition" PARTUUID="4d1ca83c-9f36-4439-a358-6676a06b0fae"
/dev/sde1: TYPE="zfs_member" PARTLABEL="Basic data partition" PARTUUID="cc2176c0-3e99-4909-b11b-64ce72f57608"
signmeuptoo@signmeuptoo-All-SeriesMint ~ $ 
I tried but something isn't right, but did the same thing to recover and put fstab back the way it was.

I used UUID and took out the quotes, but I wonder if I need to have it be "PARTUUID" rather than just uuid? Also, it seems they are "basic data partition"s?
I'm just a student, your guidance is appreciated.
User avatar
wutsinterweb
Level 5
Level 5
Posts: 917
Joined: Tue Feb 28, 2017 2:14 am
Location: Connecticut, USA

Re: Newbie: Dual booting with WIN 10, but don't see Windows drives

Post by wutsinterweb »

It's the last three drives sdc1, sdd1, and sde1 that I need to add and Dolphin wont' see them, incidentally.
I'm just a student, your guidance is appreciated.
Post Reply

Return to “Newbie Questions”