Announcement

Collapse
No announcement yet.

please help me fix my bricked VB

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • please help me fix my bricked VB

    Hi. could some linux experts please help me as i only have limited knowledge of linux
    I am on VB 2.3
    i can SSH into my VB as usual but it isnt coming up on the network. i tried to start samba but i cannot: this is the result i get:

    [[email protected] ~]# systemctl -l status smb
    smb.service - Samba SMB Daemon
    Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled)
    Active: failed (Result: exit-code) since Sun 2018-04-15 18:52:20 BST; 15min ago
    Process: 756 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAILURE)
    Main PID: 756 (code=exited, status=1/FAILURE)
    CGroup: /system.slice/smb.service

    Apr 15 18:52:20 vortexbox systemd[1]: smb.service: main process exited, code=exited, status=1/FAILURE
    Apr 15 18:52:20 vortexbox systemd[1]: Failed to start Samba SMB Daemon.
    Apr 15 18:52:20 vortexbox systemd[1]: Unit smb.service entered failed state.
    [[email protected] ~]# systemctl start smb
    Job for smb.service failed. See 'systemctl status smb.service' and 'journalctl -xn' for details.

    looking at some other threads i tried:

    yum clean all
    error: db5 error(28) from dbenv->open: No space left on device
    error: cannot open Packages index using db5 - No space left on device (28)
    error: cannot open Packages database in /var/lib/rpm
    CRITICAL:yum.main:

    Error: rpmdb open failed
    [[email protected] ~]# yum -y update
    error: db5 error(11) from dbenv->open: Resource temporarily unavailable
    error: cannot open Packages index using db5 - Resource temporarily unavailable (11)
    error: cannot open Packages database in /var/lib/rpm
    CRITICAL:yum.main:

    Error: rpmdb open failed

    so i cannot start samba and yum update fails. it says no space left on device, which is odd, because it had plenty of space left

    I was however, doing a backup by SSH from the command line (using a script that Ron had once shared on this thread). my backup usb drive became full during the backupand i got an error. maybe the backup has continued and has filled up some critical places on my VB?

    [[email protected] ~]# pvscan
    PV /dev/md0 VG VolGroup lvm2 [3.64 TiB / 0 free]
    PV /dev/sdc1 VG VolGroup lvm2 [1.82 TiB / 0 free]
    PV /dev/sdd VG VolGroup lvm2 [1.82 TiB / 42.81 GiB free]
    Total: 3 [7.28 TiB] / in use: 3 [7.28 TiB] / in no VG: 0 [0 ]

    [[email protected] ~]# pvdisplay
    --- Physical volume ---
    PV Name /dev/md0
    VG Name VolGroup
    PV Size 3.64 TiB / not usable 9.00 MiB
    Allocatable yes (but full)
    PE Size 32.00 MiB
    Total PE 119217
    Free PE 0
    Allocated PE 119217
    PV UUID CMUli2-Aw9t-BX8t-VAbR-vjAc-b9BU-sv31fX

    --- Physical volume ---
    PV Name /dev/sdc1
    VG Name VolGroup
    PV Size 1.82 TiB / not usable 16.09 MiB
    Allocatable yes (but full)
    PE Size 32.00 MiB
    Total PE 59616
    Free PE 0
    Allocated PE 59616
    PV UUID JMqACX-dqbO-rJX1-9klM-uYJE-ySAU-rnb009

    --- Physical volume ---
    PV Name /dev/sdd
    VG Name VolGroup
    PV Size 1.82 TiB / not usable 17.09 MiB
    Allocatable yes
    PE Size 32.00 MiB
    Total PE 59616
    Free PE 1370
    Allocated PE 58246
    PV UUID daxRJp-keZK-PcM5-6Ica-210c-9bOe-HXDbZ1

    any help much appreciated!




  • #2
    ok, so my google research reveals that i cannot get into yum (dnf on later versions) because i have totally filled up my VB and have no free space at all. i cant clean anything up easily as i cannot get into yum, so i need to delete something in order to get some space back so i can get into yum, fix my VB etc.

    so can anyone with linux experience pls walk me through how i can delete some stuff via SSH, please?

    thanks very much in advance

    Comment


    • #3
      I can't help solve the problem you've noted, but perhaps the best approach is to simply reinstall VB (maybe even 2.4) and then restore your backed up audio files after the reinstall.
      https://wiki.vortexbox.org/installation_guide

      Comment


      • #4
        Thanks Gary. Yes I appreciate that this is an option but it is 7TB of files so not a small undertaking and I would rather not do that if I can avoid it. I managed to delete a few tmp files from the command line safely, so I can now access Yum, and I have restarted the samba share (storage now visible again on my mapped drive on PC). next step is to start LMS again - I am on the latest version of LMS that was available via the GUI upgrade -7.9.1 I think. do you know what the correct terminology is -it used to be "squeezeboxserver" but that didn't work when I entered it -is it "logitechmediaserver" ?

        I still have zero space on my root "partition", if that's the correct word, so my installation is still liable to fall over again, so any Linux experts who can help me identify what filled up my root partition and delete that rubbish, would be appreciated. to recap., my installation has been rock solid for 6 years. it must have been something to do with the failed command line backup (because the USB backup drive became full) that has maxed out the root

        Comment


        • #5
          [[email protected] ~]# du -sh /*
          15G /backup
          4.0K /backupchecked 3
          32K /backupstorage
          8.0K /backup\storage\music
          4.0K /backupVinyl Rips 2
          0 /bin
          68M /boot
          0 /dev
          22M /etc
          4.0K /home
          0 /lib
          16K /lost+found
          4.0K /media
          4.0K /mnt
          3.1M /opt
          du: cannot access ‘/proc/21962/task/21962/fd/4’: No such file or directory
          du: cannot access ‘/proc/21962/task/21962/fdinfo/4’: No such file or directory
          du: cannot access ‘/proc/21962/fd/4’: No such file or directory
          du: cannot access ‘/proc/21962/fdinfo/4’: No such file or directory
          du: cannot access ‘/proc/21964’: No such file or directory
          0 /proc
          76K /root
          71M /run
          0 /sbin
          4.0K /srv
          4.9T /storage
          0 /sys
          0 /tmp
          995M /usr
          3.5G /var

          so i have a rogue 15GB in a directory called /backup in root (where there shouldnt be any backup) -so how do i remove this directory completely please?

          Comment


          • #6
            ok, i can report sucess. i deleted the rogue backup directory. if by any chance anyone using this forum in the future might be interested, this was the command
            code: rm -rf /backup
            obviously, be careful deleting folders in the root directory!!

            root is back to normal now
            [[email protected] ~]# df -h
            Filesystem Size Used Avail Use% Mounted on
            /dev/mapper/VolGroup-lv_root 20G 4.7G 14G 26% /
            devtmpfs 935M 0 935M 0% /dev
            tmpfs 942M 0 942M 0% /dev/shm
            tmpfs 942M 8.4M 933M 1% /run
            tmpfs 942M 0 942M 0% /sys/fs/cgroup
            tmpfs 942M 0 942M 0% /tmp
            /dev/sda2 477M 70M 378M 16% /boot
            /dev/mapper/VolGroup-lv_storage 7.2T 4.9T 2.0T 72% /storage


            Comment


            • #7
              tusken,
              Thanks for the update!

              I wanted to suggest you to install Midnight Commander ("yum install mc" !?) so you could easily browse your filesystem and delete something (even just one or two albums on /storage), when I realise your system is full! so installing anything would probably not work, and you mentioned there was plenty of space left on /storage.
              Glad you found your way and sorted this one.
              Strange your system froze/bricked when doing a back-up on a filled (or to small) drive, I recently tried to do a back-up on an older/smaller drive (using the Back-up button in the GUI) to found it didn't complain, but also didn't perform anything, just went from "this can take a while...." to "...finished back-up you can disconnect usb-drive"

              cheers
              /bart

              Comment


              • #8
                thanks Bart -I will install that now that I have some space in root!! because I would like a better utility to look at the filesystem. Previously, I couldn't even get into yum which made things very problematic!

                I am still looking into why this command line backup went so crazy when I have done it hundreds of times previously with no problem. FYI the reason I do manual backups is because my VB storage is so large that the backup wont fit on one USB drive, so I need to break the backup down into particular folders backed up to different USB backup drives.

                Comment

                Working...
                X