Foxsat HDR stuck in delete loop

No under /dev is this:

root@CECC04:/dev# ls
block ttyS0 ttyS111 ttyS125 ttyS139 ttyS152 ttyS166 ttyS18 ttyS20 ttyS34 ttyS48 ttyS61 ttyS75 ttyS89
fd ttyS1 ttyS112 ttyS126 ttyS14 ttyS153 ttyS167 ttyS180 ttyS21 ttyS35 ttyS49 ttyS62 ttyS76 ttyS9
kmsg ttyS10 ttyS113 ttyS127 ttyS140 ttyS154 ttyS168 ttyS181 ttyS22 ttyS36 ttyS5 ttyS63 ttyS77 ttyS90
lxss ttyS100 ttyS114 ttyS128 ttyS141 ttyS155 ttyS169 ttyS182 ttyS23 ttyS37 ttyS50 ttyS64 ttyS78 ttyS91
null ttyS101 ttyS115 ttyS129 ttyS142 ttyS156 ttyS17 ttyS183 ttyS24 ttyS38 ttyS51 ttyS65 ttyS79 ttyS92
ptmx ttyS102 ttyS116 ttyS13 ttyS143 ttyS157 ttyS170 ttyS184 ttyS25 ttyS39 ttyS52 ttyS66 ttyS8 ttyS93
pts ttyS103 ttyS117 ttyS130 ttyS144 ttyS158 ttyS171 ttyS185 ttyS26 ttyS4 ttyS53 ttyS67 ttyS80 ttyS94
random ttyS104 ttyS118 ttyS131 ttyS145 ttyS159 ttyS172 ttyS186 ttyS27 ttyS40 ttyS54 ttyS68 ttyS81 ttyS95
shm ttyS105 ttyS119 ttyS132 ttyS146 ttyS16 ttyS173 ttyS187 ttyS28 ttyS41 ttyS55 ttyS69 ttyS82 ttyS96
stderr ttyS106 ttyS12 ttyS133 ttyS147 ttyS160 ttyS174 ttyS188 ttyS29 ttyS42 ttyS56 ttyS7 ttyS83 ttyS97
stdin ttyS107 ttyS120 ttyS134 ttyS148 ttyS161 ttyS175 ttyS189 ttyS3 ttyS43 ttyS57 ttyS70 ttyS84 ttyS98
stdout ttyS108 ttyS121 ttyS135 ttyS149 ttyS162 ttyS176 ttyS19 ttyS30 ttyS44 ttyS58 ttyS71 ttyS85 ttyS99
tty ttyS109 ttyS122 ttyS136 ttyS15 ttyS163 ttyS177 ttyS190 ttyS31 ttyS45 ttyS59 ttyS72 ttyS86 urandom
tty0 ttyS11 ttyS123 ttyS137 ttyS150 ttyS164 ttyS178 ttyS191 ttyS32 ttyS46 ttyS6 ttyS73 ttyS87 zero
tty1 ttyS110 ttyS124 ttyS138 ttyS151 ttyS165 ttyS179 ttyS2 ttyS33 ttyS47 ttyS60 ttyS74
 
Is this real Ubuntu or that odd emulated thing on W10?
I think the latter.

Is there a Linux version I can run on Windows 10 with a user friendly GUI?
You cannot use Windows. As I thought I explained previously, Windows is not compatible with the Ext3 file system. Running a command shell which emulates the Linux command line is not the same as running Linux.
It needs to be Linux, because Windows is not compatible with the Ext3 file system

You must boot to Linux. Modern Linuxes do have user-friendly GUIs. You can bring up a command window just the same as you have in Windows, but this time it will be the real linux command line.
 
You must boot to Linux. Modern Linuxes do have user-friendly GUIs. You can bring up a command window just the same as you have in Windows, but this time it will be the real linux command line.
Yes, I came to the same conclusion so I booted up an old DVD I had with an OS called Puppy Linux (recommended by either Rick Maybury or Jack Scofield in one of the newspaper tech columns). It booted up OK with a row of disc icos in the bottom LH corner of the desktop. Hovering in turn on all of these revealed that they were all NTFS of various sizes and none was my USB connected 1TB Seagate Humax Ext3. I also had a look around the file manager under root, /dev and /mnt but could not see anything which look like a USB connected Ext3 disc. What am I missing?

Alternatively it's beginning to look like a new HDD would be a quicker solution as I've already spent a day on and off on this.
 
What am I missing?
Puppy might have mounted your internal drive(s) by default, but not external ones (unlike Windows, drives are not automatically mounted and different distros take different approaches to what the GUI decides to mount at boot). I said to use GParted (if GParted isn't installed, you're using the wrong disro), which will show you what drives are actually accessible (mounted or not).

Basically you are choosing to go your own way instead of following recommendations, and then complaining because you don't know what to do.

Alternatively it's beginning to look like a new HDD would be a quicker solution as I've already spent a day on and off on this.
Possibly it is, if you don't have free time. It might come to that anyway.
 
Many thanks for all your suggestions. It's been around 30 years since I worked with Sun Unix workstations. It will take a while before I'm up to speed so I'd appreciate patience and spoon feeding ;-)

I don't have a dedicated Linux box so I'm booting Linux from a dvd. I'm having trouble setting up the browser and the internet connection hence I could not get the Gnome-disk-utility directly. I therefore downloaded the tar file using my Windows machine and transferred it over to the one running Puppy Linux via FAT32USB stick and extracted it. The extracted files do not appear to have gnome-disk-utility in a form that will run. There seems to be some further building to be done. I'm currently struggling with this. Any pointers gratefully received.

When and if I do get Gnome-disk-utility installed and get the usb disc mounted what do I then have to do to prevent the Humax going straight back into a delete loop when I re-install the HDD.
 
Getting nowhere fast trying to install gnome-disks-utility from the extracted tar archive. Missing sudo apt-get command?!? Must admit I'm lost now. Doesn't help that I can't work out how to copy and paste in a shell/console window. Right click, ctrl+C, ctrl+V, ctrl+shft+C and ctrl+shft+V don't work
 
Getting nowhere fast trying to install gnome-disks-utility from the extracted tar archive. Missing sudo apt-get command?!? Must admit I'm lost now. Doesn't help that I can't work out how to copy and paste in a shell/console window. Right click, ctrl+C, ctrl+V, ctrl+shft+C and ctrl+shft+V don't work
What are you trying to do exactly?
If you're trying to access an hard drive from a Linux distribution then just boot from a Linux dvd (or usb) that is less than 6-7 years old that has a GUI. People have suggested that already. Use one that has a GUI that is relatively easy to navigate etc. Eg Linux Mint cd less than 7 years old.
Otherwise if you're set on using your old Puppy Linux, then why not give us a clue as to which version you're talking about? They've had GParted in that since something like version 5.x so why not use that (ie GParted in Puppy)? If you have a version of Puppy older than, say 5.4, then things will get messy.
 
Last edited:
Just use the command line and run the commands in post #20. Messing with GUI stuff is just too hard and unpredictable as no-one can see what you see.
As long as you can get a browser running and logged in to the forum, then you can copy/paste text from the terminal.
I would suggest you run a modern Ubuntu or Mint or SystemRescueCd rather than something old.
 
If you're trying to access an hard drive from a Linux distribution then just boot from a Linux dvd (or usb) that is less than 6-7 years old that has a GUI. People have suggested that already. Use one that has a GUI that is relatively easy to navigate etc. Eg Linux Mint cd less than 7 years old.
Otherwise if you're set on using your old Puppy Linux, then why not give us a clue as to which version you're talking about? They've had gparted in that since something like version 5.x so why not use that? If you have a version older then that, then things will get messy.
Yes, I was slowly coming round to that thought, so I put a more recent Puppy version (fossapup64-9.5) onto a bootable USB stick and am using that now. Will try Mint if it's no better
Just use the command line and run the commands in post #20. Messing with GUI stuff is just too hard and unpredictable as no-one can see what you see.
As long as you can get a browser running and logged in to the forum, then you can copy/paste text from the terminal.
Having trouble finding the USB connected Humax HDD. What's most likely? Under /dev?
 
lsblk would be my first try. I presume you have /dev/sda in the PC itself and /dev/sdb is the USB disk.
If so, then fdisk -lu /dev/sdb will show the partition table and smartctl -a /dev/sdb the SMART stats.
Report the output between
Code:
tags.
found it under /dev/sdd I think it's the only Linux disk , the rest are NTFS
However I get command not found when I tried smartctl . Does Mint have it?
 
It sounds like you're trying to find the Linux drive/partitions by digging around and unwittingly mounting every partition you come across.
After you've done your digging try
Code:
sudo umount -a
sudo lsblk
sudo fdisk -lu /dev/sdb /dev/sdc /dev/sdd
This is just the bits mentioned in #20.
Post the results so that someone can advise depending upon the results.
 
I am doing my best trying to follow the advice but am finding it somewhat cryptic. Trying to comply and so we're on the same page, I've put "Linux Mint 20.1 "Ulyssa" - Cinnamon (64-bit)" on a USB flash drive and will run that from now on.

Sorry didn't realise lsblk was a command. It was not boxed as the fdsk and smartctl ones were in the post.

lsblk list looked OK to me (sorry I haven't worked out how to get a text file across yet)

had to install fdisk and use sudo to run it
it listed 4 partitions on sdd (the humax hdd)
device size
sdd1 16.1G
sdd2 815.8M
sdd3 7.1T
sdd4 200G

all ID 83, type Linux

don't understand this as the disc is only 1TB total. They don't make 7TB discs , do they?

re smartctl: I'm getting "command not found". Where can I find it?

BTW apropos of nothing this Mint GUI is horrible . Is there nicer version of Mint?
 
had to install fdisk and use sudo to run it
You have to prefix most of these things with sudo. Or just run sudo -i first and that then gives you a shell with elevated permissions.
it listed 4 partitions on sdd (the humax hdd)
device size
sdd1 16.1G
sdd2 815.8M
sdd3 7.1T
sdd4 200G
That all looks very strange, but please can you run the exact commands specified above i.e. fdisk -lu /dev/sdd in this case.
Ctrl-Shift-C after highlighting the required text will copy it to the clipboard.
The output should look similar to this (but this is from a 500GB drive):
Code:
Foxsat-HDR~# fdisk -lu /dev/hda

Disk /dev/hda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1               2     4209029     2104514   83  Linux
/dev/hda2         4209030     4417874      104422+  83  Linux
/dev/hda3         4417875   924331904   459957015   83  Linux
/dev/hda4       924331905   976768064    26218080   83  Linux
re smartctl: I'm getting "command not found". Where can I find it?
Please read the previous post.
BTW apropos of nothing this Mint GUI is horrible . Is there nicer version of Mint?
I use Mate. Hated Cinnamon.
 
Can't get Linux to run after the crash. I've tried Mint Cinnamon, Mint Mate and writing the USB with Rufus and Etcher, I either get the LM logos then nothing or the LM logos and then a scrambled display - like the graphics card is on the blink, which it's not because the POST, UEFI/BIOS and Windows 10 all display perfectly. Have been at it all morning - I may have to go back to the Puppy DVD!
 
got there by running Mint from a dvd in compatibility mode

Code:
mint@mint:/$ sudo fdisk -lu /dev/sdc
Disk /dev/sdc: 931.53 GiB, 1000204886016 bytes, 244190646 sectors
Disk model: 002-1CT162    
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x2771848c

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdc1                2    4209029    4209028  16.1G 83 Linux
/dev/sdc2          4209030    4417874     208845 815.8M 83 Linux
/dev/sdc3          4417875 1901083904 1896666030   7.1T 83 Linux
/dev/sdc4       1901083905 1953520064   52436160   200G 83 Linux
 
Last edited:
and the smart report is
Code:
mint@mint:/$ sudo smartctl -a /dev/sdc
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-58-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Video 3.5 HDD
Device Model:     ST1000VM002-1CT162
Serial Number:    S1G122H3
LU WWN Device Id: 5 000c50 060f4646b
Firmware Version: SC23
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5900 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Sat Feb 13 12:15:07 2021 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x82)    Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever
                    been run.
Total time to complete Offline
data collection:         (  107) seconds.
Offline data collection
capabilities:              (0x7b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   1) minutes.
Extended self-test routine
recommended polling time:      ( 137) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x10b9)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   094   093   006    Pre-fail  Always       -       216020224
  3 Spin_Up_Time            0x0003   098   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2546
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       40
  7 Seek_Error_Rate         0x000f   086   060   030    Pre-fail  Always       -       450237824
  9 Power_On_Hours          0x0032   043   043   000    Old_age   Always       -       50559
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   020    Old_age   Always       -       2546
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       512
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       8590065666
189 High_Fly_Writes         0x003a   055   055   000    Old_age   Always       -       45
190 Airflow_Temperature_Cel 0x0022   069   045   045    Old_age   Always   In_the_past 31 (Min/Max 19/31)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       2545
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       2546
194 Temperature_Celsius     0x0022   031   055   000    Old_age   Always       -       31 (0 15 0 0 0)
197 Current_Pending_Sector  0x0012   095   095   000    Old_age   Always       -       936
198 Offline_Uncorrectable   0x0010   095   095   000    Old_age   Offline      -       936
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 531 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 531 occurred at disk power-on lifetime: 50521 hours (2105 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      02:45:28.609  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:45:28.589  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:45:28.575  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:45:28.559  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:45:28.547  READ DMA EXT

Error 530 occurred at disk power-on lifetime: 50521 hours (2105 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      02:41:21.141  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:41:21.115  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:41:21.102  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:41:21.061  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:41:21.035  READ DMA EXT

Error 529 occurred at disk power-on lifetime: 50521 hours (2105 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      02:37:14.407  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:37:14.383  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:37:14.364  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:37:14.346  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:37:14.327  READ DMA EXT

Error 528 occurred at disk power-on lifetime: 50521 hours (2105 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      02:33:06.891  READ DMA EXT
  35 00 38 ff ff ff ef 00      02:33:06.884  WRITE DMA EXT
  35 00 00 ff ff ff ef 00      02:33:06.876  WRITE DMA EXT
  25 00 08 ff ff ff ef 00      02:33:06.848  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:33:06.830  READ DMA EXT

Error 527 occurred at disk power-on lifetime: 50521 hours (2105 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      02:28:59.196  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:28:59.176  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:28:59.161  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:28:59.142  READ DMA EXT
  25 00 08 ff ff ff ef 00      02:28:59.130  READ DMA EXT

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
 
Back
Top