-
Disk failure or not?
Thank you for your input. I will check that for sure. I will put my new 4tb as a second parity drive so that way, I will be more protected if a disk fail.
-
Disk failure or not?
So i thought my disk was dead, I decided to plug it to my Windows pc and run a disk repair on it. It have correct some bad sectors or something like that. I then plugged it back to unraid (not in the array) and run a short and long smart test. They both passed! So the solution was to repair the disk (I used Hard Disk Sentinel) and change the cable. Now the big question is: can I put it back in the array? I have attached the SMART test result if someone can help me understand it. WDC_WD30EZRZ-00WN9B0_WD-WCC4E0DDCNT6-20250522-2132.txt
-
Disk failure or not?
I've changed the disk but also the cable. He was causing some problems too. Everything works good now. If the cable did corrupt the disk, can it be saved or he is fully dead now?
-
Disk failure or not?
Hi everyone! I seems to have a problem with one of my disk when I check the SMART report: Error: UNC at LBA = 0x09736a70 = 158558832 READ FPDMA QUEUED Do I need to buy a new disk or can I do something and save it? Thank you for your help! WDC_WD30EZRZ-00WN9B0_WD-WCC4E0DDCNT6-20250430-0752.txt tower-diagnostics-20250430-0803.zip
-
error: shfs_mk_share, 6450: No space left on device (28)
I've put 50GB and it solve the problem but I don't understand why. All my shared are set to 0 and it worked but maybe I had more space at that time. What is the purpose of this setting? It's to be sure that there's always a space available to this folder?
-
error: shfs_mk_share, 6450: No space left on device (28)
Hi everyone! I wanted to create a new share on my array but it doesn't work. The error doesn't show on the UI but if I check the log, I see "emhttpd: error: shfs_mk_share, 6450: No space left on device (28): ioctl: /NewFolder". I tried to restart the array, reboot the server but without any success. I have enough space on my array and also on my USB key so I don't know how to solve it. I have attached the diagnostic file. Thank you for your help! tower-diagnostics-20230830-1214.zip
-
Problem with an Unmountable: Unsupported partition layout disk
Just wanted to say that everything is back to normal now. Thank you again for all the support!
-
Problem with an Unmountable: Unsupported partition layout disk
The disk is now in the rebuilding process. By curiosity, what kind on information you where searching in the my diagnostics file? Thank you all for your help!
-
Problem with an Unmountable: Unsupported partition layout disk
Here's the new diagnostics tower-diagnostics-20220804-2252.zip
-
Problem with an Unmountable: Unsupported partition layout disk
-
Problem with an Unmountable: Unsupported partition layout disk
I've done the filesystem check without the -n switch but no luck, the disk is still in "invalid partition layout" state. Here's the result: Phase 1 - find and verify superblock... - block cache size set to 148496 entries Phase 2 - using internal log - zero log... zero_log: head block 2270027 tail block 2270027 - scan filesystem freespace and inode maps... - 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 = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Thu Aug 4 17:42:27 2022 Phase Start End Duration Phase 1: 08/04 17:42:04 08/04 17:42:13 9 seconds Phase 2: 08/04 17:42:13 08/04 17:42:14 1 second Phase 3: 08/04 17:42:14 08/04 17:42:18 4 seconds Phase 4: 08/04 17:42:18 08/04 17:42:18 Phase 5: 08/04 17:42:18 08/04 17:42:26 8 seconds Phase 6: 08/04 17:42:26 08/04 17:42:27 1 second Phase 7: 08/04 17:42:27 08/04 17:42:27 Total run time: 23 seconds done So my last option is to rebuild my disk? Can someone confirm the steps please? stop the array unassign the disk start the array without the disk format the disk with the option that is shown "Format will create a file system in all Unmountable disks" stop the array reassign the disk start the array let the system rebuild my disk
-
Problem with an Unmountable: Unsupported partition layout disk
I don't mind losing the data on this disk if I can get it back by rebuilding the array but if I can fix it without doing that, it would be great. Here's the result for the Check Filesystem: Phase 1 - find and verify superblock... - block cache size set to 148496 entries Phase 2 - using internal log - zero log... zero_log: head block 2270027 tail block 2270027 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't 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 = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Tue Aug 2 22:21:54 2022 Phase Start End Duration Phase 1: 08/02 22:21:48 08/02 22:21:48 Phase 2: 08/02 22:21:48 08/02 22:21:49 1 second Phase 3: 08/02 22:21:49 08/02 22:21:53 4 seconds Phase 4: 08/02 22:21:53 08/02 22:21:53 Phase 5: Skipped Phase 6: 08/02 22:21:53 08/02 22:21:54 1 second Phase 7: 08/02 22:21:54 08/02 22:21:54 Total run time: 6 seconds
-
Problem with an Unmountable: Unsupported partition layout disk
Hi everyone, I have checked my server today and discovered that one of my disk show the message "Unmountable: Unsupported partition layout". This is not a new disk. It is there for many years now and I don't know why I got this message today. I have the option to format the disk but I'm not sure it's the way to go. What steps should I do to fix this? I have attached my diagnotics file in case it can help. Thank you for your help! tower-diagnostics-20220802-2027.zip
-
skoub started following Harddrive still active even if spun-down? and Faulty Disk and can't do a SMART test
-
MicroServer N36L/N40L/N54L - 6 Drive Edition
hi everyone! is anybody using this server to encode movies in x264 with handbrake? what's the fps that you get? Presently, i have a little server with a G1620 with 1,16fps (preset=veryslow, profile=high). thank you for the info!
-
HowTo: Install HandBrakeCLI on your unRAID server (rather than in a VM)
i tried to compile it but when i run this command "./configure --launch --disable-gtk", i get this error: probe: host tuple...(pass) i686-pc-linux-gnu compute: available architectures...(pass) i686 find: ar...(fail) not found : name[0] = ar ERROR: unable to continue; configure stop. someone know what im missing?
skoub
Members
-
Joined
-
Last visited