Project

General

Profile

Bug #2066

The Dashboard has encountered an exception!

Added by cbelldina about 4 years ago. Updated about 4 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Dashboard UI
Target version:
-
Start date:
06/04/2016
Due date:
% Done:

0%


Description

This started all of a sudden.
I have not removed any programs.
Server is still giving out DHCP, and all appears fine there.
I cannot 'see" my mapped HDA drivers in either OSx or Windows. I cannot connect.
I can SSH.
Multiple REBOOTS, no luck.

Access denied when I try to reach [root@localhost cbelldina]# /var/hda/platform/html/log/production.log
bash: /var/hda/platform/html/log/production.log: Permission denied

● hda-ctl.service - Amahi HDA controller
   Loaded: loaded (/usr/lib/systemd/system/hda-ctl.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2016-06-04 23:04:38 EDT; 39min ago
  Process: 1426 ExecStart=/usr/bin/hda-ctl $HDA_CTL_OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 1607 (hda-ctl - sleep)
   CGroup: /system.slice/hda-ctl.service
           ├─1607 hda-ctl - sleeping for 100 seconds
           └─1609 /usr/bin/perl -w /usr/bin/hda-ctl

Jun 04 23:04:30 localhost.localdomain systemd[1]: Starting Amahi HDA controll...
Jun 04 23:04:38 localhost.localdomain systemd[1]: Started Amahi HDA controller.
Hint: Some lines were ellipsized, use -l to show in full.

History

#1 Updated by cbelldina about 4 years ago

The root appears FULL. I have no idea why. As GreyHole is not a part of it.

devtmpfs                 1.8G     0  1.8G   0% /dev
tmpfs                    1.9G  4.0K  1.9G   1% /dev/shm
tmpfs                    1.9G   65M  1.8G   4% /run
tmpfs                    1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/mapper/fedora-root   50G   50G   20K 100% /
tmpfs                    1.9G   32K  1.9G   1% /tmp
/dev/sdd1                1.8T   68M  1.7T   1% /var/hda/files/drives/2TB
/dev/sdc                 1.4T  689G  617G  53% /var/hda/files/drives/drive2
/dev/sdb                 1.8T  388G  1.4T  23% /var/hda/files/drives/drive1
/dev/sda1                477M  101M  347M  23% /boot
/dev/sde                 1.8T  342G  1.4T  20% /var/hda/files/drives/drive3
/dev/mapper/fedora-home  244G  186M  244G   1% /home
none                     4.0M     0  4.0M   0% /var/spool/greyhole/mem
tmpfs                    370M     0  370M   0% /run/user/1000

#2 Updated by cpg about 4 years ago

  • Description updated (diff)
  • Status changed from New to Assigned
  • Assignee set to cpg
  • Priority changed from High to Normal

#3 Updated by cpg about 4 years ago

  • Status changed from Assigned to Feedback
  • Assignee changed from cpg to cbelldina

This, unfortunately, is that the docs do not emphasize strongly enough that the user should avoid a /home and LVM. Your system has both. Third bullet of this section:

https://wiki.amahi.org/index.php/Amahi_9_Install#Disk_Drive_Setup

So, it has a small root. The simplest way would be to reinstall. Can you do that?

#4 Updated by cbelldina about 4 years ago

If you mean reinstall such as Fedora/Amahi...I'd rather not. I do have a some data on there. Is there a plan B option?
I'm assuming my data on the various other internal drives would be ok? I'd just be starting over on the by reinstalling F23 and Amahi on that drive again, reconnect my drives/install the software again and move along?

#5 Updated by cpg about 4 years ago

It may be easier or harder depending on a number of things.

The goal: "merge the /home partition into the root partition"

1) That can be done through a live cd or similar, using gparted, or similar. Or one could do it via LVM commands, which are not trivial.

Does this seem viable with your skills, etc.?

2) Another way is to simply move some files out or root, into the big drives (or delete a few) and get the system operational. After that, avoid walloping data in larger chunks thank the size of the Landing Zone (i.e. root) and avoid touching /home, which has to be done no matter what (unless you later relocate the landing zone).

Does 1 or 2 seem more appealing?

#6 Updated by cbelldina about 4 years ago

Hmm. I'm wondering if it wouldn't be best just to (correctly this time) reinstall F23 and Amahi?

That why I can avoid the issue in the future and not have to be OCD about the large data chunks in root.....

I do have a questions, the storage drives, while I will disconnect them when re-installing, I am going to assume that Amahi will mount the drives via the disk partition manager GUI ? And while that require them to be "formatted" before use? or will Amahi just mount them and move along?

Thanks!

#7 Updated by cpg about 4 years ago

Amahi will not mount them or format them. The Disk Wizard would only do that with user direction. Never on its own.

There are some guides for merging LVM volumes that would help with just merging /home in to the root partition.

However, the landing zone is something you always have to keep in mind. If you make it large you do not have to worry about it, especially the first time you bring data in.

#8 Updated by cbelldina about 4 years ago

I've reinstalled Amahi. I made sure not to screw it up and didn't set a Home or LVM. Should be good now.

I'll reinstall the apps and move my data back over from the Cloud. I'll also set up GreyHold again.

Hopefully the Plex dashboard works, last time it took a lot of editing files to get that back up!

Thanks!

Also available in: Atom