shire
-
Posts
222 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by shire
-
-
5 hours ago, Frank1940 said:
If I remember correctly, on the GUI Dashboard, if you click on the 'problem' symbol, you are presented with an option to 'accept' the problem and things will go 'green' unless another CRC error occurs.
Yes..those UDMA CRC errors cause an error in the drive overwiev. I acknowledged them and they are back to normal (green).
-
I ordered those. Especially for the breakout cables we don't have a lot of choices in Germany...
-
Hello together,
to have a proper connection between harddrive and controller I would like to buy new cables. My existing red break out cables don't have metal holders/clips at the end of the cable for example.
Any recommendations? I found the following on amazon:
YIWENTEC Mini SAS 36P sff-8087 zu 4-SATA-Festplatte mit Kabel 0.5m
deleyCON 3x 50cm SATA 3 Nylon Kabel Set Datenkabel 6 Gbit/s Anschlusskabel Verbindungskabel Mainboard HDD SSD Festplatte 2 S-ATA Stecker Gerade Rot
This is in Germany (amazon).
Bye.
-
The I/O errors happened during the last reboot. I rebooted again and they did not reappear.
So...I gues I have to observe both 'problems'...
Thanks...
-
Hello,
after I replaced a drive (one with reallocated sectors) I did a rebuild. This worked without any problems. I also decided to check on the SMART status of my other drives. Two are problematic. Both have ‘UDMA CRC error counts’ in the 4xx (/sdu, /sdl). Besides that, drive /sdu wrote some errors into the logfile while rebooting.
Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907029160 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907029104 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907028176 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907028216 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 3907026080 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 32 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 120 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Aug 29 13:11:11 Tower kernel: I/O error, dev sdu, sector 264 op 0x0:(READ) flags 0x80700 phys_seg 29 prio class 2
I did an extended SMART test on both drives afterwards (passed both). Could anyone check the logfiles? I have another new drive ordered that will arrive today. I would like to decide on which one to replace next.
I will check the cabeling on both drives. I have also the complete diagnostic if needed.
Bye.
WDC_WD20EARS-60MVWB0_WD-WCAZA4043525-20230830-1012.txt WDC_WD20EARS-22MVWB0_WD-WCAZA6163992-20230830-0924.txt
-
I rebooted the server after I reseated all the drives in their drive caches.
I also use pushover on my phone to monitor the server. This drive reported reallocated sectors before the reboot.
So in other words (to understand it for the future):
- A drive reports an error (like reallocated sectors)
- unRAID sees it and takes down the drive (red indicator)
- The drive might pass the SMART test nevertheless
I found a few posts on how to reenable drives on this forum. I will skip this one and just buy a new drive...
-
Hello,
I have one red drive in my array. I did a long SMART test and it passed. Should I change it (I don't see another solution)?
Bye.
-
On 1/4/2023 at 9:33 AM, JorgeB said:
See how it goes for the next parity check.
After the parity check was finished (the one with errors) I started it again with 'Write corrections to parity' unchecked. That worked without any errors. The next parity check I activated 'Write corrections to parity" and it also finished whithout errors.
Very weird.
-
The drive passed. Hm...
-
Hello,
happened during the monthly parity check. Drive 12 is quite new.
Any ideas?
Bye.
-
7 minutes ago, SimonF said:
Are the options enabled in the management settings
HA!
A few month ago I installed unraid fresh on the usb stick. I had a unusal problem with a disk not going in standby (which was solved by reinstalling the OS).
Seems I have forgotten to activate SSH and Telnet.
Works fine now.
-
Hello,
I use the web gui for almost all my work on the server. Due to other problems (now solved) I tried to connect via SSH and Telnet to the server via putty.
I always get the message 'Network Error: Connection refused'
I deleted the SSH keys in putty (regedit). That changed nothing. I can access the server via the gui, smb in Win10 and NFS from my streaming device just fine.
Any other ideas how to solve this....?
-
1 minute ago, trurl said:
Check to see if you have a lost+found share. That is where repair would have put anything it couldn't figure out.
Everything is there:-))))
-
@trurl: Thank you for your help! You saved me a lot of pain!!
-
Hurray!
-
Phase 1 - find and verify superblock... bad primary superblock - inconsistent filesystem geometry information !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap inode pointer to 97 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary inode pointer to 98 Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... sb_icount 0, counted 1728 sb_ifree 0, counted 239 sb_fdblocks 488140152, counted 46062603 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 0 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Note - stripe unit (0) and width (0) were copied from a backup superblock. Please reset with mount -o sunit=<value>,swidth=<value> if necessary done
-
If I understand it correctly I should run:
xfs_repair /dev/md12
in maintenance mode.
The disk shows "auto" at the moment. Would that work?
-
2 hours ago, trurl said:
But you did start the rebuild? So you are rebuilding an unmountable disk. Usually we try to repair the emulated filesystem before rebuilding, but we will have to try repair after rebuild completes. Not really a big deal in this case since you are not rebuilding onto the original disk. So if there are problems with repair we can try to recover files from the original.
I startet the rebuilt, which is now done.
The array now shows this.
What should we do now?:-)
-
4 hours ago, trurl said:
But maybe not hopeless since it may be possible to read at least some of the original disk.
If you are rebuilding after formatting, you are just going to get a formatted disk from the rebuild.
I haven't used the format button.
-
Disk 12 is shown as emulated.
-
The rebulit is running:
===
UNMOUNTABLE DISK PRESENT:
DISK 12 • WDC_WD40EFZX-68AWUN0_WD-WX42D91ND945 (SDG)
Format will create a file system in all Unmountable disks.
Yes, I want to do thisPARITY-SYNC/DATA-REBUILD IN PROGRESS. Pause will pause the Parity-Sync/Data-Rebuild.
Cancel will stop Parity-Sync/Data-Rebuild.
WARNING: canceling may leave the array unprotected!===
Disk 12 is mentioned as unmountable. Will this be gone, when the rebuilt is done?
-
Old drive is back (drive1).
-
1 minute ago, trurl said:
If you are sure nothing has been written to your server since you replaced that other disk there is something we could try.
Yes. Nothing.
-
Cable for LSI9207 / SATA cable
in Storage Devices and Controllers
Posted
I use something like https://www.icydock.de/product/mb455spf_frame.html this. The cable is not directly connected to the drive itself.
The metal clip fits just fine to the HD case.
Thanks!