Re: [gentoo-user] Partition of 3TB USB drive not detected

2016-08-06 Thread james

On 08/06/2016 02:21 AM, Andrea Conti wrote:

Hi,


~ # parted /dev/sde print
Model: WD My Book 1230 (scsi)
Disk /dev/sde: 6001GB
Sector size (logical/physical): 4096B/4096B


[...]


AFAICS this partition works fine, fsck does not report any problem. The
funny thing is, it should not have been possible, because of the 2GB limit
of MBR.


The real limit of MBR is 2^32 sectors, which amounts to 2TB when using
512B sectors. Both your disks are using native 4kB sectors (look at the
logical sector size in the parted output), which effectively raises the
MBR limit to 16TB.

Not that this answers your question, as the Linux kernel has supported
4kB sectors for years and AFAIK it does not need any special
configuration options to do so...

andrea


It's always a good idea to check alignment on the newer disks. Here's a 
doc [1]; but it's not always clear how to ensure proper alignment. 
Supposidly the newer tools do this automation, but it's not 100%; ymmv.



[1] 
https://www.ibm.com/developerworks/linux/library/l-linux-on-4kb-sector-disks/


Many disk are hybrids of the 512/4906 sector size.



hth,
James




Re: [gentoo-user] Partition of 3TB USB drive not detected

2016-08-06 Thread Andrea Conti
Hi,

> ~ # parted /dev/sde print
> Model: WD My Book 1230 (scsi)
> Disk /dev/sde: 6001GB
> Sector size (logical/physical): 4096B/4096B

[...]

> AFAICS this partition works fine, fsck does not report any problem. The 
> funny thing is, it should not have been possible, because of the 2GB limit 
> of MBR.

The real limit of MBR is 2^32 sectors, which amounts to 2TB when using
512B sectors. Both your disks are using native 4kB sectors (look at the
logical sector size in the parted output), which effectively raises the
MBR limit to 16TB.

Not that this answers your question, as the Linux kernel has supported
4kB sectors for years and AFAIK it does not need any special
configuration options to do so...

andrea




Re: [gentoo-user] Partition of 3TB USB drive not detected

2016-08-01 Thread james

On 08/01/2016 01:45 AM, J. Roeleveld wrote:

On Sunday, July 31, 2016 03:37:55 PM Jörg Schaible wrote:

Hi,

for my backups I use a 3TB USB drive (one big ext4 partition) without any
problems. Just plug in the cable, mount it and perform the backup. The
partition (sdi1) is detected an mountable without any problems:

=== %< ==
$ ls -l /dev/disk/by-id
total 0



=== %< ==

However, when I boot a rescue system from a USB stick, the partition on the
USB is not detected. I already tried latest SystemRescueCD (default and
alternate kernel), Knoppix and the Gentoo Admin CD. Nothing, the partition
is not available.

What's the difference? Why does my kernel find this partition and the other
one's do not? It's pretty silly to have a backup drive and cannot access it
in question ;-)


Which kernel do you boot?
The systerescue-cd has 4 kernels:
2 * 64bit and 2 * 32bit.

By default, it boots the "default" one for the architecture you are booting.
Have you tried booting the "alternate" kernel?

I have 1 system that I need to boot using the "alternate" kernel as the
"default" one is too old. (Yes, by default it boots an old kernel)

It could easily be that the kernel you are using does not support your USB3
adapter or something else you used.

Eg. apart from all the 'ls' statements, also check "uname" and
"/proc/config.gz" for differences.


I was just reading about "IOMMU" and how often, if it is not "correctly 
configured" in the kernel and other places, your memory map to other 
hardwawre, like USB, can be flaky or not work at all. Fixes often 
require loading the latest bios for your motherboard. It also matters 
the 'rev' of your motherboard and other details.


I have a Gigabyte GA-990FXA-ud3 that seems to be a victim of this bug. 
No, I have not had time to ferret out this issue, so here are a few raw 
links where it is talked about::


https://www.reddit.com/r/linux/comments/4ixnyg/question_about_iommu/

https://en.wikipedia.org/wiki/Input–output_memory_management_unit

http://developer.amd.com/community/blog/2008/09/01/iommu/

http://pages.cs.wisc.edu/~basu/isca_iommu_tutorial/

https://en.wikipedia.org/wiki/List_of_IOMMU-supporting_hardware


(more posted if you ask)...


hth,
James







Re: [gentoo-user] Partition of 3TB USB drive not detected

2016-08-01 Thread J. Roeleveld
On Sunday, July 31, 2016 03:37:55 PM Jörg Schaible wrote:
> Hi,
> 
> for my backups I use a 3TB USB drive (one big ext4 partition) without any
> problems. Just plug in the cable, mount it and perform the backup. The
> partition (sdi1) is detected an mountable without any problems:
> 
> === %< ==
> $ ls -l /dev/disk/by-id
> total 0

 === %< ==
> 
> However, when I boot a rescue system from a USB stick, the partition on the
> USB is not detected. I already tried latest SystemRescueCD (default and
> alternate kernel), Knoppix and the Gentoo Admin CD. Nothing, the partition
> is not available.
> 
> What's the difference? Why does my kernel find this partition and the other
> one's do not? It's pretty silly to have a backup drive and cannot access it
> in question ;-)

Which kernel do you boot?
The systerescue-cd has 4 kernels:
2 * 64bit and 2 * 32bit.

By default, it boots the "default" one for the architecture you are booting.
Have you tried booting the "alternate" kernel?

I have 1 system that I need to boot using the "alternate" kernel as the 
"default" one is too old. (Yes, by default it boots an old kernel)

It could easily be that the kernel you are using does not support your USB3 
adapter or something else you used.

Eg. apart from all the 'ls' statements, also check "uname" and 
"/proc/config.gz" for differences.

--
Joost



Re: [gentoo-user] Partition of 3TB USB drive not detected

2016-07-31 Thread james

On 07/31/2016 08:37 AM, Jörg Schaible wrote:

Hi,

for my backups I use a 3TB USB drive (one big ext4 partition) without any
problems. Just plug in the cable, mount it and perform the backup. The
partition (sdi1) is detected an mountable without any problems:


this tells you the device is valid and working. good.


However, when I boot a rescue system from a USB stick, the partition on the
USB is not detected. I already tried latest SystemRescueCD (default and
alternate kernel), Knoppix and the Gentoo Admin CD. Nothing, the partition
is not available.


So there could be a multitude of reasons. Did thos systems have a bios 
that support booting from a usb device? Are the bios setting set to 
select the bios device correct?


I recently read somewhere the usb devices only support (2) types of 
image booting, but I cannot find that doc right now. rodsbooks is

an excellent resource for all the issues around booting and device
and various hardware/firmware issues. LikeWhoa has made booting the usb 
for gentoo, commonplace so search out those postings on the gentoo 
forums and in the wiki.




What's the difference? Why does my kernel find this partition and the other
one's do not? It's pretty silly to have a backup drive and cannot access it
in question ;-)


It could be many things. You just have to ferret thru ideas until 
something works for your hardware, and it is a frustrating process.


make sure the image you are trying to boot is on a compatible partition 
and file system that is supported by the boot image.



hth,
James






Re: [gentoo-user] Partition of 3TB USB drive not detected

2016-07-31 Thread Daniel Frey
On 07/31/2016 06:37 AM, Jörg Schaible wrote:
> Hi,
> 
> for my backups I use a 3TB USB drive (one big ext4 partition) without any 
> problems. Just plug in the cable, mount it and perform the backup. The 
> partition (sdi1) is detected an mountable without any problems:
> 
> === %< ==
> $ ls -l /dev/disk/by-id
> total 0
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 ata-
> Crucial_CT500MX200SSD1_161512468483 -> ../../sda
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 ata-
> Crucial_CT500MX200SSD1_161512468483-part1 -> ../../sda1
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 ata-
> Crucial_CT500MX200SSD1_161512468483-part2 -> ../../sda2
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 ata-
> Crucial_CT500MX200SSD1_161512468483-part3 -> ../../sda3
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 ata-HL-DT-ST_DVDRAM_GH41N_K5Q9AN32423 
> -> ../../sr0
> lrwxrwxrwx 1 root root  9 Jul 31 15:20 ata-ST3000DM001-1CH166_Z1F45VR9 -> 
> ../../sdi
> lrwxrwxrwx 1 root root 10 Jul 31 15:20 ata-ST3000DM001-1CH166_Z1F45VR9-part1 
> -> ../../sdi1
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 usb-Generic-
> _Compact_Flash_2006041309210-0:0 -> ../../sdc
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 usb-Generic-_MS_MS-
> Pro_2006041309210-0:3 -> ../../sdf
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 usb-Generic-
> _SD_MMC_2006041309210-0:2 -> ../../sde
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 usb-Generic-_SM_xD-
> Picture_2006041309210-0:1 -> ../../sdd
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 usb-Generic_Flash_HS-
> CF_26020128B005-0:0 -> ../../sdg
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 usb-Generic_Flash_HS-
> COMBO_26020128B005-0:1 -> ../../sdh
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 usb-INTENSO_USB_AA0401297518-0:0 
> -> ../../sdb
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 usb-INTENSO_USB_AA0401297518-0:0-
> part1 -> ../../sdb1
> lrwxrwxrwx 1 root root  9 Jul 31 15:20 wwn-0x5000c50065531ec5 -> ../../sdi
> lrwxrwxrwx 1 root root 10 Jul 31 15:20 wwn-0x5000c50065531ec5-part1 -> 
> ../../sdi1
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 wwn-0x50014800 -> ../../sr0
> lrwxrwxrwx 1 root root  9 Jul 31 13:17 wwn-0x500a075112468483 -> ../../sda
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 wwn-0x500a075112468483-part1 -> 
> ../../sda1
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 wwn-0x500a075112468483-part2 -> 
> ../../sda2
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 wwn-0x500a075112468483-part3 -> 
> ../../sda3
> === %< ==
> $ ls -l /dev/disk/by-label
> total 0
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 boot -> ../../sda1
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 gentoo -> ../../sda3
> lrwxrwxrwx 1 root root 10 Jul 31 15:20 intenso -> ../../sdi1
> lrwxrwxrwx 1 root root 10 Jul 31 13:17 swap -> ../../sda2
> === %< ==
> 
> However, when I boot a rescue system from a USB stick, the partition on the 
> USB is not detected. I already tried latest SystemRescueCD (default and 
> alternate kernel), Knoppix and the Gentoo Admin CD. Nothing, the partition 
> is not available.
> 
> What's the difference? Why does my kernel find this partition and the other 
> one's do not? It's pretty silly to have a backup drive and cannot access it 
> in question ;-)
> 
> - Jörg
> 
> 

I can only think of two reasons, the kernel on the livecd doesn't
support GPT (which is unlikely) or you're booting a 32-bit kernel live
USB. I am reasonably certain for drives > 2TB a 64-bit kernel and GPT
are required.

Dan