smakovits
-
Posts
881 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by smakovits
-
-
Hmm. Wonder if that's also why I have been seeing my log partition filling up then. Seems to only make sense as I wouldn't expect it otherwise.
In the past I just ran the command to increase it to 256mb. Guess maybe it got sick of throwing errors and started breaking so I took a closer look.
Good news is the drive replacement yields an extra tb of storage.
Thanks.
If it does it again, I'll report it Beck here.
Sent from my Nexus 6P using Tapatalk
-
yes, I do. Do you suspect this as the culprit then or just something you saw?
in the mean time, I am shutting down and replacing the disk
-
@itimpi
I wanted to point you to a new thread I started which is a little more precise to my issue as it happened again...
-
Last week I was messing with my cache drive when things got all out of whack. My shares all vanished and things were not right till I rebooted. However, because I was messing with my docker config folder on the cache drive only, I thought the issue was with the cache drive causing the entire array and its shares to stop sharing. At the time I replaced the cache drive, rebooted and got going again.
Until last night that is, when I was creating a new folder on one of my shares. I was using my windows 10 computer, created new folder, but when I tried to rename it, windows reported I needed permissions to do so. I then tried going to one of my other shares when it started to prompt for credentials. This was the same behavior as last week and suddenly I knew.
I pulled down the diagnostics and rebooted, at which time order was restored. However, this is two weeks in a row that my shares simply stopped sharing, forcing me to reboot.
One thing to note is that I could access the individual disks fine still, it what just the share themselves that were suddenly broken.
The diagnostic file is within 5-10 minutes of noticing what was going on.
-
just tried again with libreelec, same result, no bitstream passthrough support with 6450.
Either I hope kodi adds support soon or just drop $$ for a new card
-
I wasn't worried about seeing it in the gui, just trying not to confuse myself with it in 2 places.
Sent from my Nexus 6P using Tapatalk
-
Sweet, that seems to have worked.
So, maybe I was being stupid. Can I not have a folder on my cache drive that is not shared? Or would it just need to be hidden?
I ask because that explains why after rebooting I have a share for appdata again under /mnt/user/"appdata"
Or, instead of smb share setting being no, make it yes, hidden? I mean I don't need it to be a share at all, but whatever.
My goal was to simply have it as a folder on my cache drive only and not share it. If I wanted to access it, I could get to it via my cache drive.
Sent from my Nexus 6P using Tapatalk
-
OK, I will try. I was holding off nervous that it could blow up all my data... Since there are no shares, I was thinking it might try deleting everything...
Sent from my Nexus 6P using Tapatalk
-
Global Share Settings? Shares Enabled?
enable disk shares: yes
enable user shares: yes
-
It might also be worth noting that all of my share config files still exist, so it's puzzling as to why they would not be there.
Is it worth trying a reboot?
Sent from my Nexus 6P using Tapatalk
-
No, I see cache, flash and all my disks only
Sent from my Nexus 6P using Tapatalk
-
It is not at all clear from your description exactly what you did?
I would suggest that you post the diagnostics file (Tools->Diagnostics) so that we can see more information on how things are currently set up on your system.
I had a share, appdata, set to cache drive only.
under smb security I selected export, no, clicked apply
thats all i did and it took all my shares with it
-
Apr 11 23:32:53 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'Beets' Apr 11 23:32:53 Tower kernel: device veth9a603a0 entered promiscuous mode Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered forwarding state Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered forwarding state Apr 11 23:32:53 Tower avahi-daemon[23433]: Withdrawing workstation service for veth44442f9. Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered disabled state Apr 11 23:32:53 Tower kernel: eth0: renamed from veth44442f9 Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered forwarding state Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered forwarding state Apr 11 23:32:53 Tower kernel: veth44442f9: renamed from eth0 Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered disabled state Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered disabled state Apr 11 23:32:53 Tower avahi-daemon[23433]: Withdrawing workstation service for veth44442f9. Apr 11 23:32:53 Tower avahi-daemon[23433]: Withdrawing workstation service for veth9a603a0. Apr 11 23:32:53 Tower kernel: device veth9a603a0 left promiscuous mode Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered disabled state Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Documents Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/ISOs Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Music Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Pictures Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Software Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Video Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Documents Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/ISOs Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Music Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Pictures Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Software Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Video Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Documents Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/ISOs Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Music Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Pictures Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Software Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Video Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 11 23:33:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:33:09 Tower emhttp: shcmd (224): :>/etc/samba/smb-shares.conf Apr 11 23:33:09 Tower emhttp: shcmd (225): cp /etc/exports- /etc/exports Apr 11 23:33:09 Tower avahi-daemon[23433]: Files changed, reloading. Apr 11 23:33:09 Tower emhttp: Restart SMB... Apr 11 23:33:09 Tower emhttp: shcmd (226): killall -HUP smbd Apr 11 23:33:09 Tower emhttp: shcmd (227): smbcontrol smbd close-share 'appdata' Apr 11 23:33:09 Tower emhttp: shcmd (228): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Apr 11 23:33:09 Tower avahi-daemon[23433]: Files changed, reloading. Apr 11 23:33:09 Tower avahi-daemon[23433]: Service group file /services/smb.service changed, reloading. Apr 11 23:33:09 Tower emhttp: shcmd (229): pidof rpc.mountd &> /dev/null Apr 11 23:33:09 Tower emhttp: Restart NFS... Apr 11 23:33:09 Tower emhttp: shcmd (230): exportfs -ra |& logger Apr 11 23:33:09 Tower emhttp: shcmd (231): /etc/rc.d/rc.atalk status Apr 11 23:33:10 Tower avahi-daemon[23433]: Service "Tower" (/services/smb.service) successfully established. Apr 11 23:34:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:35:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:35:50 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'Beets' Apr 11 23:35:50 Tower kernel: device veth17705c5 entered promiscuous mode Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower avahi-daemon[23433]: Withdrawing workstation service for veth0a7411e. Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:50 Tower kernel: eth0: renamed from veth0a7411e Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:50 Tower kernel: veth0a7411e: renamed from eth0 Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:50 Tower avahi-daemon[23433]: Withdrawing workstation service for veth0a7411e. Apr 11 23:35:50 Tower avahi-daemon[23433]: Withdrawing workstation service for veth17705c5. Apr 11 23:35:50 Tower kernel: device veth17705c5 left promiscuous mode Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:56 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f Beets Apr 11 23:36:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:36:31 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'Beets' Apr 11 23:36:31 Tower kernel: device veth3218716 entered promiscuous mode Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered forwarding state Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered forwarding state Apr 11 23:36:31 Tower avahi-daemon[23433]: Withdrawing workstation service for veth4987bee. Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered disabled state Apr 11 23:36:31 Tower kernel: eth0: renamed from veth4987bee Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered forwarding state Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered forwarding state Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered disabled state Apr 11 23:36:31 Tower kernel: veth4987bee: renamed from eth0 Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered disabled state Apr 11 23:36:31 Tower avahi-daemon[23433]: Withdrawing workstation service for veth4987bee. Apr 11 23:36:31 Tower avahi-daemon[23433]: Withdrawing workstation service for veth3218716. Apr 11 23:36:31 Tower kernel: device veth3218716 left promiscuous mode Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered disabled state Apr 11 23:36:34 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f Beets Apr 11 23:36:52 Tower kernel: device vethc50a332 entered promiscuous mode Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered forwarding state Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered forwarding state Apr 11 23:36:52 Tower avahi-daemon[23433]: Withdrawing workstation service for veth9c048c9. Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered disabled state Apr 11 23:36:52 Tower kernel: eth0: renamed from veth9c048c9 Apr 11 23:36:52 Tower kernel: veth9c048c9: renamed from eth0 Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered forwarding state Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered forwarding state Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered disabled state Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered disabled state Apr 11 23:36:52 Tower avahi-daemon[23433]: Withdrawing workstation service for veth9c048c9. Apr 11 23:36:52 Tower avahi-daemon[23433]: Withdrawing workstation service for vethc50a332. Apr 11 23:36:52 Tower kernel: device vethc50a332 left promiscuous mode Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered disabled state Apr 11 23:37:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:37:14 Tower kernel: mdcmd (108): nocheck Apr 11 23:37:14 Tower kernel: md: nocheck_array: check not active Apr 11 23:37:14 Tower cache_dirs: Stopping cache_dirs process 24473
-
I had a share/folder on my cache drive that I didnt think I needed shared any more, so I set SMB share off.
I figure I can get to the folder via the cache share already, so to avoid confussion I wanted to hide it by stopping the share. All dockers accessed it via /mnt/cache/appdata
so having an appdata share was not really needed.
however, upon doing so, all my shares when with it. I still see my folders on the drives and the share config files, so not sure what happened. I have stopped the array and started it, but no luck. the only thing I have not tried is a reboot, but I am not sure if that is needed. I an certainly a bit nervous as things have been rock solid for year and now the last week I have been dealing with issues. first my cache drive appeared to go read only taking my containers with it. and now upong replacing the drive and getting things back up, I have now lost all my shares. Data appears ok, but still. what give.
I am hoping this is an easy fix.
-
scrub status for 1b60e5b1-39f5-4a77-a870-be87c2216efe
scrub started at Sat Apr 9 13:53:12 2016 and finished after 00:18:54
total bytes scrubbed: 67.45GiB with 0 errors
-
1 Raw read error rate 0x000b 200 200 051 Pre-fail Always Never 0
3 Spin up time 0x0007 169 165 021 Pre-fail Always Never 4550
4 Start stop count 0x0032 096 096 040 Old age Always Never 4179
5 Reallocated sector count 0x0033 199 199 140 Pre-fail Always Never 3
7 Seek error rate 0x000a 200 200 051 Old age Always Never 0
9 Power on hours 0x0032 038 038 000 Old age Always Never 45948 (5y, 2m, 28d, 12h)
10 Spin retry count 0x0012 100 100 051 Old age Always Never 0
11 Calibration retry count 0x0012 100 100 051 Old age Always Never 0
12 Power cycle count 0x0032 100 100 000 Old age Always Never 225
194 Temperature celsius 0x0022 126 096 000 Old age Always Never 21
196 Reallocated event count 0x0032 198 198 000 Old age Always Never 2
197 Current pending sector 0x0012 200 200 000 Old age Always Never 0
198 Offline uncorrectable 0x0012 200 200 000 Old age Always Never 0
199 UDMA CRC error count 0x000a 200 253 000 Old age Always Never 1
200 Multi zone error rate 0x0008 200 200 051 Old age Offline Never 0
Done
-
unRAID will set a disk as read-only if any sort of file system corruption is detected.It is my cache disk yes. It houses my docker img. It seems is gone read only and so all dockers luck up. Question being why is it going read only.
I pulled it, added it to another system and ran the WD QUICK test and it checked OK. Added to a Linux system and it reads fine and can write to it too.
So it's it bad or what? Why is unRAID making it read only. It did it Thursday so I rebooted and it worked, but by the end of Friday it read only again.
Sent from my Nexus 6P using Tapatalk
You should put the array into Maintenance mode, and then click on the cache disk to run a file system check on it.
I put the disk back. how do I run said test? I see stuff for smart test, but not file system check, unless of course my eyes are playing games
seems I do not see it because cache is formatted btrfs.
can this be changed?
-
unRAID will set a disk as read-only if any sort of file system corruption is detected.It is my cache disk yes. It houses my docker img. It seems is gone read only and so all dockers luck up. Question being why is it going read only.
I pulled it, added it to another system and ran the WD QUICK test and it checked OK. Added to a Linux system and it reads fine and can write to it too.
So it's it bad or what? Why is unRAID making it read only. It did it Thursday so I rebooted and it worked, but by the end of Friday it read only again.
Sent from my Nexus 6P using Tapatalk
You should put the array into Maintenance mode, and then click on the cache disk to run a file system check on it.
I put the disk back. how do I run said test? I see stuff for smart test, but not file system check, unless of course my eyes are playing games
-
OK. I was going to just replace it actually, but it has all my docker configs so I need to get those off somehow first.
Because of the permissions, it isn't as simple as mount in new system cut and paste.
May mount it usb as unassigned and see if I can get it off. Or, pull new drive, add back, copy off.
Then Maintenance check maybe?
Sent from my Nexus 6P using Tapatalk
-
It is my cache disk yes. It houses my docker img. It seems is gone read only and so all dockers luck up. Question being why is it going read only.
I pulled it, added it to another system and ran the WD QUICK test and it checked OK. Added to a Linux system and it reads fine and can write to it too.
So it's it bad or what? Why is unRAID making it read only. It did it Thursday so I rebooted and it worked, but by the end of Friday it read only again.
Sent from my Nexus 6P using Tapatalk
-
I was starting to notice an issue with my docker containers. the question is, is the issue my cache disk or my docker img file?
Apr 8 23:15:05 Tower kernel: btrfs_dev_stat_print_on_error: 319324 callbacks suppressed Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246343, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#17 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246344, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#18 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246345, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#19 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246346, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#20 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246347, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#21 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246348, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#22 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246349, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#23 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246350, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#24 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246351, flush 0, corrupt 0, gen 0 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 8 23:15:05 Tower kernel: sd 4:0:0:0: [sdd] tag#25 CDB: opcode=0x28 28 00 10 ab 34 e0 00 00 20 00 Apr 8 23:15:05 Tower kernel: blk_update_request: I/O error, dev sdd, sector 279655648 Apr 8 23:15:05 Tower kernel: BTRFS: bdev /dev/sdd1 errs: wr 120, rd 251246352, flush 0, corrupt 0, gen 0
-
It would seem I did something wrong.
I. Say this because I got it to work now..
When it wasn't working, I only had a drive name. Call it "ud". So last night I Remounted, and gave it a new name. Except, instead of "ud" I made. It /mnt/ud.
As soon as I hit enter, it became /mnt/disks/ud and I could see this as a path when adding a vm.
When I did it before, I saw "disks" as selectable, but that's it. Now it's /mnt/disks/ud and I see the disk usage growing.
So not sure why, but it definitely wants /mnt/name on the main page when naming the unassigned device
-
So I finally got to playing with this and something is off.
I see my main disk. I format a participant share it. Call it "unassigned"
In Windows, I see \\tower\unassigned, but it does not appear in /mnt/disks
Instead, I see it at /unassigned, in the root, same place as /mnt, etc
I made a vm in /mnt/disks/Libreelec/vdisk.img, it starts and works, but I cannot find do this img anywhere. Not in unassigned, cache, anywhere. Ls -la, nothing, so it doesn't appear hidden. But where is it. I checked the flash, nothing anywhere.
So yeah. Something is off with all of this. But I can't figure it out. What does your unassigned disk section look like under unassigned disk on the main tab. Is it disk then share? Or. Just the disk?
-
why not try PKC instead of plexbmc, its beta but a much better solution
How to install OpenELEC (Official) in a VM
in VM Templates
Posted
so you guys bitstreaming to work now with the latest libreelec and the radeon cards? I installed pre-final the other day and bitstreaming still was not working.