Hello! I'm new to unRaid (still in my trial)

 

I'm testing setting up and testing features. I'm building a server mostly out of spare parts and upgrading in stages. I started a server with only a single drive with only a single pool drive and everything is working well.

 

Today I installed an old SSD I had laying around as a Cache drive. Started the server and came back with SMART errors on that drive. Server became unresponsive and i had to perform a dirty shutdown. Rebooted the server, removed the SSD from the Cache. Go to write some files to a folder on the drive and I no longer have write access aparently. Check error logs and have a number of btrfs related errors on (device md1) which I think is the SSD which is no longer installed? I thought my only pool drive was at '/mnt/disk1'

 

The following is my error log:

 

Quote

May 13 13:30:08 NetStar kernel: BTRFS: error (device loop2) in btrfs_sync_log:3177: errno=-5 IO failure
May 13 13:30:08 NetStar kernel: BTRFS error (device loop2): pending csums is 24576
May 13 13:30:24 NetStar emhttpd: shcmd (1406): umount /var/lib/docker
May 13 13:30:24 NetStar kernel: BTRFS error (device loop2): cleaner transaction attach returned -30
May 13 13:30:25 NetStar emhttpd: shcmd (1419): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1
May 13 13:30:25 NetStar root: truncate: cannot open '/mnt/disk1/system/libvirt/libvirt.img' for writing: Read-only file system
May 13 13:30:25 NetStar kernel: BTRFS info (device loop2): disk space caching is enabled
May 13 13:30:25 NetStar kernel: BTRFS info (device loop2): has skinny extents
May 13 13:30:25 NetStar root: ERROR: unable to resize '/etc/libvirt': Read-only file system
May 13 13:30:25 NetStar root: Resize '/etc/libvirt' of 'max'
May 13 13:30:25 NetStar emhttpd: shcmd (1421): /etc/rc.d/rc.libvirt start
May 13 13:30:25 NetStar root: Starting virtlockd...
May 13 13:30:25 NetStar root: Starting virtlogd...
May 13 13:30:25 NetStar root: Starting libvirtd...
May 13 13:30:25 NetStar kernel: kvm: Nested Virtualization enabled
May 13 13:30:25 NetStar kernel: kvm: Nested Paging enabled
May 13 13:30:25 NetStar kernel: tun: Universal TUN/TAP device driver, 1.6
May 13 13:30:25 NetStar emhttpd: nothing to sync
May 13 13:30:25 NetStar kernel: virbr0: port 1(virbr0-nic) entered blocking state
May 13 13:30:25 NetStar kernel: virbr0: port 1(virbr0-nic) entered disabled state
May 13 13:30:25 NetStar kernel: device virbr0-nic entered promiscuous mode
May 13 13:30:25 NetStar avahi-daemon[1860]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
May 13 13:30:25 NetStar avahi-daemon[1860]: New relevant interface virbr0.IPv4 for mDNS.
May 13 13:30:25 NetStar avahi-daemon[1860]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
May 13 13:30:25 NetStar kernel: virbr0: port 1(virbr0-nic) entered blocking state
May 13 13:30:25 NetStar kernel: virbr0: port 1(virbr0-nic) entered listening state
May 13 13:30:25 NetStar dnsmasq[9447]: started, version 2.79 cachesize 150
May 13 13:30:25 NetStar dnsmasq[9447]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify
May 13 13:30:25 NetStar dnsmasq-dhcp[9447]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
May 13 13:30:25 NetStar dnsmasq-dhcp[9447]: DHCP, sockets bound exclusively to interface virbr0
May 13 13:30:25 NetStar dnsmasq[9447]: reading /etc/resolv.conf
May 13 13:30:25 NetStar dnsmasq[9447]: using nameserver 192.168.1.1#53
May 13 13:30:25 NetStar dnsmasq[9447]: read /etc/hosts - 2 addresses
May 13 13:30:25 NetStar dnsmasq[9447]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
May 13 13:30:25 NetStar dnsmasq-dhcp[9447]: read /var/lib/libvirt/dnsmasq/default.hostsfile
May 13 13:30:25 NetStar kernel: virbr0: port 1(virbr0-nic) entered disabled state

 

Any insight would be appreciated! THX.

 

 

Your post is a bit confusing. There are 2 different "pools" in Unraid. There is the parity array, which we usually refer to as "the array". And there is the cache pool. The context in which you are using the word pool makes it difficult to decide which of these you mean.

 

You shouldn't be using an SSD in the parity array anyway.

 

Device md1 and /mnt/disk1 are both referring to disk1 in the parity array.

 

The btrfs errors seem to be referring to the docker and libvirt images, which are actually virtual disks. I recommend you just disable docker and VM services until you get things a bit more stable with your disk configurations. Probably we will just have you delete and recreate those virtual disks to fix that problem.

 

17 minutes ago, Major_Marbles said:

removed the SSD from the Cache. Go to write some files to a folder on the drive and I no longer have write access

This is particularly confusing. You seem to be saying you removed a disk and then you tried to write to it.

 

Those messages in the syslog saying you can't write something have nothing to do with any files you would be writing, but they do suggest you have filesystem corruption on disk1. Probably disk1 isn't btrfs (not the default for the array) and as I said those message are referring to vdisks, which seem to be on disk1 (but need to be recreated on cache).

 

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post. Maybe that will help clarify things.