Linux Lite Forums
Software - Support => Installing Linux Lite => Topic started by: arunp on August 14, 2014, 06:08:04 AM
-
Dear LL Team,
I have been successfully been installing LL2 in my USB & USB HDD and its working fine, except following issue;
1.When installed in USB HDD i configured one of the extended partition as FAT32 and gave the mount point as Windows the software installs and at reboot the grub runs and displays the standard LL boot options and then once booted to LL2 it goes blank further OS doesn't get loaded.
2.I reinstalled the same with all extended partitions as ext4 format it works fine.
I tried this n number of times the above 2 options the result was same, right now i working with the option 2, but i want to configure one of the partitions as FAT32.
Pl help me in this
Arun
-
Too difficult to figure out exactly what you are trying to do. Please post back with your desired partition setup in a list-type form -- eg. Partition -- Mount Point -- Format -- Partition Type.
Below is an example of how I'd like you to report what you are trying to do. It is NOT a suggestion of how to do anything, because I don't know how you are trying to set anything up yet.
/dev/sdb1 -- / (root) -- Ext4 -- Primary partition
/dev/sdb2 -- none -- none -- Extended partition
/dev/sdb5 -- /home -- Ext4 -- Logical partition
/dev/sdb6 -- /Windows -- FAT32 -- Logical partition
-
Dear gold_finger,
Thank you, will do the same; given below is my setup
(http://i.imgur.com/NKESCKs.png) (http://imgur.com/NKESCKs)
If i configure the unallocated space to
/dev/sdd7 -- FAT32 -- /Windows
The USB HDD boots and the grub shows the LL options and after the defined time it goes blank, the OS doesn't start.
If i configure the unallocated space to
/dev/sdd7 -- ext4 -- /local
It works perfect.
Pl guide me how to use FAT32 partition.
Arun
-
The drive can only have one "Extended" partition. If you are trying to create another one, that's why it's failing. Your sdb1 extended partition is currently filled by both the swap and home partitions. You can use GParted (from a live LL DVD/USB) to expand the sdb1 partition to include all of the unallocated space first, then add a "Logical" FAT32 partition if you want it inside the extended partition. Or you can just make the unallocated space into another "Primary" partition.
Are you trying to add that partition to the installation that you already have, or are you trying to re-install everything and have the FAT32 partition set-up during the installation?
Do you want the partition to be automatically mounted on each start-up?
-
Dear gold_finger,
I have tried all the options as you have said in the mail earlier;
First: During installation i added it to sdb1 as logical FAT32 partition - result - After Grub boot screen the OS doesn't start
Second: Using LL live CD and G parted removed this FAT32 and made it as unallocated using Gparted - result - After Grub boot screen the OS starts fine
Third: During installation i added it to sdb1 as logical e4xt partition - result - After Grub boot screen the OS starts fine
Fourth: I installed as given in the screen shot of my earlier post and using Gparted made it as another Primary FAT32 partition - - After Grub boot screen the OS doesn't start
As you mentioned I want to know how to configure FAT32 partition set-up during installation
Also i want to know how to assign it as another primary FAT32 partition and mount it automatically on each start-up.
Pl guide me...
-
I'm not sure what the problem is. Maybe FAT32 format can not be used for such a large partition. Have read that there is normally a size limit of 32GB in MS Windows for FAT32 partitions, but did not think that applied to Linux as well. Maybe it does. I don't know since I've not tried that.
You're not assigning the FAT32 partition a mount point of "/" or "/home", are you?
When you install and are asked for a mount point for the FAT32 partition, what are you filling in for the mount point?
As an experiment, try using NTFS format instead and see if that works. It should.
Do you have to use FAT32 for some reason? Could you use NTFS instead (assuming that experiment works)?
-
Dear gold_fingger,
Thanks for the reply, I am mounting it as /Windows also tried it with /Dos, also tried NTFS still the same problem.
I am confused, may be something to do with the Grub? any script to be edited? because the Grub boots shows all the LL options with the seconds running below and after the defined time it goes blank like its not able to decide to boot from where (I persume) :))
I hope you & the LL team dig into this issue and find out the solution :)
-
If you formatted that partition as NTFS and still had same problem, then my best guess is that you are making some kind of error in the steps you are following.
Boot the computer with your Linux Lite installation DVD. Once booted up, go to Menu -> System -> Partition Drives to start the GParted program. Take a screenshot of the window showing your drive partitions and post that back here for us to see.
Open a Terminal and enter the following commands:
lsblk
sudo blkid -c /dev/null
sudo parted -l(NOTE: that's a lowercase letter "L" at end of last command, not the number 1.)
Copy the entire terminal output and paste it back here for us to see.
Follow directions on this post (https://www.linuxliteos.com/forums/index.php?topic=487.msg2469#msg2469) for posting your terminal output and screenshot back here to the forum.
-
Dear gold_finger,
Thanks for the mail, here is the output from the terminal:
arunp@arunp-Vostro-3400:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 125.5M 0 part
├─sda2 8:2 0 12.2G 0 part
├─sda3 8:3 0 102.9G 0 part
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 117.7G 0 part /media/arunp/30D748C43DA76362
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 1K 0 part
├─sdb2 8:18 0 59.6G 0 part /
├─sdb3 8:19 0 305.6G 0 part /media/arunp/59F1FF817729F31A
├─sdb5 8:21 0 7.5G 0 part [SWAP]
└─sdb6 8:22 0 93.1G 0 part /home
sr0 11:0 1 1024M 0 rom
arunp@arunp-Vostro-3400:~$ sudo blkid -c /dev/null
[sudo] password for arunp:
Sorry, try again.
[sudo] password for arunp:
/dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="07DB-011B" TYPE="vfat"
/dev/sda2: LABEL="RECOVERY" UUID="663EC66B3EC633B9" TYPE="ntfs"
/dev/sda3: LABEL="OS" UUID="0E58C90F58C8F68D" TYPE="ntfs"
/dev/sda5: UUID="30D748C43DA76362" TYPE="ntfs"
/dev/sdb2: UUID="13ea928f-6d38-445e-b3b7-c06760ec9fea" TYPE="ext4"
/dev/sdb3: UUID="59F1FF817729F31A" TYPE="ntfs"
/dev/sdb5: UUID="01dae284-d8de-4c09-bea1-2759ea815dc4" TYPE="swap"
/dev/sdb6: UUID="0278cd76-2f6f-44fa-bb27-87602c6c6332" TYPE="ext4"
arunp@arunp-Vostro-3400:~$
-
Sorry, need output from one more command please:
cat /etc/fstab
-
linux@linux:~$ cat /etc/fstab
overlayfs / overlayfs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
/dev/sdb5 swap swap defaults 0 0
-
Looks like you ran that last command from a live DVD. Boot into your installed Mint on the hard drive and run the command again. I need the output from the installed version, not the live DVD. Thanks.
-
Dear gold_finger,
That is the issue, it doesn't boot if i configure it in that fashion. Now again i have booted it with CD and use Gparted and made the NTFS partition as unallocated and then restarted and now it boots with USB HD. Now again using the Gparted and converted the Unalocated space to NTFS and run the script and posting here.
arunp@arunp-Vostro-3400:~$ cat /etc/fstab
# /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/sdb2 during installation
UUID=13ea928f-6d38-445e-b3b7-c06760ec9fea / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb6 during installation
UUID=0278cd76-2f6f-44fa-bb27-87602c6c6332 /home ext4 defaults 0 2
# swap was on /dev/sdb5 during installation
UUID=01dae284-d8de-4c09-bea1-2759ea815dc4 none swap sw 0 0
Now if I restart the Grub runs and it doesn't start the OS
-
That is the issue, it doesn't boot if i configure it in that fashion. Now again i have booted it with CD and use Gparted and made the NTFS partition as unallocated and then restarted and now it boots with USB HD. Now again using the Gparted and converted the Unalocated space to NTFS and run the script and posting here.
arunp@arunp-Vostro-3400:~$ cat /etc/fstab
# /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/sdb2 during installation
UUID=13ea928f-6d38-445e-b3b7-c06760ec9fea / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb6 during installation
UUID=0278cd76-2f6f-44fa-bb27-87602c6c6332 /home ext4 defaults 0 2
# swap was on /dev/sdb5 during installation
UUID=01dae284-d8de-4c09-bea1-2759ea815dc4 none swap sw 0 0
Now if I restart the Grub runs and it doesn't start the OS
If I understand you right, you're saying that at this point you are booted into the system and used GParted to convert sda3 to NTFS format. Also, you made NO changes to fstab file -- it still reads as shown here. Correct? And you are saying that if you were to reboot at this point, it will not work?
I have to say, that makes absolutely no sense to me and I've never seen that happen before.
Finish doing whatever you do for the NTFS partition and reboot the computer. If it does not boot into your installed Linux Lite system, reboot again with the live DVD one more time before making any changes. From the LIVE DVD, post back entire output of these commands:
lsblk
sudo parted -l
sudo blkid -c /dev/null
sudo mount /dev/sdb2 /mnt
cat /mnt/etc/fstab
-
Dear gold_finger,
Yes, your understanding is exactly right, After the conversion of sdb3 to NTFS format and restarted the system, it does not boot from USB HDD after the Grub screen, Here is the output from the system as requested by you after booting through LL CD
linux@linux:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 125.5M 0 part
├─sda2 8:2 0 12.2G 0 part
├─sda3 8:3 0 102.9G 0 part
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 117.7G 0 part
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 1K 0 part
├─sdb2 8:18 0 59.6G 0 part /mnt
├─sdb3 8:19 0 305.6G 0 part
├─sdb5 8:21 0 7.5G 0 part [SWAP]
└─sdb6 8:22 0 93.1G 0 part
sr0 11:0 1 700M 0 rom /cdrom
loop0 7:0 0 668.3M 1 loop /rofs
linux@linux:~$ sudo parted -l
Model: ATA WDC WD2500BEKT-7 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 132MB 132MB primary fat16 diag
2 134MB 13.2GB 13.0GB primary ntfs boot
3 13.2GB 124GB 110GB primary ntfs
4 124GB 250GB 126GB extended
5 124GB 250GB 126GB logical ntfs
Model: Seagate Portable (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
2 1049kB 64.0GB 64.0GB primary ext4 boot
1 64.0GB 172GB 108GB extended
5 64.0GB 72.0GB 7999MB logical linux-swap(v1)
6 72.0GB 172GB 100GB logical ext4
3 172GB 500GB 328GB primary ntfs
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0
has been opened read-only.
Error: Invalid partition table - recursive partition on /dev/sr0.
Ignore/Cancel? i
Model: PLDS DVD+-RW DS-8A5SH (scsi)
Disk /dev/sr0: 734MB
Sector size (logical/physical): 2048B/2048B
Partition Table: msdos
Number Start End Size Type File system Flags
linux@linux:~$ sudo blkid -c /dev/null
/dev/loop0: TYPE="squashfs"
/dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="07DB-011B" TYPE="vfat"
/dev/sda2: LABEL="RECOVERY" UUID="663EC66B3EC633B9" TYPE="ntfs"
/dev/sda3: LABEL="OS" UUID="0E58C90F58C8F68D" TYPE="ntfs"
/dev/sda5: UUID="30D748C43DA76362" TYPE="ntfs"
/dev/sr0: LABEL="Linux Lite 2.0 64-bit" TYPE="iso9660"
/dev/sdb2: UUID="13ea928f-6d38-445e-b3b7-c06760ec9fea" TYPE="ext4"
/dev/sdb3: UUID="6B6D529C3C948BA7" TYPE="ntfs"
/dev/sdb5: UUID="01dae284-d8de-4c09-bea1-2759ea815dc4" TYPE="swap"
/dev/sdb6: UUID="0278cd76-2f6f-44fa-bb27-87602c6c6332" TYPE="ext4"
linux@linux:~$ sudo mount /dev/sdb2 /mnt
mount: /dev/sdb2 already mounted or /mnt busy
mount: according to mtab, /dev/sdb2 is already mounted on /mnt
linux@linux:~$ cat /mnt/etc/fstab
# /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/sdb2 during installation
UUID=13ea928f-6d38-445e-b3b7-c06760ec9fea / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb6 during installation
UUID=0278cd76-2f6f-44fa-bb27-87602c6c6332 /home ext4 defaults 0 2
# swap was on /dev/sdb5 during installation
UUID=01dae284-d8de-4c09-bea1-2759ea815dc4 none swap sw 0 0
linux@linux:~$
-
I don't see anything that would cause that problem so it still makes no sense. At this point, let's try wiping out the whole drive and starting over. If there is anything on there that you need to save, do that first.
* Boot with live LL DVD
* Open GParted and delete all partitions on the USB drive.
- Delete logical partitions before extended partition
- Delete extended partition
- Delete primary partitions
- If you can't delete swap, right-click it and choose "Swapoff" first, then delete.
- If you can't delete other partitions, right-click and choose "Unmount", then delete.
* Click "Apply" button (arrow button under word "Help") to finalize deletions.
* Now make a new partition table: Device -> Create Partition Table -> msdos
* Make the following new partitions with GParted:
- Primary partition -- 25GB -- Ext4 formatting (this will be root)
- Extended partition -- size = rest of drive, 475GB
- Logical partition -- 8GB -- Swap
- Logical partition -- 100-125GB -- Ext4 formatting (this will be /home)
- Logical partition -- 342-367GB -- NTFS formatting (this will be /mnt/Windows)
- Click "Apply" button to finalize making your new partitions.
* Close GParted and start the installer.
* Choose "Something Else" option, then on the partitioning page:
- Highlight 25GB partition, hit "Change", then
- Use as = Ext4 file system
- Mount point = "/" (root)
- Size = leave it at 25GB that you made with GParted
- Format Box = does not matter (you already formatted with GParted)
- Highlight 100-125GB partition, hit "Change", then
- Use as = Ext4 file system
- Mount point = "/home"
- Size = leave it at 100-125GB that you made with GParted
- Format Box = does not matter (you already formatted with GParted)
- Highlight 342-367GB partition, hit "Change", then
- Use as = NTFS file system
- Mount point = "/mnt/Windows" (you will need to type that in -- no quote marks.)
- Size = leave it at 342-367GB that you made with GParted
- Format Box = does not matter (you already formatted with GParted)
- No need to do anything with Swap partition. Installer will use it automatically.
- Near bottom of window, "Device for boot loader installation" = /dev/sdb (or whatever the device name for the USB drive is). It will be pre-filled with /dev/sda. You need to change it to the USB drive designation.
* Double-check your entries, then finish the installation
If you follow these steps and it refuses to boot properly, then I have no idea what is going wrong.
-
Dear gold_finger,
Thanks for all your effort, I installed the system as per your guide lines and restarted the system still the same issue. gild_finger i want to insist on one point i presume we are missing is that the "Hard disk boots, it shows all the LL grub boot options and the 10 seconds time is running below after that the OS hangs or doesn't start further in lay mans language the Grub is not able to find/decide the boot folder if we configure the system in this format. i am sorry if you have taken this point into account before to mention it again. given below is the inputs from the commands you have already asked to post after this installation:
linux@linux:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 125.5M 0 part
├─sda2 8:2 0 12.2G 0 part
├─sda3 8:3 0 102.9G 0 part
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 117.7G 0 part
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 24.4G 0 part
├─sdb2 8:18 0 1K 0 part
├─sdb5 8:21 0 7.8G 0 part [SWAP]
├─sdb6 8:22 0 97.7G 0 part
└─sdb7 8:23 0 335.9G 0 part
sr0 11:0 1 700M 0 rom /cdrom
loop0 7:0 0 668.3M 1 loop /rofs
linux@linux:~$ sudo blkid -c /dev/null
/dev/loop0: TYPE="squashfs"
/dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="07DB-011B" TYPE="vfat"
/dev/sda2: LABEL="RECOVERY" UUID="663EC66B3EC633B9" TYPE="ntfs"
/dev/sda3: LABEL="OS" UUID="0E58C90F58C8F68D" TYPE="ntfs"
/dev/sda5: UUID="30D748C43DA76362" TYPE="ntfs"
/dev/sr0: LABEL="Linux Lite 2.0 64-bit" TYPE="iso9660"
/dev/sdb1: UUID="3e1b2b86-cac2-49d1-a834-1b6a7f16b1be" TYPE="ext4"
/dev/sdb5: UUID="e36750d1-437d-45be-b954-be8a4b8cb74d" TYPE="swap"
/dev/sdb6: UUID="3e8711c6-3e32-44f2-a02e-db8f65ce6f6c" TYPE="ext4"
/dev/sdb7: UUID="62B9FEA64E895E5B" TYPE="ntfs"
linux@linux:~$ sudo parted -llinux@linux:~$ cat /etc/fstab
parted: invalid option -- 'i'
parted: invalid option -- 'n'
parted: invalid option -- 'u'
parted: invalid option -- 'x'
parted: invalid option -- '@'
parted: invalid option -- 'i'
parted: invalid option -- 'n'
parted: invalid option -- 'u'
parted: invalid option -- 'x'
parted: invalid option -- ':'
parted: invalid option -- '~'
parted: invalid option -- '$'
Usage: parted [-hlmsv] [-a<align>] [DEVICE [COMMAND [PARAMETERS]]...]
linux@linux:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 125.5M 0 part
├─sda2 8:2 0 12.2G 0 part
├─sda3 8:3 0 102.9G 0 part
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 117.7G 0 part
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 24.4G 0 part
├─sdb2 8:18 0 1K 0 part
├─sdb5 8:21 0 7.8G 0 part [SWAP]
├─sdb6 8:22 0 97.7G 0 part
└─sdb7 8:23 0 335.9G 0 part
sr0 11:0 1 700M 0 rom /cdrom
loop0 7:0 0 668.3M 1 loop /rofs
linux@linux:~$ sudo parted -l
Model: ATA WDC WD2500BEKT-7 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 132MB 132MB primary fat16 diag
2 134MB 13.2GB 13.0GB primary ntfs boot
3 13.2GB 124GB 110GB primary ntfs
4 124GB 250GB 126GB extended
5 124GB 250GB 126GB logical ntfs
Model: Seagate Portable (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 26.2GB 26.2GB primary ext4 boot
2 26.2GB 500GB 474GB extended
5 26.2GB 34.6GB 8389MB logical linux-swap(v1)
6 34.6GB 139GB 105GB logical ext4
7 139GB 500GB 361GB logical ntfs
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0
has been opened read-only.
Error: Invalid partition table - recursive partition on /dev/sr0.
Ignore/Cancel? i
Model: PLDS DVD+-RW DS-8A5SH (scsi)
Disk /dev/sr0: 734MB
Sector size (logical/physical): 2048B/2048B
Partition Table: msdos
Number Start End Size Type File system Flags
linux@linux:~$ sudo blkid -c /dev/null
/dev/loop0: TYPE="squashfs"
/dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="07DB-011B" TYPE="vfat"
/dev/sda2: LABEL="RECOVERY" UUID="663EC66B3EC633B9" TYPE="ntfs"
/dev/sda3: LABEL="OS" UUID="0E58C90F58C8F68D" TYPE="ntfs"
/dev/sda5: UUID="30D748C43DA76362" TYPE="ntfs"
/dev/sr0: LABEL="Linux Lite 2.0 64-bit" TYPE="iso9660"
/dev/sdb1: UUID="3e1b2b86-cac2-49d1-a834-1b6a7f16b1be" TYPE="ext4"
/dev/sdb5: UUID="e36750d1-437d-45be-b954-be8a4b8cb74d" TYPE="swap"
/dev/sdb6: UUID="3e8711c6-3e32-44f2-a02e-db8f65ce6f6c" TYPE="ext4"
/dev/sdb7: UUID="62B9FEA64E895E5B" TYPE="ntfs"
linux@linux:~$ sudo mount /dev/sdb2 /mnt
mount: block device /dev/sdb2 is write-protected, mounting read-only
mount: you must specify the filesystem type
linux@linux:~$ cat /mnt/etc/fstab
cat: /mnt/etc/fstab: No such file or directory
linux@linux:~$ sudo mount /dev/sdb2 /mnt
mount: block device /dev/sdb2 is write-protected, mounting read-only
mount: you must specify the filesystem type
linux@linux:~$
-
You've got a strange situation going on there. It makes no sense for it to be doing that. Your partitions look good, so don't see a problem with them. It appears that you followed steps correctly. I'm a bit stumped -- have never seen or heard of this happening before. At this point just going to have you repost output for commands that needed to be adjusted for the new partition layout you have now. Your old layout needed them to be run on sdb2. Your partitions changed with the new install. Run commands again as shown below -- this time they are going to apply to the new root partition, sdb1.
linux@linux:~$ sudo mount /dev/sdb2 /mnt
mount: block device /dev/sdb2 is write-protected, mounting read-only
mount: you must specify the filesystem type
This was looking for the old root partition on sdb2. Root is now on sdb1, so go ahead with new commands below.
sudo mount /dev/sdb1 /mnt
cat /mnt/etc/fstab
sudo umount /mnt
Post back with full output from those commands please.
-
Dear gold_finger,
I tried another way of installation, Primary partition of sdb1 - 124 GB, swaparea - 8 GB and rest extended partition of NTFS - 364 GB and installed the system. This time the system booted but doesn't mount the NTFS drive i.e not recognize the drive. given below is the output from the same commands you have specified.
arunp@arunp-Vostro-3400:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 125.5M 0 part
├─sda2 8:2 0 12.2G 0 part
├─sda3 8:3 0 102.9G 0 part
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 117.7G 0 part
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 119.2G 0 part /
├─sdb2 8:18 0 1K 0 part
├─sdb5 8:21 0 7.5G 0 part [SWAP]
└─sdb6 8:22 0 339.1G 0 part /mnt/Windows
sr0 11:0 1 1024M 0 rom
arunp@arunp-Vostro-3400:~$ sudo parted -l
[sudo] password for arunp:
Model: ATA WDC WD2500BEKT-7 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 132MB 132MB primary fat16 diag
2 134MB 13.2GB 13.0GB primary ntfs boot
3 13.2GB 124GB 110GB primary ntfs
4 124GB 250GB 126GB extended
5 124GB 250GB 126GB logical ntfs
Model: Seagate Portable (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 128GB 128GB primary ext4 boot
2 128GB 500GB 372GB extended
5 128GB 136GB 7999MB logical linux-swap(v1)
6 136GB 500GB 364GB logical ntfs
arunp@arunp-Vostro-3400:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
#Entry for /dev/sdb1 :
UUID=152be27a-4d93-4fb6-95e5-45e098c6f568 / ext4 errors=remount-ro 0 1
#Entry for /dev/sdb6 :
UUID=5480819C42DE547D /mnt/Windows ntfs-3g defaults,locale=en_US.UTF-8 00
#Entry for /dev/sdb5 :
UUID=f943611f-2a44-4f89-9b69-f840156d1c80 none swap sw 0 0
arunp@arunp-Vostro-3400:~$ sudo mount /dev/sdb6 /mnt
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
arunp@arunp-Vostro-3400:~$ cat /mnt/etc/fstab
cat: /mnt/etc/fstab: No such file or directory
arunp@arunp-Vostro-3400:~$ sudo mount /dev/sdb1 /mnt
[sudo] password for arunp:
arunp@arunp-Vostro-3400:~$ cat /mnt/etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
#Entry for /dev/sdb1 :
UUID=152be27a-4d93-4fb6-95e5-45e098c6f568 / ext4 errors=remount-ro 0 1
#Entry for /dev/sdb6 :
UUID=5480819C42DE547D /mnt/Windows ntfs-3g defaults,locale=en_US.UTF-8 00
#Entry for /dev/sdb5 :
UUID=f943611f-2a44-4f89-9b69-f840156d1c80 none swap sw 0 0
arunp@arunp-Vostro-3400:~$ sudo umount /mnt
arunp@arunp-Vostro-3400:~$
I will also reconfigure the system the Old way and post you the output as requested by you
-
Something does not make any sense to me. This is the second time now that you have posted output that indicates that you are booted into the installed LL and that it has recognized and mounted the NTFS partition -- but you seem to think that it has not.
On your last post you said it booted okay, but did not recognize the NTFS partition. That is not what I see. In screenshot below, the first red box shows that you are booted into your installed LL. The second red box show that it has mounted the NTFS partition at /mnt/Windows.
(http://ibin.co/1XuiN1G8iwcJ)
The other time this happened (where you said it wouldn't boot into the installed LL), I asked you in "Reply #7" to boot with the live DVD and run 3 commands. Your reply to that, ("Reply #8), indicated that you had run the commands from within the installed (not live) LL. In other words, you had booted into the installed LL while the sdb3 partition was formatted as NTFS -- which is something you said you could not do. When I saw that, I asked you in "Reply 9" to post output from "cat /etc/fstab" thinking you would again boot into your installed LL to do it. You then ran that command from the live DVD instead, which gave wrong info. So I asked in "Reply 11" for you to boot back into LL and run command from there. To which you said in "Reply 12" that you couldn't boot into it, even though that's exactly what you did do in "Reply 8". However, you made changes to the drive and I could no longer pursue the question.
Here is screenshot of your "Reply #8" with red boxes showing that you were booted into the installed LL and that it recognized and mounted the NTFS partition.
(http://ibin.co/1XuizQEZthB2)
One last note for now:
I'm not saying this to be mean, but to be blunt -- we are going in circles here and I feel like I'm wasting my time. I make replies to your questions and ask for output based on what you post. But, you keep making further changes to the partitions in the meantime which renders the command output I ask for inapplicable to your new, changed partitions. If you want me to continue trying to figure this out, please wait for my answers before making further changes.
In your last post you said you were going to change everything back to "the Old way" -- whatever that means. Post back whatever the situation is at that point, then don't change anything until I have a chance to reply. If you change things again before seeing my reply, I will stop replying all together.
-
Dear gold_finger,
Thank you for all posts and patience to my queries. but the fact i want to communicate to you is fact and reality of what is happening on the system, I am to aware that that in the terminal it shows the NTFS partition recognized but the reality is it is not appearing in the File manager or on the desktop screen, here is the screen shot side by side showing the terminal out put and file manager not showing the NTFS drive.
(http://[URL=http://imgur.com/8wzoNYU][IMG]http://i.imgur.com/8wzoNYU.png)[/URL][/img]
The same is true that it doesn't boot if configured in the original fashion advised by you.
gold_finger i wanted to assure you is that i sincerely wanted to use LL and distribute it among my friends here when i started that the first hindrance i faced was this i.e. they wanted one common drive partition in the portable drive where the files in this drive can be read when booted with windows and also with LL when it is booted with LL.
If i am facing this problem any body trying in this combination will definitely face this issue, I am putting all my efforts to support the LL team to put on a robust system which i am sure will once dominate the desktops. I request you if you don't trust my posts pl try this installation your self on a portable drive and if it works fine with every boot just post back one line, "it works fine" else we will continue to work on it still we put a robust LL to the world.
I sincerely apologize if my post has offended you.
Now on will continue to Post only what is requested by you.
-
The image is not appearing in the previous post
(http://i.imgur.com/8wzoNYU.png) (http://imgur.com/8wzoNYU)
-
You did not offend me. The problem is that since you are new to Linux, you don't know what to look for and sometimes there are terminology mix ups. What you describe one way, people who have a Linux-based mindset might interpret as something else from what you actually meant. In my posts I was trying to find out certain things that would divulge whether it was just a simple misunderstanding or not, but you kept trying new things on your own and those new things ended up making my questions useless.
I now see what the problem is. You are expecting to see the NTFS partition in your file manager under either Devices, Places or in the Home folder. That is not where it is going to show up. When a partition is mounted to a particular spot in the file system it will no longer show up under Devices or Places. And it won't show up in your Home folder either unless you made the mount point in the Home folder.
In your last screenshot, to find the NTFS partition you need to go to where you mounted it -- in /mnt/Windows. Open your file manager and click "File System" under Devices. That will put you at the root of the file system (at "/"). On right side you will see a bunch of folders. Click on the "/mnt" folder. Then click on "/Windows" and you will be in the NTFS partition. Try to create a folder in it. Let me know if you are able to do that, or what happens when you try.
P.s. If the system does not boot I have no clue what could be wrong with it. I've never heard of that happening before.
P.s.s. Assuming that you still have system setup as per latest screenshot and that the system does currently boot up properly, do the following to make the /mnt/Windows partition show up in your Home folder. Open a terminal and enter this command to create a symlink to the partition. Substitute your actual username where I have "username" below.
ln -s /mnt/Windows /home/username
-
Dear gold_finger,
Thank you for your patience and the excellent reply :), it worked perfectly and the drive is showing up, but not under devices, directly under File system as "mnt". I could create the link to home folder as instructed by you.
Now we need to look at our old problem, "LL is not booting". I will reconfigure the system to old partitions and install and post the outputs as requested by you in reply on 23rd Aug.
Once again thank you for your excellent support
-
:( I don't know how much help I'll be but I'll try anyways.
I am fighting my own /dev/sdb. I have it hooked up via adapter cables. The device is a 16gig SSD removed from my Acer C710 chromebook.
It acts flaky as hell. It wont show in fdisk -l, parted -l, sudo gdisk -l. example:
# fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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
Disk identifier: 0x7b89e107
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 239282175 119537664 7 HPFS/NTFS/exFAT
/dev/sda3 239284222 625141759 192928769 5 Extended
/dev/sda5 276353024 616949759 170298368 83 Linux
/dev/sda6 239284224 276350630 18533203+ 83 Linux
/dev/sda7 616951808 625141759 4094976 82 Linux swap / Solaris
# parted -l
Model: ATA SAMSUNG HM321HI (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 106MB 105MB primary ntfs boot
2 106MB 123GB 122GB primary ntfs
3 123GB 320GB 198GB extended
6 123GB 141GB 19.0GB logical ext4
5 141GB 316GB 174GB logical ext4
7 316GB 320GB 4193MB logical linux-swap(v
# gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.8
Problem opening /dev/sdb for reading! Error is 2.
The specified file does not exist!
So. I used a gparted live cd ver 0.19.1-1.i486 and booted it. I got it to see /dev/sdb. I assigned a partition table and told it to be GPT. I hit apply. Done. I then made a new partition and told it to be ext4 and labled it as / (root). Apply and done.
Gparted live iso shows my 16gig ssd as / formatted as ext 4 as a GPT drive.
But. Becuase the hard drive is flaky. I have to look in
# dmesg | tail
[ 209.172126] Buffer I/O error on device sdb, logical block 0
[ 209.172196] ldm_validate_partition_table(): Disk read failed.
[ 209.172219] Dev sdb: unable to read RDB block 0
[ 209.172252] sdb: unable to read partition table
[ 209.172441] sd 7:0:0:0: [sdb] READ CAPACITY failed
[ 209.172445] sd 7:0:0:0: [sdb]
[ 209.172446] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 209.172449] sd 7:0:0:0: [sdb] Sense not available.
[ 209.172477] sd 7:0:0:0: [sdb] Attached SCSI disk
[ 986.488753] perf interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Because I still can't get the durn thing to be recognised even then. So probably a hardware issue.
Anyways. Since you asked. Maybe try
sudo dmesg | tail
instead of
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 298.1G 0 disk
├─sda1 8:1 0 100M 0 part
├─sda2 8:2 0 114G 0 part
├─sda3 8:3 0 1K 0 part
├─sda5 8:5 0 162.4G 0 part /home
├─sda6 8:6 0 17.7G 0 part /
└─sda7 8:7 0 3.9G 0 part [SWAP]
sr0 11:0 1 1024M 0 rom
Because as you can see. dmesg can see my /dev/sdb when nothing else can.
HTH. Like I said. My chromebook is dead and I am fighting with its hard drive myself.
Just stepped in because I was asked. I don't know how much help or not this gives.
Happy Trails, Rok
Oh yeah. Since we are talking Windows File systems here.
apt-cache policy ntfs-3g
And was a md5sum done of Linux Lite 2.0 before installing?
-
Dear gold_finger,
I reinstalled LL with our original configuration (sorry partition sizes got changed) and posted below the out puts as requested from your reply #17 and also the out put from other commands posted in your earlier output. The problem remains the same, when booted the Grub blue screen runs and after the defined 10 Seconds it goes blank, does not start OS.
linux@linux:~$ sudo mount /dev/sdb1 /mnt
linux@linux:~$ cat /mnt/etc/fstab
# /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/sdb1 during installation
UUID=668e1088-6de1-41c1-abe5-be736568f639 / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb6 during installation
UUID=862df362-9691-4344-a7d3-a9f29295a067 /home ext4 defaults 0 2
# /mnt/Windows was on /dev/sdb7 during installation
UUID=58D83E5E1618D324 /mnt/Windows ntfs defaults,umask=007,gid=46 0 0
# swap was on /dev/sdb5 during installation
UUID=f943611f-2a44-4f89-9b69-f840156d1c80 none swap sw 0 0
linux@linux:~$ sudo umount /mnt
linux@linux:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 125.5M 0 part
├─sda2 8:2 0 12.2G 0 part
├─sda3 8:3 0 102.9G 0 part
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 117.7G 0 part
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 119.2G 0 part
├─sdb2 8:18 0 1K 0 part
├─sdb5 8:21 0 7.5G 0 part [SWAP]
├─sdb6 8:22 0 97.7G 0 part
└─sdb7 8:23 0 241.5G 0 part
sr0 11:0 1 700M 0 rom /cdrom
loop0 7:0 0 668.3M 1 loop /rofs
linux@linux:~$ sudo blkid -c /dev/null
/dev/loop0: TYPE="squashfs"
/dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="07DB-011B" TYPE="vfat"
/dev/sda2: LABEL="RECOVERY" UUID="663EC66B3EC633B9" TYPE="ntfs"
/dev/sda3: LABEL="OS" UUID="0E58C90F58C8F68D" TYPE="ntfs"
/dev/sda5: UUID="30D748C43DA76362" TYPE="ntfs"
/dev/sr0: LABEL="Linux Lite 2.0 64-bit" TYPE="iso9660"
/dev/sdb1: UUID="668e1088-6de1-41c1-abe5-be736568f639" TYPE="ext4"
/dev/sdb5: UUID="f943611f-2a44-4f89-9b69-f840156d1c80" TYPE="swap"
/dev/sdb6: UUID="862df362-9691-4344-a7d3-a9f29295a067" TYPE="ext4"
/dev/sdb7: UUID="58D83E5E1618D324" TYPE="ntfs"
linux@linux:~$ sudo parted -l
Model: ATA WDC WD2500BEKT-7 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 132MB 132MB primary fat16 diag
2 134MB 13.2GB 13.0GB primary ntfs boot
3 13.2GB 124GB 110GB primary ntfs
4 124GB 250GB 126GB extended
5 124GB 250GB 126GB logical ntfs
Model: Seagate Portable (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 128GB 128GB primary ext4 boot
2 128GB 500GB 372GB extended
5 128GB 136GB 7999MB logical linux-swap(v1)
6 136GB 241GB 105GB logical ext4
7 241GB 500GB 259GB logical ntfs
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0
has been opened read-only.
Error: Invalid partition table - recursive partition on /dev/sr0.
Ignore/Cancel? i
Model: PLDS DVD+-RW DS-8A5SH (scsi)
Disk /dev/sr0: 734MB
Sector size (logical/physical): 2048B/2048B
Partition Table: msdos
Number Start End Size Type File system Flags
linux@linux:~$
Pl look into it and let me know what is to be done further..
-
arunp,
From what I see, everything looks to be in order so really don't know what is causing the problem. At this point, I can only make wild guesses as to what's going on.
A few weeks ago on a different forum someone else was having similar (not exactly the same) problems with booting. Went back and forth trying various things for over seven pages thinking that the person must have been doing something wrong. In the end the cause turned out to be something nobody suspected and we discovered it virtually by accident -- his keyboard wasn't being read properly on boot-up. Maybe something obscure and silly like that is going on with you.
Since you appear to be partitioning and installing everything correctly, I can only guess that there might be some kind of miscellaneous hardware issue going on. So, let's just run through some things to check.
1. Is your monitor connected directly to the computer, or are you using some type of adapter or switch between the monitor and computer connection?
2. Is your keyboard connected directly to computer, or are you using some type of adapter or switch between it and the computer?
3. Do you have access to another keyboard that you can plug into computer and try? (Can you borrow one to test on your computer from a friend, relative, or from work?)
4. Check all connections to make sure they are not loose -- either where they are plugged into back of computer or where they are connected to your peripherals.
5. Open computer and check that all connections are secure:
- check that RAM are firmly seated in their slots
- check cable connections between hard drives and motherboard
- check cable connections between DVD/CD player and motherboard
- if you have a graphics card, check that it is firmly seated in its slot
6. If none of the above help, report back with exact brand and model # of your computer, your monitor, your keyboard and your mouse. Maybe we can do searches for those to see if there are any reports of strange Linux issues with them?
Unfortunately that's all I can think of right now. Countless people use NTFS and FAT32 partitions with Linux without issue, so I seriously doubt that is the cause of the problem. It must be some other miscellaneous thing causing the problem.
-
Dear gold_finger,
I am using a Dell Vostro 3400 Laptop, Every thing is working fine with this as the same laptop works fine when i boot with windows and also LL configured as i posted in my reply 24th Aug 14, this reply also i am typing with LL booted and from Firefox browser in the below configuration
arunp@arunp-Vostro-3400:~$ sudo mount /dev/sdb1 /mnt
[sudo] password for arunp:
arunp@arunp-Vostro-3400:~$ cat /mnt/etc/fstab
# /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/sdb1 during installation
UUID=c4d3ddc8-fde0-4de3-91c1-e4ea48250115 / ext4 errors=remount-ro 0 1
# /mnt/Windows was on /dev/sdb6 during installation
UUID=2555-2887 /mnt/Windows vfat utf8,umask=007,gid=46 0 1
# swap was on /dev/sdb5 during installation
UUID=f943611f-2a44-4f89-9b69-f840156d1c80 none swap sw 0 0
arunp@arunp-Vostro-3400:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 125.5M 0 part
├─sda2 8:2 0 12.2G 0 part
├─sda3 8:3 0 102.9G 0 part
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 117.7G 0 part
sdb 8:16 0 465.8G 0 disk
├─sdb1 8:17 0 119.2G 0 part /
├─sdb2 8:18 0 1K 0 part
├─sdb5 8:21 0 7.5G 0 part [SWAP]
└─sdb6 8:22 0 339.1G 0 part
sr0 11:0 1 1024M 0 rom
arunp@arunp-Vostro-3400:~$ sudo blkid -c /dev/null
/dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="07DB-011B" TYPE="vfat"
/dev/sda2: LABEL="RECOVERY" UUID="663EC66B3EC633B9" TYPE="ntfs"
/dev/sda3: LABEL="OS" UUID="0E58C90F58C8F68D" TYPE="ntfs"
/dev/sda5: UUID="30D748C43DA76362" TYPE="ntfs"
/dev/sdb1: UUID="c4d3ddc8-fde0-4de3-91c1-e4ea48250115" TYPE="ext4"
/dev/sdb5: UUID="f943611f-2a44-4f89-9b69-f840156d1c80" TYPE="swap"
/dev/sdb6: UUID="2555-2887" TYPE="vfat"
arunp@arunp-Vostro-3400:~$ sudo parted -l
Model: ATA WDC WD2500BEKT-7 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 132MB 132MB primary fat16 diag
2 134MB 13.2GB 13.0GB primary ntfs boot
3 13.2GB 124GB 110GB primary ntfs
4 124GB 250GB 126GB extended
5 124GB 250GB 126GB logical ntfs
Model: Seagate Portable (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 128GB 128GB primary ext4 boot
2 128GB 500GB 372GB extended
5 128GB 136GB 7999MB logical linux-swap(v1)
6 136GB 500GB 364GB logical fat32
arunp@arunp-Vostro-3400:~$
This issue happens only when an extended partition is configured with ext4 (sdb6)for /home along with an extended NTFS or FAT32 (sdb7)format for /Windows.
Is it possible anybody in your team can try installing in this configuration and figure out what's the issue.
-
Didn't know you were using a laptop.
Since this is such a weird occurrence and it appears that you aren't doing anything wrong, I'm going to install as you did to a spare computer and see if I run into same thing. Will post back later with the results.
-
Sorry arunp,
I'm fresh out of ideas. Did test install on a spare laptop and everything worked without any problems. Here is output from the test:
bill@HP-Pavilion-dv6000:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 149.1G 0 disk
├─sda1 8:1 0 14.9G 0 part /
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 4.6G 0 part [SWAP]
├─sda6 8:6 0 6.8G 0 part /home
└─sda7 8:7 0 122.9G 0 part /mnt/Windows
sr0 11:0 1 1024M 0 rom
bill@HP-Pavilion-dv6000:~$ sudo parted -l
Model: ATA ST9160821AS (scsi)
Disk /dev/sda: 160GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 16.0GB 16.0GB primary ext4 boot
2 16.0GB 160GB 144GB extended
5 16.0GB 20.9GB 4897MB logical linux-swap(v1)
6 20.9GB 28.1GB 7235MB logical ext4
7 28.1GB 160GB 132GB logical ntfs
bill@HP-Pavilion-dv6000:~$ cat /etc/fstab
# /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/sda1 during installation
UUID=e0447201-638f-4375-98a1-e510245bc183 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda6 during installation
UUID=283dd3a7-5d1a-4ba3-b0ae-d28d64641134 /home ext4 defaults 0 2
# /mnt/Windows was on /dev/sda7 during installation
UUID=434E2ECE41CD2A42 /mnt/Windows ntfs defaults,umask=007,gid=46 0 0
# swap was on /dev/sda5 during installation
UUID=2f0b0896-6a1f-499f-aa7f-b29882b0e3df none swap sw 0 0
-
Dear gold_finger,
Thank you for the quick verification, the only difference from this installation and mine is, I have a "sda" default HDD along with Laptop loaded with Windows and the LL is installed in a USB HDD "sdb" which i boot connected to USB port of the Laptop by setting the boot options in the BIOS to boot from USB HDD if connected.
Practically this should not create the issue I mention, if so pl let me know what is to be done and if possible can you try installing in this configuration i.e booting LL from USB HDD sdb and the laptop having a default OS of Windows
Once again Thank you for your excellent support :)
-
The difference between your setup and mine should not make any difference at all with regard to the system's ability to boot with that NTFS partition. Like I said before, my guess would be that literally hundreds of thousands of people have dual-boot (Windows - Linux) systems using NTFS (or FAT32) partitions in similar manner to what you are trying to do. I've been fairly active on Linux forums for the past couple of years and I've never seen this happen before. I've done searches to try and find others with that problem and came up empty. At this point, I'm completely stumped! I have no idea what could be wrong.
I do have an old laptop drive with Windows 7 on it that I plop into one of my laptops once a year. If I have the time, I'll put it in and hook up the other drive in an external enclosure and install LL to it. That will be an almost identical situation to yours. I'm 99.9% sure that there will be no problem booting into it. Check back in periodically over next few days -- I'll post results when I get chance to run experiment.