nordika

Members
  • Posts

    37
  • Joined

  • Last visited

Posts posted by nordika

  1. Hello,

     

    When trying to format an old disk in Unraid (which was previously formatted in Windows as ntfs), I got this log:

     

    ar 23 16:19:50 Adonis kernel: Buffer I/O error on dev sdf, logical block 732566641, async page read
    Mar 23 16:19:50 Adonis kernel: ata8: EH complete
    Mar 23 16:19:50 Adonis kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
    Mar 23 16:19:50 Adonis kernel: ata8.00: BMDMA stat 0x25
    Mar 23 16:19:50 Adonis kernel: ata8.00: failed command: READ DMA EXT
    Mar 23 16:19:50 Adonis kernel: ata8.00: cmd 25/00:08:88:a3:50/00:00:5d:01:00/e0 tag 0 dma 4096 in
    Mar 23 16:19:50 Adonis kernel: ata8.00: status: { DRDY ERR }
    Mar 23 16:19:50 Adonis kernel: ata8.00: error: { UNC }
    Mar 23 16:19:50 Adonis kernel: ata8.00: configured for UDMA/133
    Mar 23 16:19:50 Adonis kernel: sd 4:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
    Mar 23 16:19:50 Adonis kernel: sd 4:0:0:0: [sdf] tag#0 Sense Key : 0x3 [current] 
    Mar 23 16:19:50 Adonis kernel: sd 4:0:0:0: [sdf] tag#0 ASC=0x11 ASCQ=0x4 
    Mar 23 16:19:50 Adonis kernel: sd 4:0:0:0: [sdf] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 88 00 00 00 08 00 00
    Mar 23 16:19:50 Adonis kernel: I/O error, dev sdf, sector 5860533128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    Mar 23 16:19:50 Adonis kernel: Buffer I/O error on dev sdf, logical block 732566641, async page read
    Mar 23 16:19:50 Adonis kernel: ata8: EH complete
    Mar 23 16:19:50 Adonis kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
    Mar 23 16:19:50 Adonis kernel: ata8.00: BMDMA stat 0x25
    Mar 23 16:19:50 Adonis kernel: ata8.00: failed command: READ DMA EXT
    Mar 23 16:19:50 Adonis kernel: ata8.00: cmd 25/00:08:88:a3:50/00:00:5d:01:00/e0 tag 0 dma 4096 in
    Mar 23 16:19:50 Adonis kernel: ata8.00: status: { DRDY ERR }
    Mar 23 16:19:50 Adonis kernel: ata8.00: error: { UNC }
    Mar 23 16:19:50 Adonis kernel: ata8.00: configured for UDMA/133
    Mar 23 16:19:50 Adonis kernel: sd 4:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
    Mar 23 16:19:50 Adonis kernel: sd 4:0:0:0: [sdf] tag#0 Sense Key : 0x3 [current] 
    Mar 23 16:19:50 Adonis kernel: sd 4:0:0:0: [sdf] tag#0 ASC=0x11 ASCQ=0x4 
    Mar 23 16:19:50 Adonis kernel: sd 4:0:0:0: [sdf] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 88 00 00 00 08 00 00
    Mar 23 16:19:50 Adonis kernel: I/O error, dev sdf, sector 5860533128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
    Mar 23 16:19:50 Adonis kernel: ata8: EH complete
    Mar 23 16:19:52 Adonis unassigned.devices: Reloading disk '/dev/sdf' partition table.
    Mar 23 16:19:52 Adonis unassigned.devices: Reload partition table result: /dev/sdf:  re-reading partition table
    Mar 23 16:19:52 Adonis unassigned.devices: Formatting disk '/dev/sdf' with 'xfs' filesystem.
    Mar 23 16:19:52 Adonis unassigned.devices: Format drive command: /sbin/mkfs.xfs -f '/dev/sdf1' 2>&1
    Mar 23 16:19:53 Adonis unassigned.devices: Format disk '/dev/sdf' with 'zfs' filesystem failed: Error accessing specified device /dev/sdf1: No such file or directory Usage: mkfs.xfs /* blocksize */#011#011[-b size=num] /* config file */#011[-c options=xxx] /* metadata */#011#011[-m crc=0|1,finobt=0|1,uuid=xxx,rmapbt=0|1,reflink=0|1, #011#011#011    inobtcount=0|1,bigtime=0|1] /* data subvol */#011[-d agcount=n,agsize=n,file,name=xxx,size=num, #011#011#011    (sunit=value,swidth=value|su=num,sw=num|noalign), #011#011#011    sectsize=num /* force overwrite */#011[-f] /* inode size */#011[-i perblock=n|size=num,maxpct=n,attr=0|1|2, #011#011#011    projid32bit=0|1,sparse=0|1] /* no discard */#011[-K] /* log subvol */#011[-l agnum=n,internal,size=num,logdev=xxx,version=n #011#011#011    sunit=value|su=num,sectsize=num,lazy-count=0|1] /* label */#011#011[-L label (maximum 12 characters)] /* naming */#011#011[-n size=num,version=2|ci,ftype=0|1] /* no-op info only */#011[-N] /* prototype file */#011[-p fname] /* quiet */#011#011[-q] /* realtime subvol */#011[-r extsize=num,size=num,rtdev=xxx] /* sectorsize */#011[-s size=num] /* version */#011#011[-V] #011#011#011devicename <d

    ** Press ANY KEY to close this window ** 

     

     

    Can you please help?

     

    Thanks.

     

     

  2. Hi,

     

    I am trying to run the process above but after starting the array in maintenance mode and clicking on the disk I want to check, I cannot see this:

     

    "You should see a page of options for that drive, beginning with various partition, file system format, and spin down settings. The section following that is the one you want, titled Check Filesystem Status. There is a box with the 2 words Not available in it. This is the command output box, where the progress and results of the command will be displayed. Below that is the Check button that starts the test or repair, followed by the options box where you can type in options for the test/repair command. The options box may already have default options in it, for a read-only check of the file system. For more help, click the Help button in the upper right."

     

    I am running 6.11.5.

     

    Can someone help?

     

    Thanks.

  3. On 11/22/2022 at 7:55 PM, mafkees1233 said:

    Thank you for your reply.

    I'm trying to connect from a computer in the same network.

    The url displayed is 192.168.0.152:9091 , which is the correct ip and port for the server.

    Other containers (portainer) are working fine

    In Peerport, insert a port number.

    I had this issue myself and it was solved this way.

  4. 10 hours ago, trurl said:

    Post diagnostics

    Hi trurl,

     

    Here it is:

     

     

    Pulling image: binhex/arch-krusader:latest

    IMAGE ID [latest]: Pulling from binhex/arch-krusader. 
    IMAGE ID [22244236f553]: Pulling fs layer. Downloading 100% of 656 KB. Verifying Checksum. Download complete. Extracting. Pull complete. 
    IMAGE ID [6c1d8bd44355]: Pulling fs layer. Downloading 100% of 5 KB. Verifying Checksum. Download complete. Extracting. Pull complete. 
    IMAGE ID [6cc4d86ea9ca]: Pulling fs layer. Downloading 100% of 99 MB. Verifying Checksum. Download complete. Extracting. Pull complete. 
    IMAGE ID [f05c437884d0]: Pulling fs layer. Verifying Checksum. Download complete. Extracting. Pull complete. 
    IMAGE ID [4b12aa7a512b]: Pulling fs layer. Downloading 100% of 2 KB. Download complete. Extracting. Pull complete. 
    IMAGE ID [90236c47a3d5]: Pulling fs layer. Downloading 100% of 168 MB. Verifying Checksum. Download complete. Extracting. Pull complete. 
    IMAGE ID [33aaeb2eadaf]: Pulling fs layer. Download complete. Extracting. Pull complete. 
    IMAGE ID [15a3d58300e8]: Pulling fs layer. Downloading 100% of 2 KB. Verifying Checksum. Download complete. Extracting. Pull complete. 
    IMAGE ID [7445d0565b8e]: Pulling fs layer. Downloading 100% of 1019 B. Verifying Checksum. Download complete. Extracting. Pull complete. 
    IMAGE ID [55d5b196cdc8]: Pulling fs layer. Downloading 100% of 7 KB. Verifying Checksum. Download complete. Extracting. Pull complete. 
    IMAGE ID [35f3a0aceaf6]: Pulling fs layer. Downloading 100% of 203 MB. Verifying Checksum. Download complete. Extracting. 
    IMAGE ID [6497eb1aba75]: Pulling fs layer. Downloading 100% of 3 KB. Download complete. 
    IMAGE ID [687f6fd87943]: Pulling fs layer. Downloading 100% of 1 KB. Download complete. 
    IMAGE ID [c8166650c2bb]: Pulling fs layer. Downloading 100% of 263 MB. Verifying Checksum. Download complete. 

    TOTAL DATA PULLED: 733 MB

    Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: write /usr/lib/python3.7/asyncio/__pycache__/base_subprocess.cpython-37.pyc: no space left on device

     

  5. @trurl

     

    That is exactly how I have it but with a mac and not a pc.

     

    My doubt is how do I configure the time the mac will take to shutdown in case of a power failure?

     

    Because I want it to shutdown before my unRAID.

    Just take a look at the file. It is well documented with comments.

    On my PC I had to manually edit apcupsd.conf.

     

     

    Thanks Trurl, I will look up for that file on the mac.

     

    You cannot supply me with your apcupsd.conf for my guidance?

     

    Thanks

     

     

    Thanks trurl.