Everything down. Can't Login.

ryecoaaron · 11. April 2016

Check the output of mount to see if it is mounted.

You must not have had any files in apt cache then. Delete some of the files you grabbed from the remote server. I don't know where you are transferring them to. I guess look in /media/ and subfolders to start?

jkingaround · 11. April 2016

i know where they're downloaded to but now they're mixed in with the mounted raid array

ryecoaaron · 11. April 2016

Unmount the array and then delete.

jkingaround · 11. April 2016

how do i do that? sorry i'm fairly unfamiliar with linux.

ryecoaaron · 11. April 2016

Post the output of: mount

jkingaround · 11. April 2016

Code

root@NAS:/media# mount


sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)


proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)


udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=985204,mode=755)


devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)


tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=789504k,mode=755)


/dev/disk/by-uuid/2d594a47-498b-486b-b7d4-c93b6d0f570d on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)


tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)


tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=4115640k)


tmpfs on /tmp type tmpfs (rw,relatime)


/dev/md127 on /media/dce7ba36-614c-4255-91c3-44630fdd8929 type xfs (rw,noexec,relatime,attr2,delaylog,sunit=1024,swidth=5120,usrquota,grpquota,_netdev)


rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)

Alles anzeigen

ryecoaaron · 11. April 2016

Try: umount -l /dev/md127
Then post output of mount again.
Have to be careful because you would delete files on the data drive if it does not unmount.

tekkb · 11. April 2016

You can get some if logs are taking up a lot of room by:
rm /var/log/*.gz

jkingaround · 11. April 2016

so it was being filled up by my cron job / lftp script. i'll figure out a way to make sure it doesn't run if it's not mounted. but for now i've turned it off in crontab. the umount fixed it and now rootfs is 3% used. I still cannot access webui, i cleared cookies and cache. tried in incognito. nothing.

Code

root@NAS:~# df -h


Filesystem                                              Size  Used Avail Use% Mounted on


rootfs                                                  282G  2.8G  265G   2% /


udev                                                     10M     0   10M   0% /dev


tmpfs                                                   771M  540K  771M   1% /run


/dev/disk/by-uuid/2d594a47-498b-486b-b7d4-c93b6d0f570d  282G  2.8G  265G   2% /


tmpfs                                                   5.0M     0  5.0M   0% /run/lock


tmpfs                                                   4.0G  4.0K  4.0G   1% /run/shm


tmpfs                                                   3.8G     0  3.8G   0% /tmp


/dev/md127                                               20T   17T  2.9T  86% /media/dce7ba36-614c-4255-91c3-44630fdd8929

Alles anzeigen

found the thread from before that allowed me to access the webui

Code

omv-mkconf omvextrasorg aptclean

. now i'm back in webui and everything is working however my RAID array shows "clean, degraded" but all the drives are listed and SMART shows no issues and i can't "recover" nothing is showing up in the dialog.

ryecoaaron · 12. April 2016

I think the other drive is bad. That is why you can recover anything.

jkingaround · 12. April 2016

Shouldn't smart be showing it as bad? Or have one less drive in the raid? How can I tell which is bad so I can replace

ryecoaaron · 12. April 2016

You are missing one drive in the array. smart isn't always the best indicator.

Look at the output of cat /proc/mdstat and compare which drives are in the output of fdisk -l. That will tell you which drive is bad. You might be able to find the serial number in physical disks tab. You can try wiping that drive and adding to the array to see if it will work.

jkingaround · 12. April 2016

took a look and all the drives listed in the cat /proc/mdstat are in the physical drives section except the OS drive.. i think it's fine

ryecoaaron · 12. April 2016

Post both of them. If there is a missing 'U' and all the drives listed in mdstat match fdisk, then you probably have a failed drive that isn't showing up.

jkingaround · 12. April 2016

Code

root@NAS:~# cat /proc/mdstat


Personalities : [raid6] [raid5] [raid4] 


md127 : active raid6 sde[9] sda[10] sdc[6] sdh[5] sdf[4] sdg[8] sdi[2] sdd[1]


      20511855616 blocks super 1.2 level 6, 512k chunk, algorithm 2 [9/8] [UUUUUUU_U]


      


unused devices: <none>


root@NAS:~# fdisk -l


Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes


255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


Disk /dev/sdc doesn't contain a valid partition table


Disk /dev/sdb: 320.1 GB, 320072933376 bytes


255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 512 bytes


I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk identifier: 0x0008a16e


   Device Boot      Start         End      Blocks   Id  System


/dev/sdb1   *        2048   599773183   299885568   83  Linux


/dev/sdb2       599775230   625141759    12683265    5  Extended


/dev/sdb5       599775232   625141759    12683264   82  Linux swap / Solaris


WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 3000.6 GB, 3000592982016 bytes


256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System


/dev/sda1               1  4294967295  2147483647+  ee  GPT


Partition 1 does not start on physical sector boundary.


Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes


255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


Disk /dev/sdd doesn't contain a valid partition table


Disk /dev/sde: 3000.6 GB, 3000592982016 bytes


255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


Disk /dev/sde doesn't contain a valid partition table


Disk /dev/sdf: 3000.6 GB, 3000592982016 bytes


255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


Disk /dev/sdf doesn't contain a valid partition table


Disk /dev/sdg: 3000.6 GB, 3000592982016 bytes


255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


Disk /dev/sdg doesn't contain a valid partition table


Disk /dev/sdh: 3000.6 GB, 3000592982016 bytes


255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


Disk /dev/sdh doesn't contain a valid partition table


Disk /dev/sdi: 3000.6 GB, 3000592982016 bytes


255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


Disk /dev/sdi doesn't contain a valid partition table


Disk /dev/md127: 21004.1 GB, 21004140150784 bytes


2 heads, 4 sectors/track, -1 cylinders, total 41023711232 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 524288 bytes / 3670016 bytes


Disk identifier: 0x00000000


Disk /dev/md127 doesn't contain a valid partition table

Alles anzeigen

ryecoaaron · 12. April 2016

Do you have 10 physical drives in your system?

jkingaround · 13. April 2016

Yes apparently. XD I forgot I had 9 drives + 1 OS drive. Time to dismantle and find the serial number missing?

ryecoaaron · 13. April 2016

I would write down the serial numbers that show up in the Physical Drives tab and the find the drive that isn't in the list. Maybe a wire or something came off? Otherwise, it has probably failed.

jkingaround · 17. April 2016

Zitat von ryecoaaron

I would write down the serial numbers that show up in the Physical Drives tab and the find the drive that isn't in the list. Maybe a wire or something came off? Otherwise, it has probably failed.

so i went through the drives missing and figured out which one it is, unplugged and replugged and it seemed to show up upon reboot. I set the RAID to recover, went about business as usual. This morning I woke up to find the RAID array missing completely! I have a pushbullet when my NAS restarts and I received one so it must have rebooted for some reason. The drive may be bad and I have a spare I can swap in. Please let me know what can I do?

ryecoaaron · 17. April 2016

Swap in the new drive and we'll go from there.

Jetzt mitmachen!