February 11, 201511 yr I'm having multiple issues here. First is two red balls with missing disks and an invalid configuration. Next is getting a zero byte file when I try to create a syslog. What am I doing wrong? After I get a syslog, we can tackle the first problem! Running v.5.0.6 Thank you! Dave
February 11, 201511 yr Author I'm having multiple issues here. First is two red balls with missing disks and an invalid configuration. Next is getting a zero byte file when I try to create a syslog. What am I doing wrong? After I get a syslog, we can tackle the first problem! Running v.5.0.6 Thank you! Dave First I tried this command via Telnet: cp /var/log/syslog /boot That created a zero byte log Then I tried going to utils and creating the log from there, but the window that popped up has shown "transferring data from tower..." for about 30 minutes now.
February 11, 201511 yr Author Put your flash drive in your PC and let it do checkdisk. I ran chkdsk and there are no issues with the flash drive. 766MB available and no problem with the file system.
February 11, 201511 yr Author I'm having multiple issues here. First is two red balls with missing disks and an invalid configuration. Running v.5.0.6 Thank you! Dave Ok, I rebooted and was able to get a syslog. See attached. Before I rebooted, Disks 3 & 8 were missing. After reboot, all were green and the configuration was valid. I then started a parity check and almost immediately Disk 13 went red and the check stopped. This is getting weird! Thanks for any advice you can offer. Dave syslog.zip
February 11, 201511 yr I see some things in that syslog that I would comment on, but since it has timestamps from September I assume it would be pointless. Try again.
February 11, 201511 yr Author >>>I see some things in that syslog that I would comment on, but since it has timestamps from September I assume it would be pointless. Try again.<<< Would the syslog report back to September, even though it was just generated after a reboot yesterday? I assumed that the syslog would only go back to the last reboot.
February 11, 201511 yr >>>I see some things in that syslog that I would comment on, but since it has timestamps from September I assume it would be pointless. Try again.<<< Would the syslog report back to September, even though it was just generated after a reboot yesterday? I assumed that the syslog would only go back to the last reboot. It does - which suggest the file that was attached is not the correct syslog.
February 11, 201511 yr Author I realized that was probably what happened as soon as I hit send. My bad! Will post the right file tonight.
February 12, 201511 yr Author >>>I see some things in that syslog that I would comment on, but since it has timestamps from September I assume it would be pointless. Try again.<<< Would the syslog report back to September, even though it was just generated after a reboot yesterday? I assumed that the syslog would only go back to the last reboot. It does - which suggest the file that was attached is not the correct syslog. Turns out that was the right file! My clock and calendar must need to be updated. I run the machine headless and had never noticed that it was way off. So the syslog that I posted does reflect the current situation. Thank you!
February 12, 201511 yr Maybe your CMOS battery is dead and it won't keep time. Sep 25 23:56:30 Tower kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. This is sometimes a false alarm, but unRAID thinks your flash may be corrupt. Sep 25 23:56:30 Tower logger: Installing system plugins Sep 25 23:56:30 Tower logger: installing plugin: webGui-latest Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Document is empty in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Start tag expected, '<' not found in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: xml parse error I wouldn't be surprised if this isn't also a zero byte file. Either that or a bad download or corrupted plg file. The zero byte syslog you mentioned earlier is the reason I had you check your flash drive. Lots of read and write errors on disk 13. Since disk 13 had a write error it was taken off line, which is why it is red. Check all cables and connectors at both ends and get a smart report of disk 13.
February 13, 201511 yr Author Maybe your CMOS battery is dead and it won't keep time. Sep 25 23:56:30 Tower kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. This is sometimes a false alarm, but unRAID thinks your flash may be corrupt. Sep 25 23:56:30 Tower logger: Installing system plugins Sep 25 23:56:30 Tower logger: installing plugin: webGui-latest Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Document is empty in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Start tag expected, '<' not found in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: xml parse error I wouldn't be surprised if this isn't also a zero byte file. Either that or a bad download or corrupted plg file. The zero byte syslog you mentioned earlier is the reason I had you check your flash drive. Lots of read and write errors on disk 13. Since disk 13 had a write error it was taken off line, which is why it is red. Check all cables and connectors at both ends and get a smart report of disk 13. I've attached four smart reports. Disk 13 is the one which currently has a red ball, but previously Disks 3 and 8 both went red, and Disk 10 just before that. I ran a short smart test on all four and then ran the reports. I'll check the flash and see what I can find. Thank you! smart13.txt smart03.txt smart08.txt smart10.txt
February 13, 201511 yr Author Maybe your CMOS battery is dead and it won't keep time. Sep 25 23:56:30 Tower kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. This is sometimes a false alarm, but unRAID thinks your flash may be corrupt. Sep 25 23:56:30 Tower logger: Installing system plugins Sep 25 23:56:30 Tower logger: installing plugin: webGui-latest Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Document is empty in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): /boot/plugins/webGui-latest.plg:1: parser error : Start tag expected, '<' not found in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: Sep 25 23:56:30 Tower logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Sep 25 23:56:30 Tower logger: xml parse error I wouldn't be surprised if this isn't also a zero byte file. Either that or a bad download or corrupted plg file. The zero byte syslog you mentioned earlier is the reason I had you check your flash drive. Lots of read and write errors on disk 13. Since disk 13 had a write error it was taken off line, which is why it is red. Check all cables and connectors at both ends and get a smart report of disk 13. And yes, you're exactly right that webGui-latest.plg is zero byte. Would the Upgrade webGui utility fix that?
February 13, 201511 yr Author Maybe your CMOS battery is dead and it won't keep time. Sep 25 23:56:30 Tower kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. This is sometimes a false alarm, but unRAID thinks your flash may be corrupt. [/quote] Testdisk shows a bad sector count on the flash drive. Should I repair that with testdisk? Sorry for being so helpless, but I'd rather go slowly and ask along the way than mess something up.
February 13, 201511 yr Maybe your CMOS battery is dead and it won't keep time. Sep 25 23:56:30 Tower kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. This is sometimes a false alarm, but unRAID thinks your flash may be corrupt. Testdisk shows a bad sector count on the flash drive. Should I repair that with testdisk? Sorry for being so helpless, but I'd rather go slowly and ask along the way than mess something up. Yes to repair flash. Disk 10 smart report is the one that looks worrisome. But you can't do anything about that while disk 13 is red. What did you find out about your cables and connections when you checked them? Do you have locking SATA cables? Any reason something might have come loose?
February 13, 201511 yr Author Maybe your CMOS battery is dead and it won't keep time. Sep 25 23:56:30 Tower kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. This is sometimes a false alarm, but unRAID thinks your flash may be corrupt. Testdisk shows a bad sector count on the flash drive. Should I repair that with testdisk? Sorry for being so helpless, but I'd rather go slowly and ask along the way than mess something up. Yes to repair flash. Disk 10 smart report is the one that looks worrisome. But you can't do anything about that while disk 13 is red. What did you find out about your cables and connections when you checked them? Do you have locking SATA cables? Any reason something might have come loose? I've been through the server and checked every cable connection -- no issues that I could find. I did move across the country about six months ago, but I'd have thought that anything that was going to come loose would have shown up months ago. I'll repair the flash and reboot. I'll repair the flash drive
February 13, 201511 yr ... I did move across the country about six months ago, but I'd have thought that anything that was going to come loose would have shown up months ago ... Did you remove the disks and pack them separately? If you shipped them in hot-swap cages, the weight of the disks and any vibrations during the move may very well have caused microscopic fractures on the PCB's and/or the plug-in connectors. There have been several issues caused by doing this on other threads in this forum ... the most recent on a system that was shipped overseas to Germany where the user ended up replacing all 3 of his hot-swap cages because of these issues.
February 13, 201511 yr Author ... I did move across the country about six months ago, but I'd have thought that anything that was going to come loose would have shown up months ago ... Did you remove the disks and pack them separately? If you shipped them in hot-swap cages, the weight of the disks and any vibrations during the move may very well have caused microscopic fractures on the PCB's and/or the plug-in connectors. There have been several issues caused by doing this on other threads in this forum ... the most recent on a system that was shipped overseas to Germany where the user ended up replacing all 3 of his hot-swap cages because of these issues. Nope! Just left everything mounted as it was, packed it well and made the move. I'd moved the same box from Singapore to Texas a few years ago without incident, but maybe I wasn't so lucky this time.
February 13, 201511 yr Author Now I'm afraid the flash drive is toast. I stopped and restarted the array. No red balls. Parity sync started and no errors showing, but showing 4 billion reads and 17 billion writes on the flash.
February 13, 201511 yr The drives add a significant amount of weight and can cause a lot of stress on the chassis during shipment. This isn't a big deal if they are individually cabled -- it's easy to simply unplug/replug all the cables to ensure they are still securely seated after shipment; but if they're in hot-swap cages it is definitely NOT a good idea to ship them in the case. I always pack and ship the disk drives separately -- very well wrapped and securely cushioned in their own box.
Archived
This topic is now archived and is closed to further replies.