04-30-2015, 07:58 PM
On sdb, where I have tried to set up a shared DATA partition (that we are having difficulty in binding), it was formatted as ntfs on a GPT drive. I formatted in ntfs so that I could share data between both win8.1 and LL.
It has just occurred to me that as sdb carries the flag 'msftdata', as a microsoft basic data partition, it might be protected by windows from being shared or bound to My Home Directory in LL..? What do you think?
If this is the case, then changing from an ntfs to an ext4 file structure on sdb should work, but then, presumably, I wont be able to share data with win8.1.
It's worth noting that rebooting LL after a fresh install for a dual boot UEFI system also got stuck and hung indefinitely, when I ran the install so that /home and swap would go on on sdb (/ being on sda). In the end, the only UEFI win8.1/LL set up so far that has appeared to work for me is one where I exclude sdb, and have the two OSes with LL's home installed as root, all on sda. So could the msftdata flag be interfering???
Mike
It has just occurred to me that as sdb carries the flag 'msftdata', as a microsoft basic data partition, it might be protected by windows from being shared or bound to My Home Directory in LL..? What do you think?
If this is the case, then changing from an ntfs to an ext4 file structure on sdb should work, but then, presumably, I wont be able to share data with win8.1.
It's worth noting that rebooting LL after a fresh install for a dual boot UEFI system also got stuck and hung indefinitely, when I ran the install so that /home and swap would go on on sdb (/ being on sda). In the end, the only UEFI win8.1/LL set up so far that has appeared to work for me is one where I exclude sdb, and have the two OSes with LL's home installed as root, all on sda. So could the msftdata flag be interfering???
Mike
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work