Issues with adding a 3TB USB Drive to Amahi (and greyhole)

[PatrickDickey]

Hi everyone,

I purchased a 3TB Seagate USB drive for my server, and tried adding it in. At first, I had a couple of lines in my /etc/fstab commented out, because they were drives that I wasn't using/weren't working properly. When I ran the hda-diskmount script, it replied that the drive was already in /etc/fstab with no UUID and was commented out. So I removed the commented lines altogether and re-ran it.

Now the results are:

Code: Select all

**************************************************************** Ignoring /dev/sdc1 - already in /etc/fstab as UUID= ****************************************************************

Here's my /etc/fstab

Code: Select all

[root@localhost tripwire]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Sun Sep 29 13:51:49 2013 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/hda-root / ext4 defaults 1 1 UUID=41bbae2f-7461-402c-9827-9c09dc34db73 /boot ext4 defaults 1 2 /dev/mapper/hda-home /home ext4 defaults 1 2 /dev/mapper/hda-swap swap swap defaults 0 0 UUID=5daf66e3-61f2-438e-a288-a218c922434e /var/hda/files/drives/drive1 ext4 defaults 1 2 UUID=ee6b982e-4a79-47af-a2e9-d408591c8935 /var/hda/files/drives/drive2 ext4 defaults 1 2 UUID=561975f5-db29-4f89-981c-3c110c64cddd /var/hda/files/drives/drive4 ext4 defaults 1 2 UUID=b6557d0e-9433-41cf-be24-cd40eddac1f8 /var/hda/files/drives/drive5 ext4 defaults 1 2 UUID=f30859b4-6f6d-41d2-aa80-a6afea739f65 /var/hda/files/drives/drive6 ext4 defaults 1 2

And the results of ls -l /dev/disk/by-uuid

Code: Select all

[root@localhost tripwire]# ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 10 Oct 22 20:31 172a8d6f-9273-4e4e-972c-1603d0a59296 -> ../../dm-1 lrwxrwxrwx 1 root root 9 Oct 22 20:31 2011-02-17-17-10-30-00 -> ../../sr1 lrwxrwxrwx 1 root root 10 Oct 22 20:31 41bbae2f-7461-402c-9827-9c09dc34db73 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 22 20:31 51aeb7d6-e19e-4b33-9bec-22130c4fb484 -> ../../dm-0 lrwxrwxrwx 1 root root 10 Oct 22 20:31 561975f5-db29-4f89-981c-3c110c64cddd -> ../../sde1 lrwxrwxrwx 1 root root 10 Oct 22 20:31 5daf66e3-61f2-438e-a288-a218c922434e -> ../../sdb1 lrwxrwxrwx 1 root root 10 Oct 22 20:31 7b4e7bbf-de85-4144-a49e-4a8c73e7f0f9 -> ../../dm-2 lrwxrwxrwx 1 root root 10 Oct 22 20:31 a9603d9e-9a60-4d50-a182-dabd1da0217f -> ../../sda3 lrwxrwxrwx 1 root root 10 Oct 23 14:27 b6557d0e-9433-41cf-be24-cd40eddac1f8 -> ../../sdh1 lrwxrwxrwx 1 root root 10 Oct 23 13:27 ee6b982e-4a79-47af-a2e9-d408591c8935 -> ../../sdi1 lrwxrwxrwx 1 root root 10 Oct 22 20:31 f30859b4-6f6d-41d2-aa80-a6afea739f65 -> ../../sdg1

I formatted it on Ubuntu using GParted using the defaults for ext4. And per the wiki, I changed the hda-diskmount script on the line for driveext=. (the only change was adding a "w" to the egrep -i command, as it wasn't there).

Trying to manually mount the drive to /media gives me this (along with dmesg | tail)

Code: Select all

[root@localhost media]# mount /dev/sdc /media mount: /dev/sdc is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. [root@localhost media]# dmesg | tail [75383.110076] usb 1-3: reset high-speed USB device number 21 using ehci-pci [75416.106088] usb 1-3: reset high-speed USB device number 21 using ehci-pci [75448.104058] usb 1-3: reset high-speed USB device number 21 using ehci-pci [75486.118081] usb 1-3: reset high-speed USB device number 21 using ehci-pci [75521.110073] usb 1-3: reset high-speed USB device number 21 using ehci-pci [75557.110050] usb 1-3: reset high-speed USB device number 21 using ehci-pci [75590.106059] usb 1-3: reset high-speed USB device number 21 using ehci-pci [75622.104061] usb 1-3: reset high-speed USB device number 21 using ehci-pci [75639.356746] grow_buffers: requested out-of-range block 18446744071562067968 for device sdc [75639.356763] isofs_fill_super: bread failed, dev=sdc, iso_blknum=17, block=-2147483648

Also here's the relevant portion of fdisk -l

Code: Select all

Disk /dev/sdc: 3000.6 GB, 3000592977920 bytes, 732566645 sectors Units = sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: dos Disk identifier: 0x00021365 Device Boot Start End Blocks Id System /dev/sdc1 63 3906963455 2742951684 83 Linux

I can log in on a desktop and re-run GParted if necessary, but I was hoping that there's an easy fix to this problem. I'm at a loss, and I'm getting drive full and other errors with my other drives (which makes me wonder if this isn't a problem with my USB card/ports).

Thanks for any help in getting this drive working, and have a great day.
Patrick.

P.S. As far as following the wiki guide on adding a 3TB drive, I only did the changes recommended on the forum post as I had already formatted the drive, and it shows it as a 3TB drive in fdisk.

[bigfoot65]

Not sure how accurate the wiki guidance is for Amahi 7. Might try formatting the drive using the guidance in the wiki vs gParted. I used cfdisk in the past to create the partition and then

Code: Select all

mkfs.ext4 -j /dev/sdc

Whenever I used gParted, I had problems. This was with 2TB drives but could be related. Just a thought.

[PatrickDickey]

Not sure how accurate the wiki guidance is for Amahi 7. Might try formatting the drive using the guidance in the wiki vs gParted. I used cfdisk in the past to create the partition and then

Code: Select all

mkfs.ext4 -j /dev/sdc

Whenever I used gParted, I had problems. This was with 2TB drives but could be related. Just a thought.

Well that solved most of the problems. Now I have to manually configure greyhole to use the drive. I'll have to dig into that tomorrow, as I'm off to work shortly. Is there anything on the wiki about configuring greyhole manually by chance? Or is getting greyhole tied into the webpage, so we can configure it via the Setup tab in the works?

Have a great day.
Patrick.

[bigfoot65]

There is some guidance in the wiki about Greyhole. Nothing to tie it into the dashboard yet, but it's on the todo list. Sorry, but no estimate on when it will be done.

[PatrickDickey]

There is some guidance in the wiki about Greyhole. Nothing to tie it into the dashboard yet, but it's on the todo list. Sorry, but no estimate on when it will be done.

Just out of curiosity, did the code behind the dashboard change so much that it couldn't just be added in from the previous version (Amahi 6.x, I mean)?

Have a great day. and thanks again.
Patrick.

[bigfoot65]

Yes it did change drastically, otherwise we would have added it back already. When it's done, it will be a plug-in vs hard coded as before. That is one of the big changes with Amahi 7 is the ability to add plug-ins for things such as this.